Fulfilment and carrier integration
Warehouse and shipping wired directly into the store so dispatch stops being a manual re-entry step. For Polaclub that was integration with the carrier, replacing hand-worked fulfilment.
Ecommerce automation for stores where growth now costs staff hours.
Norml automates the work around the order — fulfilment, carriers, reviews, support, reporting — so volume stops being a staffing problem. We start from where your team actually spends its hours, not from a list of integrations.
A few clients we’ve worked with
The store scaled. The operations behind it did not.
Every order is touched by hand somewhere between checkout and dispatch.
Review requests go out when someone remembers, so the store has far fewer reviews than orders.
The same product questions arrive daily and a person answers each one.
Stock, orders and the accounting figures live in different places and get reconciled manually.
Ad spend rose and nobody can say which product or campaign actually paid.
What our Ecommerce automation services include.
We map the order lifecycle as it runs today and price each automation against the hours it removes. Integrations follow from that; we do not connect a tool because it is available.
Review collection
Automatic review requests over email and SMS, timed to delivery rather than to order, so the volume of reviews tracks the volume of sales.
Support assistants
An assistant answering from your live FAQ and product catalogue, on your own provider key, handling the repeat questions and handing the rest to a person.
Order routing and notifications
Orders and enquiries into the CRM or helpdesk with the right tags and owner, with immediate notification and staged follow-up.
Data consolidation and reporting
Store, payment and ad data pulled into one place so revenue and margin can be read per product and per campaign.
Monitoring
Alerts when an integration silently stops, because the expensive automation failure is the one nobody notices for a fortnight.
Ecommerce automation deliverables.
The agreed scope identifies which of these deliverables your project needs.
- 01
A map of the order lifecycle with the manual steps and their cost named.
- 02
The agreed automations, built against your real tools and accounts.
- 03
A support assistant answering from your live catalogue, where that is in scope.
- 04
Consolidated reporting by product and campaign.
- 05
Failure alerts and a documented recovery path.
- 06
Handover documentation, including what each automation must not be trusted with.
Our process
How our Ecommerce automation process works.
Map
Follow a real order end to end and count the manual touches. You get the diagnosis before any tool is chosen.
[ 01 ]
Prioritize
Rank the automations by hours removed against build cost, and drop the ones that do not pay.
[ 02 ]
Build
Implement against your live systems, one automation at a time, each verified before the next.
[ 03 ]
Instrument
Reporting and failure alerts, configured as part of the build rather than afterwards.
[ 04 ]
Hand over
Accounts in your name, documentation, and a session with the people who will run it.
[ 05 ]Ecommerce automation questions.
Where does ecommerce automation usually pay back fastest?
Fulfilment and review collection, in that order, because both scale linearly with orders and both are pure staff time today. Support automation pays next. Reporting pays slowest but changes the most decisions.
Which platform does this need?
Most of our commerce work is WooCommerce on WordPress, where the order lifecycle is open enough to automate properly rather than patch. Other platforms are possible; what changes is the implementation route, not the method.
Will an AI assistant give customers wrong answers?
It can, which is why it answers from your own catalogue and FAQ rather than from general knowledge, and why anything outside that goes to a person. We also measure and publish what these assistants cost and where they fail, because the failure mode is a confident wrong answer rather than an obvious error.
Do you replace our accounting software?
No. We organize the data — orders, payments, ad spend — so it can be reported and planned against. The accounting itself stays where it is.
Can this be done without rebuilding the store?
Usually yes. Automation sits around the existing store, and we would rather add it to a working store than bundle it into a redesign nobody asked for.
Website 2.0 combines strategy, design, development and launch in one engagement; automation is scoped separately against the hours it removes.