Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Amazon FBA & Multi-Channel Fulfillment Manager
A build-to-order Odoo module that manages Amazon FBA inbound shipment plans, routes non-Amazon channel orders through Multi-Channel Fulfillment (MCF), and reconciles FBA storage, removal and reimbursement transactions inside Odoo. ECOSIRE scopes, builds, installs and supports it for you.
$499.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
New `ecosire.fba.inbound.plan` / `ecosire.fba.inbound.line` models to create, submit and track FBA inbound shipment plans against Amazon shipment IDs, with received-vs-planned quantity variance
MCF order routing: an `ecosire.mcf.order` model that submits eligible non-Amazon `sale.order` lines to Amazon Multi-Channel Fulfillment and writes back fulfillment order ID, carrier and tracking
FBA inventory ledger sync into a dedicated `Amazon/FBA` `stock.location`, keeping `stock.quant` aligned with Amazon fulfillable, reserved and inbound quantities
Fee posting for FBA storage, long-term storage, removal, disposal and referral fees parsed from Amazon finance/inventory reports into their own records
Optional `account.move` bridge so FBA fees post as journal entries and finance sees true landed cost of fulfillment
Reimbursement claim tracking model with status workflow (eligible, filed, approved, credited) and shipment/SKU linkage for lost or damaged units
`@api.depends` computed fields for net FBA margin per SKU after referral and fulfillment fees, surfaced on `product.template`
Amazon SP-API integration on a scheduled `ir.cron` for report pulls, inventory sync and MCF submission, with retry and throttling handling
SKU/ASIN mapping layer linking Amazon listings to Odoo `product.product` via a dedicated mapping model (no hard-coded default codes)
`ir.model.access.csv` plus `ir.rule` record rules separating warehouse, finance and admin visibility, multi-company aware
OWL reconciliation dashboard summarizing inbound in-transit, MCF in-flight, unposted fees and open reimbursement claims
QWeb PDF reports for FBA monthly fee summary and printable reimbursement claim packets
`base.automation` rules that flag short-received inbound lines and stalled MCF orders for follow-up before Amazon claim windows close
Full data exposure over Odoo XML-RPC/JSON-RPC so external BI or middleware can read FBA, MCF and fee records
Built and tested against Odoo 17.0, 18.0 and 19.0, Community or Enterprise, with edition-aware accounting behavior
इस उत्पाद के बारे में
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?"
Amazon FBA & Multi-Channel Fulfillment Manager क्यों चुनें
New `ecosire.fba.inbound.plan` / `ecosire.fba.inbound.line` models to create, submit and track FBA inbound shipment plans against Amazon shipment IDs, with received-vs-planned quantity variance
MCF order routing: an `ecosire.mcf.order` model that submits eligible non-Amazon `sale.order` lines to Amazon Multi-Channel Fulfillment and writes back fulfillment order ID, carrier and tracking
FBA inventory ledger sync into a dedicated `Amazon/FBA` `stock.location`, keeping `stock.quant` aligned with Amazon fulfillable, reserved and inbound quantities
Fee posting for FBA storage, long-term storage, removal, disposal and referral fees parsed from Amazon finance/inventory reports into their own records
Optional `account.move` bridge so FBA fees post as journal entries and finance sees true landed cost of fulfillment
Reimbursement claim tracking model with status workflow (eligible, filed, approved, credited) and shipment/SKU linkage for lost or damaged units
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.
What you get
- Installable, version-pinned source code (the addon) built for your exact Odoo edition and version (17.0 / 18.0 / 19.0)
- Installation and configuration on your environment, including SP-API credential wiring, location mapping and `ir.cron` schedule setup
- Technical documentation: data model, `ir.model.access.csv`/record-rule matrix, SP-API endpoints used and cron/automation design
- End-user guide plus a live training session for your warehouse and finance teams
- UAT on a staging clone with a documented test plan and a rollback plan before production go-live
- Post-go-live support window for defect fixes and configuration questions
- Git repository handover with full commit history so you retain ownership and can extend it independently
Who this is for
FBA seller adding MCF
An Amazon FBA merchant who also sells on Shopify, eBay or their own site and wants Amazon to fulfill those orders via MCF. Needs one place to route those orders and confirm tracking without logging into Seller Central.
Operations / inventory lead
Manages inbound shipments and stock accuracy. Needs FBA inbound plans, received-vs-planned reconciliation and a real FBA quantity view inside Odoo's `stock` module rather than exported reports.
Finance / bookkeeping owner
Responsible for true margin and cost of goods. Needs FBA storage, referral and removal fees posted to `account.move` and reimbursement credits tracked so month-end reconciliation stops living in spreadsheets.
Multi-marketplace operator
Runs several Amazon marketplaces and channels and needs SKU/ASIN mapping, multi-company record rules and API access to feed downstream BI — a native Odoo home for the whole FBA/MCF picture.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Amazon FBA & Multi-Channel Fulfillment Manager module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Amazon FBA & Multi-Channel Fulfillment Manager, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Amazon FBA & Multi-Channel Fulfillment Manager Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fit to your FBA/MCF workflow | Built to your exact marketplaces, channels and edition | Fully bespoke but you carry all design decisions | Generic feature set, rarely covers MCF + fees together | |
| FBA inbound shipment plans | Dedicated models tracking planned vs received | Possible, if you spec and build it | Sometimes partial; often listing/order only | |
| MCF order routing | Routes non-Amazon orders to MCF with write-back | Buildable with SP-API effort | Uncommon; usually Amazon-order focused | |
| FBA fee reconciliation | Storage, removal, referral fees posted; optional `account.move` | Depends entirely on your build scope | Rarely reconciles fees to accounting | |
| Reimbursement claim tracking | Model with status workflow and SKU linkage | Only if explicitly built | Seldom included | |
| Support and ownership | Support window + full source + git handover | You own it but also maintain it | Vendor-locked, roadmap not yours | |
| Odoo 17/18/19 + edition awareness | Built and tested per your version and edition | Your responsibility to target and test | Version support varies by listing | |
| API access to the data | Standard models, full XML-RPC/JSON-RPC access | Yes, if designed that way | Usually, but schema is opaque |
Frequently Asked Questions about Amazon FBA & Multi-Channel Fulfillment Manager
+How long does delivery take?
This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how many marketplaces and MCF channels you run and whether the accounting bridge is in scope. The timeline is fixed once we agree the specification on the scoping call.
+Which Odoo versions and editions do you support?
We build against Odoo 17.0, 18.0 and 19.0, on both Community and Enterprise. Edition matters for the accounting bridge — Enterprise changes how FBA fees flow into `account.move` — so we confirm your exact version and edition before quoting and build the addon to match.
+What do I need to provide for the Amazon integration?
Access to Amazon's Selling Partner API (SP-API) for your seller account — we guide you through granting the developer/app authorization and the required roles (inventory, fulfillment, finance). Without SP-API access the module cannot sync inventory, route MCF or read fee reports.
+Does this replace my existing Amazon connector?
No. This is focused on the FBA and MCF fulfillment side — inbound plans, MCF routing, fee reconciliation and reimbursements. If you already run an order/listing connector we scope the integration boundary so they complement rather than fight each other over the same `product.product` and `sale.order` records.
+How are updates and support handled after go-live?
Every build includes a post-go-live support window for defect fixes and configuration help. Because you receive the full source and git repository, you own the code and can extend it yourself; we also offer ongoing support and version-upgrade engagements (for example when Amazon changes an SP-API endpoint or when you migrate Odoo versions) as a separate arrangement.
+Can other systems read the FBA and MCF data?
Yes. Everything is stored in normal Odoo models, so all FBA inbound, MCF and fee records are available over Odoo's XML-RPC/JSON-RPC API for your BI tools or middleware, in addition to the in-app OWL dashboard and QWeb reports.
+Will it handle multiple marketplaces and companies?
Yes. The SKU/ASIN mapping layer and `ir.rule` record rules are multi-company and multi-marketplace aware, so a group running several Amazon marketplaces keeps data correctly scoped per company and per warehouse team.
Related Modules
कोटेशन का अनुरोध करें
Amazon FBA & Multi-Channel Fulfillment Manager
A build-to-order Odoo module that manages Amazon FBA inbound shipment plans, routes non-Amazon channel orders through Multi-Channel Fulfillment (MCF), and reconciles FBA storage, removal and reimbursement transactions inside Odoo. ECOSIRE scopes, builds, installs and supports it for you.
- New `ecosire.fba.inbound.plan` / `ecosire.fba.inbound.line` models to create, submit and track FBA inbound shipment plans against Amazon shipment IDs, with received-vs-planned quantity variance
- MCF order routing: an `ecosire.mcf.order` model that submits eligible non-Amazon `sale.order` lines to Amazon Multi-Channel Fulfillment and writes back fulfillment order ID, carrier and tracking
- FBA inventory ledger sync into a dedicated `Amazon/FBA` `stock.location`, keeping `stock.quant` aligned with Amazon fulfillable, reserved and inbound quantities
- Fee posting for FBA storage, long-term storage, removal, disposal and referral fees parsed from Amazon finance/inventory reports into their own records