Checkout

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.

Two ways to offer delivery choices

• Shipping rates. Fetch shipping costs for the merchant's configured carrier accounts. Each carrier account typically maps to a specific carrier service (for example, one account for FedEx Economy 2–3 Day, another for FedEx Priority Overnight). Each account can be configured to fetch live rates from the carrier, or to use a costing profile in Carriyo. Use this when you want to expose carrier services directly to the customer.
• 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). Use this when you want full control over what the customer sees, regardless of the underlying carriers.

The two are not exclusive (a merchant can use both), but most integrations pick one as the primary approach.

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.