Amazon MCF adapter - process maps

Amazon MCF adapter - process maps

How every flow in the LataSys 3PL Connector runs when the Amazon MCF adapter is installed. Transport: Selling Partner API (Fulfillment Outbound 2020-07-01 and FBA Inventory v1) over HTTPS. Auth: Login with Amazon - client id (username), client secret (password) and a refresh token; access tokens last an hour and are renewed automatically. Warehouse mappings hold marketplace ids - each marketplace's FBA pool acts as one warehouse.

Shared behaviour for every flow below:

  • Triggers - the scheduler (per-instance cadences on the Synchronisation tab), the Run-an-Operation wizard, or per-record buttons. There is no webhook: SP-API notifications need an AWS SQS/EventBridge destination, so polling carries every flow.
  • Logging - every run writes a Sync Log entry: full request and response (URL, headers with credentials redacted, body), every Odoo action taken, and every record touched. Errors are retryable from the log entry.
  • Watermarks - each flow stamps its last-run time on the instance; the scheduler only fires when the cadence has elapsed.
  • License - flows pause if the licensing service reports the installation suspended for non-payment.

1. Connection test and marketplace fetch
Test Connection Marketplace-participations query - the one SP-API call needing no marketplace id. Validates the credentials AND lists every marketplace id on the account
Fetch Warehouses Offers the same marketplaces on the warehouse mapping line, so the remote code is picked rather than typed

2. Order push

Process diagram
Trigger Cron (order cadence), wizard, auto-send on confirmation
Direction Odoo -> Amazon
Data sent Recipient name, address, phone; SKUs and quantities; speed category; displayable order id, date and comment; fulfilment policy, notification emails, feature constraints (blank box, block AMZL, signature)
Odoo records 3PL Order binding (pending -> sent; held when created on hold)
Failure Retryable Sync Log error; nothing partially written

3. Status poll and despatch write-back

Process diagram
Trigger Cron (status cadence), manual
Direction Amazon -> Odoo
Data received Fulfilment order status; shipment lines and quantities; manufacturer lot codes (informational); carrier code, tracking numbers, customer tracking (Swiship) link
Odoo records Delivery picking validated; backorders; carrier + tracking on the picking; binding state despatched
Failure Savepoint-protected - a failed write-back leaves no partial documents; error is retryable

4. Order amendment
Trigger Update at 3PL on an order Amazon has not started processing
Calls updateFulfillmentOrder
Data sent Destination address, shipping speed, order comment, line quantities
Outcome Amazon applies the changes; once processing has started, the update is rejected and logged

5. Holds and release
Create on hold Orders submitted with fulfilment action Hold reserve FBA stock for up to 14 days without shipping (never-released orders are cancelled by Amazon)
Release The binding's Release button switches the order to Ship
New hold after submission Attempted, but Amazon only documents holds at creation time - may be rejected

6. Order cancellation
Trigger Order cancelled in Odoo
Calls cancelFulfillmentOrder
Outcome Binding closed; if Amazon already despatched, the order is flagged instead

7. Proof of delivery
Trigger POD fetch on a despatched order
Calls getFulfillmentOrder, then package tracking
Data received Current delivery status, delivery date/time, who signed. Amazon exposes no signature image

8. Inventory sync

Process diagram

No lot detail: FBA reports no batch-level stock, so quantities land as product totals.

9. Product match
Match The FBA inventory feed doubles as the product list (SKU, name, ASIN); Odoo products match by SKU and bindings are created
Push Not supported - the catalogue is managed in Seller Central

10. Returns

Process diagram

Amazon reports returns per fulfilment order, not in a global feed - discovery is a per-order sweep of recent despatches.

11. Webhooks

Not available: SP-API push notifications require an AWS SQS or EventBridge destination, which a plain HTTPS endpoint cannot subscribe to. All flows run on the polling cadences.

Amazon, Amazon MCF and FBA are trademarks of their respective owner; the names are used solely to identify the service this module interoperates with.

    • Related Articles

    • Amazon MCF adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to Amazon Multi-Channel Fulfilment (MCF): prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. MCF fulfils your non-Amazon orders from FBA stock via Amazon's ...

    • ShipHero adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the ShipHero adapter is installed. Transport: GraphQL over HTTPS. Auth: Bearer JWT with refresh - enter the developer-user email/password (the adapter obtains and refreshes tokens itself) or paste ...

    • MintSoft adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the MintSoft adapter is installed. Transport: REST v1 over HTTPS. Auth: the MintSoft username/password are exchanged for a 24-hour API key (POST /api/Auth), cached ~23h and sent as the ms-apikey ...

    • ShipBob adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the ShipBob adapter is installed. Transport: ShipBob Developer API 2026-07 (REST/JSON) over HTTPS - api.shipbob.com, or sandbox-api.shipbob.com on sandbox instances. Auth: Personal Access Token as ...

    • Huboo adapter - process maps

      How every flow in the LataSys 3PL Connector runs when the Huboo adapter is installed. Transport: Huboo public REST API v2 over HTTPS (https://api.huboo.uk/v2; a sandbox base URL, if issued during Huboo onboarding, goes in the instance's Base URL ...