Industries - Retail & eCommerce
Channels multiply faster than the systems behind them.
Retail ERP and eCommerce integration is what stops each new channel inventing its own version of stock, price and customer. Add a marketplace, a wholesale line and click-and-collect, and omnichannel operations quickly outgrow spreadsheets. We connect channels, retail inventory management, fulfilment and accounting integration so availability is real, service is automated and margin includes the fees and freight usually left out.
At a glance
- Typical profile
- Multi-channel retailers, online sellers and brands with wholesale and direct lines.
- Most common constraint
- Separate stock positions per channel and margin reported before fees.
- Where we usually start
- Inventory synchronisation and automated order communication.
Operating model
Demand to margin.
Eight stages. Channel count multiplies the cost of every weak join.
Eight connected stages from acquisition to channel margin, built on one inventory truth and one customer record. Stock mismatches and returns branch to a person, and true channel margin returns to buying.
- 01
Demand and acquisition
Marketing · Demand, campaign
Paid, organic, marketplace and retail foot traffic, each with different acquisition cost and different data quality.
- 02
Order capture across channels
Storefront / channel · Order
Web store, marketplace, wholesale and in-store transactions arriving into systems that were never designed to agree with each other.
- 03
Inventory and availability
Inventory · Available stock
One physical stock pool promised across several channels, which is where most retail operational pain originates.
- 04
Purchasing and replenishment
Buying · Purchase order
Reorder decisions balancing lead time, seasonality and cash, usually made from exports rather than live data.
- 05
Fulfilment and despatch
Fulfilment · Shipment
Pick, pack, ship or click-and-collect, where cost per order is either measured or absorbed silently.
- 06
Customer service
Service · Customer enquiry
Where-is-my-order, availability and returns enquiries - high volume, highly automatable, and usually handled manually.
- 07
Returns and exchanges
Service / inventory · Return
A structural cost of online retail that deserves a designed process rather than an email thread.
- 08
Margin and channel reporting
Finance · Channel margin
True profitability by channel, product and customer once fees, freight and returns are included.
Stock mismatch or oversell
When a channel promises stock the warehouse does not have, the order is held for a person to substitute, refund or re-promise. The customer record and the inventory record stay in step.
Fees, freight and return rates return to buying and channel decisions so profitability is judged per channel and product rather than on gross revenue.
Constraints
Five constraints that cap retail margin.
01Stock truth split across channels
Separate stock numbers in the web store, marketplace and point of sale lead to oversells, cancellations and reputation damage during peak periods.
02Manual wholesale order entry alongside online orders
Retailers with a trade side often run two entirely different order processes, doubling admin and halving visibility.
03Channel fees and freight excluded from margin
Marketplace commission, payment fees, freight and returns are frequently omitted, so the products that look best are not always the ones earning money.
04Customer records fragmented by channel
The same person exists separately in the store system, the web store and the email platform, making retention work guesswork.
05Service enquiries answered by hand
Order status and returns questions consume service capacity that automated notifications and a self-service path would remove.
Automation
Automation that removes oversells and service load.
| Opportunity | What changes |
|---|---|
| Inventory synchronisation | One stock position feeding every channel with allocation rules, replacing periodic manual updates and oversell recovery. |
| Order and fulfilment flow | Orders from all channels landing in one queue with consistent picking, shipping and notification regardless of origin. |
| Order status communication | Confirmation, despatch and tracking notifications sent automatically, which removes the largest single category of service contact. |
| Returns workflow | Structured return authorisation, receipt and refund or exchange, with reason codes that accumulate into product insight. |
| Replenishment recommendations | Reorder proposals from actual sell-through, lead time and seasonality, presented as decisions rather than as spreadsheets. |
| Customer data unification | A single customer record across channels, making lifetime value and retention measurable rather than assumed. |
Where we start
Channels multiply faster than the systems behind them, and stock truth is the first casualty.
We start with the operating model, then choose platforms against it. If the model does not need a capability, we do not licence it.
Architecture
Storefronts sell. Operations decide truth.
Commerce and channels should own
Storefront and demand
- Product presentation and content
- Checkout, payment and promotions
- Marketplace and retail transactions
- Marketing campaigns and audiences
- Customer-facing service experience
ERP or operations should own
Stock, cost and fulfilment
- Master product data and pricing rules
- Single inventory position and allocation
- Purchasing, landed cost and valuation
- Fulfilment, despatch and returns processing
- Margin by product, channel and customer
Practical AI
Where AI fits a retail business.
Content, service drafting and pattern detection - always with review before customers see it.
Product content generation and enrichment
Draft descriptions, attributes and category mapping from supplier data, reviewed before publication rather than published blind.
Service response drafting
Order status, availability and returns replies composed from live data for an agent to review, which shortens response time without removing the human.
Demand and stock anomaly detection
Flagging products whose movement has changed materially, while there is still time to reorder or clear.
Supplier document processing
Purchase confirmations and invoices read and matched against orders, with variances queued for review.
Platform roles
Which system should own which job.
Shopify or your storefront as the sales channel
Storefronts should own presentation and checkout. They should not become the master of stock or cost once wholesale or multi-channel selling begins.
Odoo where operations outgrow the storefront
Purchasing, landed cost, multi-location inventory and wholesale pricing typically justify moving operational truth into an ERP.
Zoho for customer service and analytics
Service cases, customer history and cross-channel reporting fit well alongside commerce systems without duplicating stock data.
GoHighLevel where acquisition is the constraint
Retailers whose problem is repeat demand rather than operations may see faster return from marketing and follow-up automation.
Implementation
Four things that decide the outcome.
01Decide the system of record before integrating anything
Most retail integration failures are really unresolved ownership questions about product, price and stock.
02Never cut over during peak trading
Seasonality should dictate the go-live window. A quiet fortnight is worth more than an earlier date.
03Clean product data before connecting channels
Synchronising inconsistent SKUs, units and barcodes just distributes the problem faster.
04Plan for returns from the start
Returns are not an edge case in online retail. A process designed late becomes a permanent manual workaround.
Retail and eCommerce systems questions we are asked most
- Do we need retail ERP, or is Shopify plus accounting enough?
- A storefront plus accounting works well while there is one channel and simple stock. Retail ERP becomes worth the cost when purchasing, landed cost, multi-location inventory, wholesale pricing and returns all have to reconcile. The usual signal is stock accuracy problems and manual reconciliation between channels and the ledger.
- Do we need an ERP, or can our storefront and accounting software cope?
- Storefront plus accounting works well for single-channel sellers with straightforward stock. The signal to move is usually multi-channel selling, wholesale pricing, multi-location inventory or landed cost - the point where people maintain spreadsheets to answer questions the systems cannot.
- How do we stop overselling across channels?
- By establishing one authoritative stock position with allocation rules, and having every channel read from it rather than hold its own figure. Buffer stock is a workaround for a synchronisation problem, not a solution.
- What is the real margin picture we should be measuring?
- Product margin after channel fees, payment costs, freight and returns. Any of those omitted will systematically flatter certain channels and mislead purchasing decisions.
- Can wholesale and retail run in the same system?
- Yes, and generally they should share stock and product data. What differs is pricing, terms and order capture, which can be handled through customer pricing rules rather than a separate system.
- Where should a growing retailer start?
- Usually inventory synchronisation and automated order status communication. The first removes oversells, the second removes most service contacts, and neither requires a full platform decision.
Where to go next
Count last month's cancelled orders and refunded oversells.
That figure, plus the service time spent explaining them, is usually the business case for connecting inventory properly.