If you sell on Amazon FBA, your true inventory and cost picture lives in Seller Central, not in Odoo. Odoo core gives you a clean stock.warehouse, stock.quant and product.template model, but it has no concept of an FBA fulfillment center, no inbound shipment plan workflow, and no way to see the storage, long-term-storage, removal and referral fees that Amazon silently deducts. Sellers who also want Amazon to fulfill their Shopify, eBay or website orders via MCF end up copying tracking numbers by hand and reconciling FBA settlement reports in a spreadsheet at month-end. The gap widens the moment you cross into multiple marketplaces or run MCF, because there is no native place to answer "what is my real landed margin after FBA fees?"

ECOSIRE builds a dedicated module that models the Amazon fulfillment side natively in Odoo. We add new models such as ecosire.fba.inbound.plan and ecosire.fba.inbound.line to create and track inbound shipment plans against your Amazon shipment IDs, plus an ecosire.mcf.order model that routes eligible non-Amazon sales orders to Amazon's MCF and writes back the fulfillment order ID, carrier and tracking. FBA inventory is synced into a mapped Odoo location (an Amazon/FBA sub-location of stock.location) so stock.quant reflects Amazon's fulfillable, reserved and inbound quantities via @api.depends computed fields. Fee events — storage, long-term storage, removals, disposals and reimbursements — are parsed from Amazon's finance and inventory reports and posted as their own records, with an optional bridge to account.move so finance sees the real cost of fulfillment.

Technically it is a standard Odoo addon: a versioned __manifest__.py declaring dependencies on stock, sale and (where you use it) account; access control through ir.model.access.csv plus ir.rule record rules so warehouse and finance teams see only what they should; list, form and kanban views in XML with OWL components for the reconciliation dashboard; and a QWeb PDF report for FBA fee summaries and reimbursement claims. Integration with Amazon uses the Selling Partner API (SP-API) on a scheduled ir.cron, and everything we build is also reachable over Odoo's own XML-RPC/JSON-RPC API so your other systems can read the same data. Automated actions (base.automation) can, for example, flag any inbound line received short so you can open a reimbursement claim before Amazon's window closes.

Because this is build-to-order, nothing is a black box you download and hope fits. We start with a short scoping call to confirm your marketplaces, MCF channels, SP-API access and Community-vs-Enterprise edition, then build the module against your exact Odoo version (17.0, 18.0 or 19.0). Community and Enterprise differ — Enterprise's accounting and studio-adjacent features change how we bridge fees to account.move, and we account for that up front. You receive the full source, we install it on your staging environment for UAT, and we go live only after you sign off, with a support window and a clean git repository handover so you are never locked to us.