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 Selling Partner API.

What this adapter provides

Flow	Supported
Order push and despatch write-back	Yes
Order amendment	Yes - address, speed, comment and quantities, until Amazon starts processing
Order cancellation	Yes
Holds	Yes - create on hold, release per order
Inventory sync	Yes - per marketplace; no lot detail
Product match	Yes - from the FBA inventory feed
Product push	No - the catalogue is managed in Seller Central
Supplier push	No - not applicable to FBA
Returns (registration, labels, discovery)	Yes
Warehouse list fetch	Yes - your marketplaces (see below)
Carrier list fetch	No - the carrier arrives with the despatch
Proof of delivery	Yes - delivery status and signatory from tracking
Webhooks	No - polling only (see below)
ASNs / GRNs	No - inbound FBA shipments are managed in Seller Central

Prerequisites

The LataSys 3PL Connector (core app) installed and licensed.
An Amazon seller account with stock in FBA.
A Selling Partner API developer application registered in Seller Central and self-authorised, giving you:
the LWA client id (starts amzn1.application-oa2-client...);
the LWA client secret;
the refresh token issued when you self-authorise the application (starts Atzr|...).
No AWS keys are needed - SP-API no longer requires AWS signing.

Installation

Install the LataSys 3PL Connector: Amazon MCF Adapter module. The provider then appears in the provider list when creating a 3PL instance, along with its provider card (API operations reference) under Configuration - Providers.

Connection setup

Authentication is Login with Amazon (LWA). On the instance's Connection tab:

Pick the Amazon Region - the SP-API region your seller account lives in; it decides the API endpoint (and its sandbox variant). UK sellers use Europe. The Base URL field is only an advanced override.
Choose the environment - Sandbox uses Amazon's sandbox endpoint for the same region.
Enter the LWA client id as the username, the client secret as the password, and the refresh token, then press Test Connection. Access tokens last an hour and are obtained and renewed automatically; you never manage them.

Test Connection also lists every marketplace id on your account - you will need them for the warehouse mappings next.

Mappings

Warehouses are marketplaces - MCF exposes no warehouses; FBA stock is pooled per marketplace. Add one warehouse mapping line per marketplace, pairing an Odoo warehouse with that marketplace's id as the remote code (amazon.co.uk: A1F83G8C2ARO7P). Fetch Warehouses offers your marketplaces on the mapping line so you do not have to hunt for the ids. Orders ship from the marketplace mapped to their Odoo warehouse - an order is never silently fulfilled from another marketplace's pool - and each marketplace's FBA stock syncs into its own warehouse.
Shipping speed via Requested Methods - MCF has no carrier list; instead every order carries one of Amazon's fixed speed categories: Standard, Expedited or Priority. Press Load Requested Methods to pull the three categories into the Accepted Services list, then map your requested-delivery-method values (and delivery methods) onto them. Where no mapping matches, the adapter falls back to keywords in the delivery-method name (for example "next day" reads as Priority, "express" as Expedited), then to the instance's Default Shipping Speed.
Statuses - press Load Missing Defaults. Complete and Complete (Partial) count as despatched; Unfulfillable and Invalid surface as Hold; Cancelled follows your remote-cancel policy.

Amazon Options tab

Field	What it does
Default Shipping Speed	Speed category sent when neither the requested-method mapping nor the delivery-method name decides one
Create Orders On Hold	Submit orders with fulfilment action Hold: Amazon reserves the stock for up to 14 days without shipping. Release each order with its Release button (the order is cancelled automatically if never released)
Fulfilment Policy	How Amazon handles partial availability: Fill or Kill (ship complete or cancel), Fill All (ship everything, wait for stock) or Fill All Available (ship what is there). Empty uses Amazon's default, Fill or Kill
Default Order Comment	Shown on the packing slip when the order carries no delivery instructions
Notification Emails	Comma-separated addresses Amazon notifies about the shipment (sent on every order)
Blank Box	Request unbranded packaging (BLANK_BOX) on every order
Block Amazon Logistics	Request that Amazon's own last-mile carrier is not used (BLOCK_AMZL) on every order
Signature on Delivery	Request signature confirmation on every order
Stock Measure	Which FBA quantity syncs into Odoo: Fulfillable (what can be picked, packed and shipped today - the default) or Total (includes inbound and reserved units, which overstates what Odoo can sell)
Default Return Reason Code	Amazon return reason code used when registering customer returns. Marketplace-specific - see Amazon's return reason code list for your marketplace

Provider-specific behaviour

Order reference - the configured order reference (Odoo order number or customer reference, per the instance's Order Reference Sent setting) becomes Amazon's seller fulfilment order id. It must be unique and is truncated to 40 characters.
Amendments - changes to the delivery address, speed, comment or line quantities are pushed with Update at 3PL while the order is still in Received or Planning; once Amazon starts processing, amendments are rejected.
Holds - with Create Orders On Hold, stock is reserved for up to 14 days; release with the binding's Release button. Amazon only documents holds at creation time - placing a new hold on an already-submitted order is attempted but may be rejected.
Tracking links - the delivery is written back with Amazon's customer-facing tracking link (a Swiship page), alongside the carrier code and tracking numbers per package.
Proof of delivery - from package tracking: delivery status, date and who signed. Amazon exposes no signature image.
Lot codes - FBA does not do batch-level fulfilment. Despatches arrive un-batched; manufacturer lot codes are reported per shipment item for information only (a single code inherits the item quantity). Keep "Products Use Batch/Lot Tracking" off on MCF instances.
Returns - registering a return yields an RMA page URL with the return barcode and mailing label; postage is not prepaid. Only SKUs actually shipped on the order can be returned, and the Default Return Reason Code must be set. The returns cron discovers returns per fulfilment order (Amazon has no global returns feed), sweeping orders despatched in the last 60 days.
No webhooks - polling only - SP-API push notifications require an AWS SQS or EventBridge destination, which a plain HTTPS webhook cannot subscribe to. All updates arrive via the scheduled polls; set the status and stock cadences accordingly.

Troubleshooting

Symptom	Likely cause
"credentials missing" on every flow	LWA client id (username), client secret (password) or refresh token not set on the Connection tab
"Amazon returned no access token"	Refresh token invalid or revoked - re-authorise the application in Seller Central and paste the new token
"No marketplace mapping for Odoo warehouse..."	Add a warehouse mapping line pairing that warehouse with its marketplace id
"Product ... has no Internal Reference (SKU)"	MCF identifies products by seller SKU - set the Internal Reference to match the FBA SKU
Order lands on hold as Unfulfillable	No fulfillable FBA stock for that SKU in the order's marketplace
Return creation asks for a reason code	Set Default Return Reason Code in the Amazon Options

See also: Amazon MCF adapter - process maps for the end-to-end flow diagrams.

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