Storefront

Storefront is the shopper-facing surface that powers delivery choices on your webstore or app. It gives you the delivery options a customer can pick, live carrier rates for a route, a per-product delivery promise for product pages, and the eligible stores or warehouses near a customer. Every lookup is stateless: it reads your configuration, it doesn't create an order.

At checkout, you control which delivery choices your customer sees. Carriyo gives you two ways to do this. The right one depends on whether you want to expose carrier services directly, or present a curated list of named delivery options.

Presenting delivery choices

• Delivery options. Present a curated list of options the merchant has configured. Each option has its own pricing, estimated delivery time, supported customer geography, eligible fulfillment locations, and delivery method (home delivery or customer collection). This is the storefront surface for showing priced delivery choices to shoppers.

To compare raw carrier rates across carrier accounts and choose a carrier for a shipment — an internal, operator-facing task rather than a shopper one — see Shipping rates under carrier configuration.

Beyond the cart, the same surface serves product pages and locators: fetch a delivery promise per product with per-product delivery options, and find the nearest eligible stores or warehouses with eligible locations.

What the customer's choice carries into the rest of the platform

Whichever approach is used, the customer's choice is captured and sent back to Carriyo when the order or shipment is created:

• For delivery options, the order or shipment carries the delivery_option code (or id). If the merchant is using Carriyo's order management, the chosen delivery option constrains Allocation: only the fulfillment locations attached to that option are eligible.
• For shipping rates, the order or shipment carries the chosen carrier_account_id, so the shipment is booked through the carrier account the customer picked.

In both cases, the customer's checkout choice becomes the operational reality: what was shown is what gets honored.

The estimated delivery date becomes a promise

A delivery option's response carries an estimated delivery date for each eligible option returned. When the customer picks one, that estimate is captured on the order and becomes the customer-facing promise. The internal SLAs that track whether that promise is being met are computed later, once the shipment is created. See Automation → service levels.

How it fits with other modules

• Orders. The chosen delivery option flows into the order and constrains allocation.
• Shipping. The chosen carrier account (or the carrier account behind the chosen delivery option) is the one that books the shipment.
• Carrier configuration. Carrier accounts, costing profiles, and network profiles drive what checkout can return.
• Locations. Delivery options reference fulfillment locations and customer collection locations.