The AI Channel Sync Agent: How It Catches Price and Stock Drift in Odoo and MYOB Acumatica

Your ERP says three units in stock. Shopify says fourteen. A marketplace listing is still showing a promo price that ended a fortnight ago. Nobody changed anything on purpose, and every system involved is working exactly as it was configured to. This is channel drift, and if you sell through more than one channel, you have some of it right now.

An AI channel sync agent is a monitoring agent that reads prices, stock levels and product content across your ERP, your online store and your marketplaces, flags anything that doesn’t match, and drafts corrections for a person to approve. It doesn’t replace your connectors. It checks their work, and yours. MYOB’s ERP research found 45% of Australian decision-makers say disconnected systems limit growth, and channel drift is that problem in its most public form. It’s the version of your data your customers can see.

Why price and stock drift happens even when your connector works

Connectors move data on a schedule or in response to events, and they do it the same way every time. That predictability is the whole point. In our experience the drift almost never starts inside the connector. It starts at the edges:

• Edits made directly in the storefront. Someone fixes a price in the Shopify admin at 5pm to close a sale, means to update the ERP tomorrow, and doesn’t. The two systems now disagree, and the next sync may or may not put them back in step depending on which direction it pushes.
• Promotions that outlive their end date. A sale price gets loaded on the channel, the end date passes, and the full price never comes back because the promo was never in the ERP to begin with.
• SKU mismatches. Odoo’s Amazon Connector matches orders to products by internal reference, which is your SKU. Rename a SKU on one side and the matching quietly breaks for that product.
• Sync windows. MYOB’s eCommerce Connector pushes product, price and inventory updates manually or on a schedule. Between runs, the channels disagree by design. That’s fine, as long as someone knows how wide the window is.
• Fields no connector carries. Every integration has a scope. Whatever sits outside it, often product descriptions, images or channel-specific pricing, is maintained twice by hand, and hand-maintained data drifts.
• Warehouse corrections. A stocktake writes inventory down in the ERP after the morning sync has already told the marketplace there’s plenty available.

None of these are bugs. They’re the normal texture of running one product catalogue across three or four systems, which is why checking for drift is a standing job rather than a one-off cleanup.

How an AI channel sync agent actually works

The agent runs on a schedule, reads from each system through its API under its own limited credentials, and compares. Price in the ERP against price on each channel. Free-to-sell stock against displayed availability. SKU mappings against the product master. Where everything matches, it says nothing. Where something doesn’t, it flags the difference, proposes a correction, and waits.

Here’s a concrete morning from a setup like the ones we build. At 6:30am the agent compares a wholesale distributor’s ERP against their Shopify store and marketplace listings. It finds three exceptions. A promo price is still live on one SKU nine days after its end date. A product the stocktake wrote down to three units still shows fourteen available on the marketplace. And one SKU stopped matching entirely after a rename last week, so nothing has synced for it since. The agent drafts a summary with a proposed fix for each, sized in dollars: the promo SKU has sold 41 units below list since the end date. The channel manager reads it with coffee, approves the price restore and the stock correction, and holds the SKU rename for a quick check with the warehouse. The approved fixes go out through the normal connector, and every step is logged.

“The connector is almost never the thing that’s broken. Drift comes from the edges. A promo that never ended, a SKU renamed on one side, a stocktake that landed after the sync ran. The agent’s job is to notice fast and put a correction in front of a person, not to fire updates at three sales channels on its own.”

Josh Craig, Director, Auboros

Most of the tools marketed in this space promise the opposite: agents that detect mismatches and fix them automatically. We’d urge caution there. An agent with unattended write access to your prices and stock is a new way to be wrong at scale, and when it misreads a situation it will misread it on every channel at once. Drafts first, a person approves, always. It’s the same pattern we use for replenishment agents that draft purchase orders, and it costs you minutes a day.

Wrong prices online are a compliance problem in Australia

Drift isn’t just untidy. The ACCC requires businesses to display clear and accurate prices as a single total figure, including GST (Goods and Services Tax). If different prices for the same item are displayed in different places, the multiple pricing rules apply: sell at the lowest displayed price or withdraw the item until it’s corrected. And advertising a special price on stock you can’t actually supply in reasonable quantities can amount to bait advertising.

Notice that every one of those risks is exactly what drift produces. A promo price lingering on one channel is a multiple pricing problem. A marketplace showing availability the warehouse doesn’t have is an availability claim you can’t back. None of this is legal advice, and edge cases belong with your lawyer. The practical point is simpler: a daily drift check is cheap insurance against problems that are expensive to have.

Where Odoo and MYOB Acumatica are up to

Odoo

Odoo ships its own e-commerce platform, and for external channels the picture is connector by connector. The Amazon Connector (Enterprise) synchronises confirmed orders into Odoo and pushes available quantities back for merchant-fulfilled products, with a dedicated stock location tracking inventory in Amazon’s fulfilment centres. Shopify and WooCommerce run through third-party connectors, which vary widely in what they carry and how often; we covered the detail in our Shopify and WooCommerce integration guide.

One thing worth saying plainly, because we checked the v19 Enterprise source code: none of this synchronisation involves AI. There is no AI module touching stock or channel sync in Odoo 19. The connectors are deterministic, which is what you want from plumbing. The agent layer that watches for drift is something you add on top, reading through Odoo’s APIs under its own permissions.

MYOB Acumatica

MYOB’s eCommerce Connector brings Shopify and BigCommerce into MYOB Acumatica: product, price and inventory changes made in the ERP flow out to the storefront, and orders, customers and payments flow back in, with B2B features like customer-specific pricing supported. Globally, Acumatica offers native connectors for Amazon, Shopify and BigCommerce with real-time inventory synchronisation. As always with this platform, global Acumatica features typically reach the ANZ product 6 to 9 months later, so confirm what your MYOB Acumatica build includes before planning around it. For what the platform’s AI can and can’t do today, see our MYOB Acumatica AI guide.

On both platforms the honest summary is the same. The sync plumbing exists and works. The integrity checking layer, the thing that notices when reality and the storefront have parted ways, is not in the box. That’s the agent’s job.

How to run a channel sync agent safely

The Australian Bureau of Statistics found 12% of Australian businesses used AI in 2024-25, up from 1% two years earlier, and 22% of medium-sized businesses. Most of that adoption is still chatbots and content. Wiring an agent to your sales channels deserves more care:

• Start read-only. Run the agent for a fortnight with no write path at all. You’ll learn how much drift you actually have, and the reports build trust before anything can go wrong.
• Gate every write. Price changes and stock corrections are drafted, never fired. A named person approves each one, and the approval is part of the audit trail.
• Give it its own credentials. The agent reads through API keys scoped to exactly the data it needs, so you can see everything it touched and switch it off in one place.
• Log the misses too. When the agent flags something that turns out to be fine, record it. False positives are how you tune the thresholds.

We run agents on this pattern in production, for ourselves and for clients, and the governance is most of the work. The comparison logic is the easy part. Deciding who approves what, and proving afterwards what happened, is where an AI agent build succeeds or fails.

---

Selling through Shopify, BigCommerce or a marketplace alongside Odoo or MYOB Acumatica?

Auboros builds drafts-first AI agents over both platforms from Brisbane, working with businesses across Queensland and Australia. We can audit how much drift your channels are carrying today and scope an agent to keep it caught.

If your storefront and your ERP don’t always agree, book a free consultation. We’ll look at your channel setup together and tell you honestly whether an agent is worth it yet.