The native Amazon Connector maps important core processes. The 4EGrowth FBM Extension complements the accounting assignment, flexible inventory sources, controllable invoice and shipping data, as well as traceable error processes.
The short answer
The standard connects. The extension makes self-fulfillment controllable and analyzable.
The native connector
What Odoo already covers sensibly in the standard
The previous article referred to Odoo 16 and is outdated in several places. According to the currently published Odoo 19 documentation, the standard connector supports FBA and FBM, multiple accounts and marketplaces, the import of confirmed orders, the transfer of available FBM quantities, as well as shipping notifications with tracking data.
The final standard features of Odoo 20 will be reviewed again after the official release. The following differences mainly concern the additional professional configuration of the 4EGrowth extension.
4EGrowth FBM Extension
The most important extensions – based on their usefulness in daily operations
Manage accounting by marketplace country
Especially importantFor each marketplace country, a collective debtor or a defined standard customer can be stored. This allows for a conscious decision on how Amazon orders are booked and later evaluated in Odoo.
Cleanly assign sales and evaluations
Especially importantSales team and price list can be pre-set by marketplace country. This creates robust structures for revenue analysis, responsibilities, and commercial evaluations.
Make uploads and feedback visible
Invoices, inventory, and shipping data run through traceable processes. Transmission, feedback, and status become visible and trackable. The team recognizes what Amazon has accepted or rejected.
Use storage location or calculated field
For inventory uploads, a specific storage location or a calculated field can serve as the source. This allows for the representation of safety stocks, reservations, and custom availability logics.
Control invoice upload by country
Whether invoices need to be uploaded depends on the respective marketplace and process case. The extension allows for country-specific control and can deliberately exclude countries from the invoice upload.
Validate invoices before upload
Invoices are checked before or during transmission. Status and errors remain visible so that incomplete or rejected documents do not go unnoticed.
Assign warehouses and storage locations by marketplace
Each marketplace country can be assigned its own warehouse or a specific storage location. This separates orders and inventory cleanly and supports operational responsibility by market.
Identify and fix errors faster
Revised reports assign errors more accurately to an order, document, feed, or marketplace. This shortens error searching and supports correction and resubmission.
Visible instead of black box
A feed workflow must clearly show what has been transmitted
“Optimized feed workflow” is too abstract as a functional term. The result is crucial: The team can trace the relevant data flows, check their status, and assign errors to a specific process.
Check if an upload is necessary, validate the document, and track transmission and feedback.
Define inventory source, transfer quantities selectively, and identify rejected records.
Transmit carrier, tracking, and shipping confirmation and trace the feedback.
Taxes & Compliance
OSS and cross-border belong in the process design.
Amazon's own shipping across multiple European countries connects delivery route, marketplace, debtor, tax logic, and accounting. The 4EGrowth configuration reflects country- and marketplace-specific standard values, supports cross-border cases, and makes the allocation for OSS processes more understandable.
The gross sales tax can also be recorded according to the marketplace process so that order values and tax processing are consistently combined.
Standard and Extension
The difference lies in booking logic, configurability, and control
| Requirement | Native Connector | 4EGrowth FBM Extension |
|---|---|---|
| Import FBM orders | Basic process available | Controllable individual and batch processes with traceable status |
| Debtor per marketplace country | Limited account/marketplace configuration | Collective debtor or defined standard customer per marketplace country |
| Evaluation structure | Limited standard allocation | Sales team and price list per marketplace country |
| Upload inventory | Available quantity | Warehouse location or calculated field with its own inventory logic |
| Invoice upload per country | Not core to the documented order synchronization | Country-specific control, validation, and visible status |
| Shipping notification | Shipping and tracking are reported | Traceable transmission and error process |
| Errors and reports | Standard reports | Enhanced detection and more accurate assignment |
| OSS and cross-border | To design around taxes and fiscal positions | Simplified country and marketplace-related configuration |
Consciously delineated
FBM core module, FBA, and add-ons remain separate
Pan-EU and further FBA processes do not belong in the FBM extension. The same applies to lot and serial numbers, which are considered a separate add-on. This keeps transparent which function is included in self-shipping and which is needed additionally.
For FBA, Pan-EU, inventory movements, returns, billing, and other add-ons, a separate comprehensive Amazon connector page follows.
Before go-live
Six questions for a realistic FBM practical test
- Which collective debtor or standard customer applies per marketplace country?
- Which sales teams and price lists are needed for later evaluation?
- Do invoices need to be uploaded to Amazon – and for which countries?
- Which warehouse location or calculated field determines the Amazon inventory?
- How are cross-border and OSS cases distinguished technically and tax-wise?
- How does the team recognize, correct, and repeat erroneous invoice, inventory, and shipping transmissions?
Frequently asked questions
Odoo 20 Amazon FBM explained concisely
What is the most important difference to the standard connector?
The additional professional configurability: Debtors, sales teams, price lists, inventory sources, warehouses, invoice uploads, and error processes can be controlled by marketplace country.
Do invoices need to be uploaded to Amazon?
That depends on the marketplace, the chosen Amazon process, and the tax-related configuration. The extension can control the upload by country, validate invoices, and make status and errors visible. The specific obligation should be examined from a professional and tax perspective.
Can a calculated field be used as Amazon inventory?
Yes. In addition to a warehouse location, a calculated field can be used as the basis for the inventory upload.
Can each marketplace country receive its own standard data?
Yes. Collective debtor or standard customer, sales team, price list, as well as warehouse or storage location can be stored by marketplace country.
Is Pan-EU part of this FBM extension?
No. Pan-EU is professionally part of FBA and is treated on its own FBA or overall connector page.
Further information
Fully consider Amazon processes in Odoo
Next step
Configure Amazon self-shipping in Odoo 20 accurately and operationally.
We examine marketplaces, debtor logic, evaluation structures, inventory, stock sources, invoice uploads, shipping data, and tax cases and show which configuration and modules are actually needed for your FBM process.
Discuss Amazon FBM process