Repository navigation
Document Storefront verified reviews, promotion availability, order chat and add-on limits - #65
Merged
Merged
Conversation
…hat and add-on limits
New requests: GET orders/{id}/activity-flow, GET orders/{id}/stores, and
POST customers/socket-token.
Checkout: gateway is a code (or cash); customer, cart and service_quote
requirements; pickup and cash are booleans; percentage tips; promoCode alias;
ebarimt_registration_no; socket_token and the checkout.{id} realtime channel;
status answered from the database with verify; QPay callback answers SUCCESS
in plain text and PAYMENT_NOT_PAID; payment intent updates keep the checkout;
setup intent takes only customer; capture uses the cart snapshot, bookings
and multi-store master orders.
Carts: open, checked out and cleared statuses; empty returns the device's open
cart; catalog and food-truck lines. Service quotes: cart_items_unavailable 422,
facilitator, scheduled_at, service_type, all, is_route_optimized, full quote
object. Customers: email fallback, review-account bypass, create and update
fields. Order chat: limit 50, chat_ id prefix, 403/422, socket token.
Food trucks: store, network and catalog pricing, network scoping, retrieve
scoped to the storefront. Reviews: reviews_disabled and network store param.
Products, stores, promotions, notifications and categories: corrected fields
and descriptions.
5 of 16 tasks
roncodes
added a commit
that referenced
this pull request
Oct 14, 2026
The three storefront customer requests describe both the review-account bypass and the SMS guard limits.
roncodes
added a commit
that referenced
this pull request
Oct 14, 2026
The notification type list names both the activity and chat types from #65 and the order_updated, order_item_unavailable and order_balance_paid types.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the Storefront API changes from fleetbase/storefront#115, #116, #117 and #118, which the redesigned app uses:
GET reviews/eligibility), returningcan_review,reason,message,orderandreview.orderandfiles, and the403 { error, reason }refusal.storeparam (required with network keys) and the sort values.subject_type,verifiedandis_mine. The reviewer is shown as first name and last initial, with no email or phone.include=scheduled.code(a shareable code),availability,next_starts_atandowner.applies_tolists public IDs.before/limit), Send Order Chat Message and Mark Order Chat as Read. It covers the Order Chat object, thechat.{id}socket channel and events, and the 401/403/404/409driver_not_assigned/423chat_closedrefusals.is_requiredandmax_selectable.Related Issue
Closes #
Type of Change
Implementation Notes
Requests whose result depends on data the run may not have follow the collection's existing
expected_statuspattern:403refusal unless the environment setsreview_eligible.chat_order_idset (an order with an assigned driver), they expect success;order_idand expect409 driver_not_assigned;404.Validation
Command output / summary:
Not run:
postman:run:storefront. It needs a running stack with the backend PRs deployed.Documentation Impact
fleetbase/fleetbase.ioUpdate: complete against storefront v0.4.25 (fleetbase/storefront#119)
I compared every
storefront/v1route, controller and response resource onrelease/v0.4.25with this collection.New requests
GET orders/{id}/activity-flow: the order's progress steps.GET orders/{id}/stores: each store's part of a multi-store Network order.POST customers/socket-token: a customer token for the realtime connection.Corrected or completed
gatewayis a gateway code orcash.customer,cartandservice_quoteare now marked required where the API requires them.pickupandcashare booleans, and tips accept percentages.promoCodealias andebarimt_registration_no.socket_tokenand thecheckout.{id}realtime channel.verify.SUCCESSin plain text, andPAYMENT_NOT_PAIDreplacesPAYMENT_NOTFOUND.customer.cart_items_unavailable422, new params (facilitator,scheduled_at,service_type,all,is_route_optimized) and the full quote object.limitdefaults to 50, chat ids use thechat_prefix, the 403 and 422 responses, and the socket token.storeandnetworkfields, catalog pricing, network scoping, and retrieve limited to the storefront's own trucks.reviews_disabledand the networkstoreparam.npm run postman:lintpasses with 0 errors.