Checkout methods
Your customers choose how their order reaches them when they pay: “Express”, “Standard”, “Point relais”, “Click and collect”. The “Checkout methods” tab of the “Automation” page, the last page under “Orders & shipping”, lists every one of them and lets you say which carrier service its labels are bought with, so a customer who paid for next-day delivery gets a next-day label without anyone choosing it by hand.
The card was in “Settings”, in the section called Shipping Defaults, until September 2026. An old link to it opens this tab, and that section, “Sender & packages” since then, keeps a short note with “Open checkout methods”.
Where the methods come from
Each store sends the method with the order, and Horizon keeps it:
| Store | What is kept |
|---|---|
| Shopify | The shipping line’s title, its rate code and source, the carrier and the delivery category, plus the customer’s language |
| WooCommerce | The shipping method’s title, its method id (flat rate, free shipping, a plugin’s own) and the zone instance; local pickup is recognised |
| PrestaShop | The name of the carrier the customer picked, its id and reference, plus the order’s language |
| Adobe Commerce | The shipping description and the shipping method code |
| CSV file | An optional delivery_method column (or shipping_method), and an optional language column |
The card groups orders by the method’s name as the customer saw it, one row per store family. A method renamed in the store appears as a new row, because that is what the next customers see.
The card
Every method on your orders of the last 90 days has a row: how many orders used it, how many are still waiting for a label, when it was last seen, and what its labels use right now. The pill says where it stands: “Mapped”, “Suggested”, “Uses shipping settings”, “No label” or “Not mapped”. A method that looks like a pickup point also shows “Pickup point”.
Until you map a method, its labels use your shipping settings, exactly as before.
A mapping you save applies at once to every order still waiting for a label, including orders that arrived before it. The row says how many. “Undo” puts the previous mapping back for a few seconds after you save.
When no order carries a method yet, the card says so and waits: rows appear as orders arrive.
Suggestions
Each row suggests a mapping, and “Accept” saves it in one click. A button above the list accepts every suggestion at once, and saves all of them or none.
The suggestion reads the method’s name and the codes the store sent:
- A rate Horizon’s own Shopify checkout quoted names its exact carrier and service.
- A carrier named in the method (“Chronopost - Chrono 13”, “Mondial Relay Domicile”, “UPS Access Point”) is the only carrier suggested for it, which is what PrestaShop and the WooCommerce carrier modules send. When you cannot buy with that carrier, or it has no such service here (a UPS Access Point, a Colissimo pickup point), there is no suggestion: never another carrier than the one your customer paid for.
- Express, next day, 24h, priority, before 1 pm: an express service, such as UPS Express Saver or Chrono 13.
- Standard, economy, free shipping, home delivery: your shipping settings, or the named carrier’s standard service when it is not your default carrier (“Mondial Relay Domicile” is Mondial Relay’s home delivery).
- Point relais, relay, parcel shop, locker, or “Mondial Relay” alone: a pickup-point service, such as Mondial Relay’s or Chrono Relais. With no pickup-point carrier connected, the row says there is no suggestion. You can still map it: its labels are then created from Create Order (see below).
- Click and collect, local pickup, store pickup: no label.
Only carriers you can buy labels with are ever suggested: the ones in your shipping settings and your own connected carrier accounts. See Connect a carrier account.
The card names services the way you read them (“UPS Express Saver”, “Chronopost Chrono 13”); the service codes appear only in the editor’s lists.
Changing a mapping
“Change” (or “Map” on a row with no mapping) opens the row’s editor. It also says what your store calls the method when the store sent a code of its own. Under “Labels for this method”, choose one of three:
- “Use a carrier service”: pick where it is “Delivered to”, “The customer’s address” or “A pickup point”, then the carrier and its service. A pickup point offers only pickup-point services.
- “Use my shipping settings”: the labels keep your defaults, and the method stops showing as not mapped.
- “Don’t buy labels: the customer collects the order”: automatic labels skip these orders. A label you create by hand for one of them uses your shipping settings.
“Save mapping” saves it, and so does Enter. Escape closes the editor without saving. “Remove mapping” takes the mapping away, and the labels go back to your shipping settings. If a save fails, the editor stays open with your choices and a retry.
A pickup-looking method mapped to a home service gets a warning: customers who chose a pickup point would receive their parcel at home.
Pickup points
Stores do not send us the pickup point a customer picked yet. So an order whose method is mapped to a pickup-point service cannot be labelled from “Orders”, rather than buy a home delivery the customer did not choose, or a pickup-point product with no point:
- The order’s “Shipping label” block says why, and its one action is “Create it in Create Order”: it opens the create order form with the order’s recipient filled in, and you choose the point there.
- A bulk run leaves such orders out before it starts, and names them in its dialog and in its result, as left out with a pickup point to choose, instead of failing each one.
- A label rule refuses it and says why.
Once a store does send the point, the order’s label is bought as usual, to that point.
What decides the label
For an imported order’s label, three things can name the carrier and the service. The first that says something wins:
| Order | Who decides | How |
|---|---|---|
| 1 | Automation rules | “Set the carrier”, “Set the service” or a “Choose the carrier by price or speed” pick replace the mapping entirely: the carrier is the rule’s or your default one, the service the rule’s or that carrier’s default |
| 2 | The checkout method’s mapping | A mapped service gives both the carrier and the service |
| 3 | Your shipping settings (“Sender & packages”) | Everything else: no mapping, a mapping to your defaults, or an order with no method |
A package or sender rule does not decide the service, so the mapping still applies beside it.
A “Choose the carrier by price or speed” rule replaces a mapped service by default. Tick the keep this service box in the mapping’s editor and the rule leaves it alone for that method: no prices are asked for and the order says the customer’s choice was kept. A pickup-point mapping is always kept, since comparing prices could only offer a home delivery instead. A carrier or service rule below the choice still overrides the mapping. See Automation rules.
The mapping applies to a label bought with “Create label”, in a bulk run, and by “Create the shipping label”. It never applies to a return label: how the customer chose to receive an order says nothing about how it comes back.
On the order
The order’s details show the method beside the delivery line, with what decides its label: mapped to a service, an automation rule, your shipping settings, or no label. Once the order has a label, it says which of them the label was bought with. An unmapped method on an order still waiting for its label offers “Map it”, which opens this card.
On “Orders”, a banner asks you to map your methods when it matters: some are not mapped yet while orders wait for a label with them (their labels use your shipping settings until then), and your customers choose between several methods, or one of them looks like express, a pickup point or click and collect. A pickup-point method no connected carrier can serve is not counted: there is nothing to map it to that would buy its labels. “Map methods” opens the card. A store where everyone picks the same one method never sees it. Hiding it keeps it hidden on that browser until a new method appears.
Through the API
The checkout method an order carries and its customer’s language are set by the store’s import and are read-only through the orders API. See API keys.