- Dry-run first, on every new storeA new instance simulates every job: no record changes in Odoo, nothing is sent to Bagisto, and each job keeps what it would have written. You untick Dry Run Mode when you have read the results.
- One Odoo stock behind the shopOdoo sends Bagisto what it can still sell of each product: the on-hand less what waits to go out, less a buffer, never below zero, to one inventory source. A sale confirmed in Odoo lowers it within about a minute.
- Orders that add up to Bagisto's totalLines at Bagisto's prices before tax, the shipping as a line of its own and what still differs (discounts, fees, rounding) as one named line; Bagisto's tax stays on the order.

bambooforge_bagisto_connector254 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.
How you use it
Four flows, in the order you will meet them
Connect: one instance per store, dry-run first
Test Connection proves the address and the account, and the first sync writes nothing.
- In Odoo: Bagisto Connector > Configuration > Instances > New. Enter the server's address and an admin user's email and password, or a token; Bagisto needs its bagisto/rest-api package.
- Press Test Connection. The state turns Connected and Configuration > Order State Mappings gets seven rows for the store; a failure sets Error, and Last Connection Error says why.
- On the Import tab press Queue Customer Import and Queue Product Import. Dry Run Mode is on: each job keeps what it would have written, and Operations > Validation Results lists what the checks found.
- Untick Dry Run Mode on the Safety tab and press the buttons again: the records are written, each with a Bagisto tab and a row under Configuration > Binders.

Every order status has a rule, and every order adds up
Bagisto gives each order a status; a table per store decides what Odoo does with it.
- Configuration > Order State Mappings holds the statuses Bagisto uses, each with Keep draft, Confirm sale order, Cancel sale order or Ignore; an administrator changes a row or adds one.
- An imported order is confirmed, cancelled or left as a quotation by the row of its status; a status with no row is ignored.
- With Match Storefront Totals on, the shipping is a line of its own and what still differs one named line; the total the order had to reach and the difference left stay on its Bagisto tab.

One Odoo stock behind the store
Odoo sends the store what it can still sell; a sale in Odoo lowers the figure.
- Tick Stock Export Enabled on the Import tab and choose the Stock Source Warehouse, or leave it empty for the whole company.
- A stock move in Odoo starts the push within about a minute, and it runs every 30 minutes: for each bound product, the on-hand less what waits to go out, less the buffer, never below zero, to one Bagisto inventory source.
- Bagisto's API gives no stock to read, so the figure goes one way: from Odoo to Bagisto.
A failed job lands in a list, not in silence
Every import, export and stock push is a queue job with its retries.
- A job that fails waits and is tried again with a growing wait; five failures in a row pause the store until it is healthy again.
- Dead-letter lists the jobs that will not run again by themselves; Requeue Jobs sends them back once the cause is fixed.
- Control Tower shows each store's health, backlog, dead letters and conflicts on one card.
Price and where to buy
199 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:
Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.
