Nothing about a parcel is settled until the label exists, so Odoo asks for one at the point of dispatch and the tracking that comes back reaches the order the customer is actually watching.
A shipping label is not a document, it is a purchase. The moment one is created the carrier is chosen, the service is fixed and the cost is committed, which is why the timing of that request matters more than the mechanics of it. Warehouses that create labels early end up voiding them when an order changes, and warehouses that create them by hand end up with a second browser tab, a retyped address and a parcel that leaves with no tracking against the order. Connecting Odoo and Amazon Shipping puts the request at dispatch, where the order has stopped moving.

The Amazon Shipping label is requested when the Odoo delivery is ready to go, so a change to the order earlier in the day does not leave a bought label to be voided.
Alumio connects to Amazon Shipping through the interface it makes available, so the packing bench stops retyping an address that already exists one screen away in Odoo.
The reference comes back onto the Odoo delivery, so a customer asking where their parcel is gets an answer from the order rather than from somebody searching a carrier portal.
Because each label is tied to the Odoo delivery it belongs to, a second attempt is recognised rather than producing a duplicate that ships twice and gets refunded once.
A delivery is picked and confirmed in Odoo, and Alumio requests the Amazon Shipping label at that moment, so the parcel leaves with the right service on it and nothing was committed while the order could still change.
Once the label is issued, Alumio writes the tracking reference onto the Odoo delivery, so support answers a question about a parcel from the order record instead of opening a carrier site and searching by address or by name.
Parcel weights and dimensions held against the Odoo delivery travel with the label request, so the service and the cost are calculated from what is actually in the box rather than from a default set when the account was opened.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
A customer watches a parcel more closely than they watched the order, and that is where the next connection goes. The tracking reference reaching Odoo is useful to the business, and the shopper still finds out by checking, so a notification service that tells them when something changes is the common addition to Odoo and Amazon Shipping. Alumio holds that connection alongside this one, so the message goes out from the same event.
It can, and the two halves are timed separately. The Amazon Shipping label request goes out when an Odoo delivery reaches the state you nominate, usually confirmed and ready to dispatch, while the tracking reference comes back as soon as it is issued. Keeping those apart is what stops a label being bought against an order that is still being amended in the warehouse.
No, this is configured rather than coded. The second browser tab goes away, along with the address somebody retypes into it and the tracking number they paste back afterwards. Which Odoo delivery state triggers an Amazon Shipping label, and which weights and services apply, are entries in Alumio. Where a business calculates parcel dimensions on a rule of its own, the Code Transformer takes that step.
Money and choice, both of which is why the timing is worth deciding. Creating the Amazon Shipping label commits the cost and fixes the service, so an Odoo order that changes afterwards means voiding and reissuing rather than simply editing. Requesting it at the point the delivery is confirmed keeps the order editable for as long as it genuinely is, and means the label on the box describes the parcel that is actually going out.
A parcel that shipped with no tracking returned is the failure the customer finds, because the goods are moving and the order cannot say so. Alumio monitors each request live and records the Odoo delivery the label was asked for, so an Amazon Shipping reference that never comes back raises an alert naming the delivery and the reason. Retries run where configured, so nothing is quietly shipped untracked.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.