Your retailer's EDI documents accepted. Your product and price data right.
Quantonic is a Melbourne consultancy led by Amit Bhardwaj. ERP and EDI for wholesalers, distributors, manufacturers and the retailers they supply: the product and price data inside the ERP, the documents that move between you and your trading partners, and the interfaces in between.
Twenty minutes, bring one problem. Onsite across Melbourne, remote for the rest.
Your trading partners
- Purchase order
- Order response
- Advance ship notice
- Invoice
Your ERP
- Items, GTINs and hierarchy
- Suppliers, customers and their GLNs
- Costs, RRP and promotions
- Orders, stock and ranging
I work at the arrows: the master data, the mappings and the tests that make a document accept first time and a price land in every store once.
Call me when…
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 →
What I do
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.
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.
Interfaces that agree with each other
The links between ERP, EDI, web store, 3PL or WMS and store systems: interface specifications, data-flow documentation, exception handling, and the SQL and Power BI reporting that shows whether it is working.
How it is delivered: the scope, the test script and the change request written down, taken through your change control, with a short note every week. When it is bigger than one person, I write the scope and run the test and the change with your ERP's own partner.
Four ways to start
ERP and EDI health check · three days
Your retailers' compliance guides and your last 90 days of rejections and chargebacks, read against your product master, GLNs and price file. On day three you hold a written findings list, what it is costing you, three fixes you can make this month and a costed fix plan.
Retailer EDI onboarding sprint · per trading partner
Purchase order, order response, ASN and invoice mapped to the retailer's specification, a test run of real orders with you watching, certification passed, first production documents accepted, a one-page runbook.
Product and price data clean-up · before an upgrade, migration or new channel
Items, hierarchy, GTINs, GLNs, costs, RRP and promotional pricing validated, an exception list with owners, a cleaned file loaded to your test system and signed off, a validation template you keep.
Implementation, upgrade and incident support · by the day
A senior pair of hands for the data, the test scripts and the cutover of an ERP implementation or upgrade. Fix-and-resend when a retailer rejects a day's documents. Cover at your desk when your ERP or EDI person is away. Written cap, weekly invoices.
No price is printed here. The shape and the rate are said on the first call and written down before any work starts. The engagements in detail →
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.
How it starts
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.
Proof
- 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.
From the blog
Short, practical pieces on EDI documents, product data and the places they break.
Master data is the orphan: the ERP-side work nobody owns
Practitioners on SAP, JD Edwards, SYSPRO, Infor and Acumatica describe the same EDI failures in different vocabularies. Nearly all of them are a unit code, a location number, a part number or a pack level in the wrong place, owned by no one.
When EDI only arrives through an adaptor: SYSPRO, MYOB Acumatica, Cin7 and the others
Many of the ERPs Australian suppliers run have no translator of their own. EDI arrives through a partner adaptor, and the adaptor's choice of door decides how upgrades, licences and failures behave.
No ERP does EDI alone: what users of fourteen ERPs say
I read what the people who run SAP, NetSuite, Dynamics, Epicor, Acumatica, Odoo, IFS, Infor, JD Edwards and SYSPRO say about EDI in their own forums. The ERP opens a door, something else does the EDI, and the ASN is where it hurts.
What I commit to
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.
Who you are dealing with
Amit Bhardwaj, founder and principal consultant. Sixteen years in IT, nine of them in retail supply-chain systems: four and a half years certifying retailer–supplier EDI at a global network, then four and a half years owning the ERP product master, the pricing engine and the EDI lifecycle for a national store network, six of those months as acting manager of the team.
Quantonic is new, and it is one accountable person. The person who scopes the work does the work. Where I bring in a specialist, they work under my contract and my supervision, and you know who before any work starts.
More about Amit and Quantonic →Contact
Seabrook, Melbourne