Documents your retailers accept. Data your ERP can trust.
ERP, EDI and AI consulting for wholesalers, distributors, manufacturers and the retailers they supply. Melbourne, led by Amit Bhardwaj.
Twenty minutes, bring one problem. Onsite across Melbourne, remote for the rest.
Quantonic works at the join between retail operations and the systems that run them: the product and price data inside the ERP, the documents that move between trading partners, and the interfaces that have to agree with each other.
- 16
- Years in IT
- 9
- Years in retail supply-chain systems
- 95%
- Of a national network's trade document flows, owned end to end
- 16,000+
- Cost updates in one month-end load
Earned in-house, as an employee. Former employers, not clients. There are no client results to show yet, so none are claimed.
Three practices, one accountable person.
ERP data
Product and price data that is right
Product and supplier master data, pricing and costing, promotions, hierarchies and ranging, bulk loads and month-end cost updates. Validation and load tooling so the data goes in right once. Data readiness, test scripts and cutover for an upgrade or a new module.
EDI
Documents your trading partners accept
Trading-partner onboarding and certification. The retailer's compliance guide read against your rejection history. Mapping specifications, partner and GLN set-up, rejections and chargebacks cleared at the cause rather than the symptom.
AI
The small things a busy team stops seeing
One AI job inside the workflow where the work already happens, proven against a measured baseline before it touches anything live: invoice-to-order mismatches, orders keyed by hand, answers lost in documents.
Built for the businesses that supply retail, and the retailers they supply
Industries where the work fits. Not a client list.
The situations that start a call
- A retailer has sent a non-compliance notice and the chargebacks are eating your margin.
- A new retailer wants purchase orders, ASNs and invoices by EDI by a date you cannot miss.
- The one person who understood your ERP data or your EDI mapping is leaving, or has left.
- Your ERP vendor wants you to upgrade and your product master and price file are a mess.
- Your ERP, your web store and your 3PL disagree about stock, price or orders, and someone reconciles them by hand every week.
- You are mid-implementation or mid-upgrade and nobody owns the data migration, the test scripts and the cutover.
Something near this? Twenty minutes on a call. Within two business days, a one-page written scope and quote, or a straight "not me" and a pointer to who can. Tell me the problem →
Which order model do you run?
Each one changes the document set, the structure of the ASN, the GLNs and the ERP configuration behind it. The first ten minutes of the call establish which you run and where it breaks.
DC replenishment
Bulk orders to the retailer's distribution centre; pallet, carton and item hierarchy on the ASN.
Direct to store
A purchase order and a delivery per store; a ship-to GLN and a customer record for every one.
Cross-dock, packed by store
One order to the DC with store allocations; cartons labelled and packed by store.
Drop ship
The retailer sells, you ship each parcel to the consumer; stock feeds, tracking and returns.
Consignment and scan-based
Stock stays yours until sold; sales reports in, invoice on sale.
3PL-fulfilled
Your ERP holds the order, a third-party warehouse ships; the ASN is built from their confirmation.
Group and multi-distributor
A head office orders for members, or distributors fulfil central orders; bill-to and ship-to come apart.
Web, marketplace and emailed
Orders outside EDI brought into the same pipeline, with the same acknowledgement and dispatch discipline.
Where the proof was earned
EDI, network side.
Four and a half years at a global cloud EDI network certifying retailer–supplier integrations: purchase orders, order responses, ASNs and invoices over AS2, SFTP and FTPS; XML and XSLT mapping faults; map development with third-party providers.
EDI, retailer side.
Four and a half years at a national store network as the EDI owner for 95 percent of its trade document flows across two networks: supplier onboarding and GLN set-up, purchase-order-response failures and rejections, the escalation point for every failed or delayed document.
ERP.
Owned that network's ERP product master and pricing engine: daily price loads to every store, RRP, future-dated and clearance pricing, supplier cost updates and month-end cost register loads of 16,000+ updates. Cut product master data errors by 25 percent in the first year with automated validation. Same-day recovery when 4,800 catalogue SKUs lost promotional pricing in every store.
Projects and change.
Led system and data projects from proposal to change board: the product-hierarchy rebuild from two tiers to four across the whole catalogue, a module through which stores respond to head-office offers, and a kit-sales reporting build with a 22-scenario UAT script. Six months as acting manager of the retail systems team.
Earned in-house, as an employee. Former employers, not clients. There are no client results to show yet, so none are claimed.
Twenty minutes, a written scope, weekly steps you can stop.
- Twenty minutes on a call
Five on your problem, five on what I would do, five on shape and rate, five on the next step.
- A written scope within two business days
One page: what I will do, what it costs, what it cannot do. Or a straight "not me" and a pointer to who can.
- Weekly steps you can stop
A short written note every week. Stop at the end of any week. You keep every account, document and mapping.
Insights
Short, practical pieces on EDI documents, product data, AI in the workflow and the places they break.
EDI vs API: is EDI still used, and what replaces it?
Retailers still send their suppliers EDI compliance guides. APIs have arrived beside EDI, not in place of it. What each one is, when a supplier meets which, and what has to be right either way.
Keeping AI honest: approvals, audit trail, change control. What a pharmaceutical maker's rules demand, and why every business should borrow three of them
A pharmaceutical maker cannot let an AI tool near a batch record without validation, an audit trail and change control. Three of those rules are worth borrowing by any business whose AI touches live data.
AI belongs inside the workflow, not beside it. A supplier's master-data check before the EDI send, where the work already happens
A separate AI tool is a second job, and second jobs are the first thing dropped. The check that works sits where the item is saved and the document leaves, in the screen your people already use.
In writing, before any work starts
- A written scope and price before any work starts
Fixed price for scoped work, a capped day rate for urgent or ongoing work, and a line saying what the work cannot do.
- Nothing goes live without your sign-off
I work in your test environment first. Every change has a written change note and a rollback step.
- Your accounts, your data, your documents
You create the accounts I use and can revoke them any time. Mappings, specs and test scripts are yours once paid for.
All seven commitments → None of this is a guarantee of a business result.
Bring one problem.
Twenty minutes on a call. Within two business days, a one-page written scope and quote, or a straight "not me" and a pointer to who can.