What was actually wrong
Nutri Advanced needed a commerce platform that supported the Health & wellness business model and the trading patterns of its customers.
This was not a brochure storefront. Buyers arriving for a specific item needed enough product information and context to identify it with confidence, while stock, account pricing and purchase history had to support the same buying decision.
Order flow, stock and customer data crossed several back-office systems, so integration boundaries and operational handoffs likely shaped how the platform was built.
Stock was not one flat number. Depot location, availability and fulfilment context had to remain meaningful so customers and order teams could rely on what the platform showed.
Business customers also needed the platform to reflect how they buy: parent and child account relationships, repeat purchase, order history, account documents and the correct pricing and stock context.
The commerce layer had to sit cleanly alongside ERP, without turning every operational dependency into a launch risk.
What was at stake
Unclear product, pricing or fulfilment information can create friction before an order is placed.
Most relevant to Health & wellness teams weighing similar platform decisions.
If catalogue and operational data drift, buyers can lose confidence in product information, pricing, stock and purchase history. That can delay or abandon an order, while internal teams absorb the uncertainty through manual checking and customer service.
For repeat buyers and trade accounts, uncertainty creates friction every time an order is placed again. Wrong-part risk, unclear account terms and a harder repeat-order path can frustrate buyers and move the burden back to account teams and support.
Once a buying habit moves elsewhere it is expensive to win back. The consequence of inaction is not dramatic; it is cumulative.
Five things, in order.
- 01Mapped the buying journey before the interfaceStarted with how customers actually order on this site, then let the journey shape the interface decisions, not the other way round.
- 02Rebuilt the commerce foundation around how the business operatesRebuilt the commerce foundation around the operational logic the business already depended on, without resetting what already worked.
- 03Connected the systems that the storefront cannot work withoutThe commerce layer had to sit cleanly alongside ERP without coupling the launch to every system on day one.
- 04Scoped the rules per audience, not per platformAccount-led ordering and self-serve buying were shaped as distinct journeys on the same foundation. Local catalogue, depot, inventory, delivery and pricing rules had to remain coherent for the buyer context in front of the screen.
- 05Moved the project into support with the operating context intactHandover preserved the operational decisions made during build, so support could keep moving the platform forward without re-learning the business.
Platforms and integrations
Difficult parts
Results
In the client's words
iWeb created a meaningful user-facing digital experience that can be utilised by consumers and health professionals to provide inspiration, deliver additional product information, and guarantee exposure to a broad product range.”
Ongoing support
The project did not end when the platform went live.
Support mattered because the health and wellness still depended on parts data, pricing imports, account behaviour, inventory feeds, integrations and customer-facing information after launch.
Keeping the build decisions and system ownership visible gave the support team a clearer basis for tracing issues and maintaining the connected trading system after launch.










