If you run a butcher shop, deli or fresh food store on Wedderburn scales with Atria Manager, your product data already lives in one place: PLU codes, prices, stock, even the label text. The problem is getting that data onto a website without retyping everything and keeping two systems in sync by hand. We built the EUX Atria Connector to solve exactly that, and it now runs production WooCommerce stores for butchers across Australia. This post explains how it works.
What Atria Manager is (and is not)
Wedderburn’s ecosystem has a few parts that are often confused. Atria Manager is the back office: it holds your product file, sends price updates to your Digi scales, and manages customers and loyalty. Atria POS is the till software. The connector integrates with Atria Manager, which means you do not need Atria POS to sell online: a store running Atria Manager with Digi scales is fully supported.
The architecture: what flows where
The connector sits between Atria and WooCommerce and moves data in both directions on different triggers. Product data flows down on a schedule (every 15 minutes by default, the same cadence Atria uses to push prices to your scales). Orders and customers flow up the moment they happen.
Pick a scenario to watch it move:
Interactive: pick a sync scenario
Two details worth knowing from production: the Atria appliance must support TLS 1.2 for the connector to establish its secure connection (older appliance configs need updating first), and every run writes to a sync log inside WordPress, so you can check whether a specific price update went through.
The field mappings
These are the real mappings the connector uses, straight from our handover documentation:
Interactive: explore the mappings
| Atria field | WooCommerce field | Notes |
|---|---|---|
PLUCode | SKU | The reference key linking both systems |
EcommerceDescription | Product title | Also ItemText type 1031 |
EcommerceUnitPrice | Sale price | Can be overridden online-only, e.g. to cover picking costs |
EcommerceRrpPrice | Regular price | Set RRP higher than unit price to show a sale online |
Inventories[].OnHand | Stock quantity | Multiple inventories are summed |
IsWeighed | Unit of measure (kg or pcs) | Drives weighed-product behaviour |
ItemText[Type=10] | Long description | The online description from the Ecommerce tab |
ItemText[Type=8] | Country of origin | Plus types 1033 ingredients, 1034 storage |
ItemLabelImages[ImageBoxNo=7] | Product image | Upload images in Atria before the first sync |
ParentPLUCode | Parent SKU | Builds variable products with ParentConversions as attributes |
| WooCommerce field | Atria field | Notes |
|---|---|---|
| Order ID | CustomerOrderReference | The reference key for order updates |
| Line item SKU | OrderItems[].PluCode | With quantity, unit of measure and line number |
| Chosen attributes | OrderItems[].Comment | Selected sauce, dressing, cut preferences |
| Pickup or delivery | Delivered | Plus PickupTime for the selected slot |
| Coupons | PluCode 900001 line | Discounts appear as a dedicated line item in Atria |
| Customer note | Notes | |
| Fulfilment | Status: Filled | Marking Filled in Atria completes the Woo order |
| WooCommerce field | Atria field | Notes |
|---|---|---|
| Billing email | Email | The reference key for customers |
| Name and phone | Name, LastName, Phone | |
| Shipping address | Address[] | Billing address is used for pickup orders |
| Atria customer ID | id | Stored against the Woo customer, links loyalty |
| Loyalty points | Customer balance | Synced on schedule or on demand for campaigns |
Create once, update carefully
The most important design decision in the connector: product creation and product update sync different fields. When a PLU does not exist in WooCommerce, the connector creates the product in full. From then on, updates only touch prices, stock and the product name. That means your marketing team can rewrite descriptions, add photography and tune SEO in WooCommerce without the next sync overwriting their work.
Weighed products deserve their own post
Meat is sold by the kilo but ordered online as “2 rump steaks”. The connector carries the unit of measure (kg or pieces) and unit weight down from Atria so WooCommerce can estimate totals, and the final weighed amount flows back after packing. Combined with an authorise-then-capture payment flow, the customer is charged for exactly what the scales say. We cover both patterns in detail in separate posts on selling by weight and payment capture for weighed goods.
FAQ
How often does it sync?
Products, prices and stock sync on a schedule, every 15 minutes by default, and the interval is configurable. Orders and customers push to Atria immediately.
Do I need Atria POS, or is Atria Manager enough?
Atria Manager is enough. The connector talks to Atria Manager, so stores running Manager with Digi scales and no Atria POS tills are fully supported.
Can the website price differ from the shelf price?
Yes. By default the ecommerce unit price follows the store price, but it can be overridden per product for an online-only price, and the RRP field displays sale pricing online.
What about Shopify?
The same integration pattern applies, and Wedderburn connects both platforms. We are WooCommerce specialists, so if you are choosing a platform for a scales-driven store, we recommend talking to us first, as weighed-product checkout works quite differently across platforms.
Selling online with Wedderburn equipment
EUX is a WooCommerce Pro Partner, one of only three in Australia, and we have taken multiple Wedderburn-equipped stores online end to end: connector, click and collect, delivery zones, SMS notifications and payments. Talk to us about your store, or explore our WooCommerce integration services.
