Ecommerce orders to AutoCount
Short answer: Ecommerce orders from Shopify, WooCommerce, Shopee, Lazada or a custom website can be sent into AutoCount automatically. The important part is mapping item codes, customer rules, stock timing, payments, cancellations and exceptions before syncing live orders.
Why ecommerce teams outgrow manual keying
Manual keying works when order volume is low. It breaks when the business starts receiving orders from multiple channels.
Common symptoms:
- Admin spends hours creating invoices from online orders
- Stock in AutoCount is not updated until later
- Website stock and warehouse stock disagree
- SKU names differ between platforms and AutoCount
- Refunds, cancellations and returns are handled manually
- Finance needs extra cleanup before closing the month
At this point, ecommerce growth creates back-office drag. Integration removes that drag.
What should sync into AutoCount
The exact document depends on your workflow. Some businesses create sales orders first. Others create invoices after payment or fulfilment.
Typical data mapping includes:
| Ecommerce data | AutoCount decision |
|---|---|
| Order number | External reference or document reference |
| SKU | Item code mapping |
| Customer | Debtor rule, cash sales rule or customer creation |
| Shipping fee | Item, GL or separate line |
| Discounts and vouchers | Discount handling and reporting rule |
| Payment method | Clearing account or payment status |
| Fulfilment status | When stock should move |
| Cancellation or return | Reversal or credit process |
The AutoCount ecommerce sync service covers the build pattern in more detail.
Website, marketplace or both
Different channels need different rules.
- Shopify or WooCommerce usually gives more control over fields, checkout and customer records.
- Shopee and Lazada require platform-specific mapping for vouchers, fees and settlement.
- Custom ecommerce systems can be shaped around your own workflow but need clear API documentation.
- Multi-channel setups need one stock rule so all platforms do not oversell the same inventory.
If your business is already operating as a fulfilment workflow, see ecommerce fulfilment systems.
The safest first phase
For most companies, the first phase should not cover every edge case. It should cover the highest-volume order path, with an exception queue for anything unusual.
Start with:
- Clean SKU mapping
- One document type
- One or two sales channels
- Clear duplicate prevention
- Exception review before posting bad records
Then expand to returns, bundles, special pricing, branch stock and reporting.
FAQ
Can ecommerce orders create invoices automatically in AutoCount?
Yes, but it depends on your accounting process. Some businesses prefer sales orders first, then invoices after fulfilment or payment confirmation.
What happens if a SKU does not match AutoCount?
The order should be held in an exception queue until the mapping is fixed. It should not post with a guessed item code.
Can this sync stock back to the ecommerce store?
Yes, but two-way stock sync needs careful rules so warehouse, AutoCount and ecommerce do not overwrite each other incorrectly.
Check My Ecommerce Sync