Yes AI. AI consulting for Australian businesses.
Forms and calculators require JavaScript. You can still read this page and contact us by phone or email.
Call (03) 9003 0111 | hello@yesai.au
Interactive controls are loading. Phone and email links are available.
An order is copied into several systems within minutes of being placed: the ERP, the warehouse or 3PL, perhaps a drop ship supplier, a carrier booking and a customer messaging tool. Then the customer emails to change the address, swap a size or cancel one item. Someone edits the order in the store admin and assumes that is the end of it. In many stacks the edit stays exactly where it was made.
A large share of off the shelf connectors sync order creation reliably and treat everything after it as out of scope. The result is a parcel sent to the old address, the wrong size picked, a cancelled item shipped and invoiced, or stock that stays reserved for an order that no longer exists. This page covers the change types that matter, how far through fulfilment each can safely go, how payments and GST documents should follow, and the integration patterns that make changes reliable.
These are design gaps, not staff mistakes. Each one appears in stacks that otherwise run well.
Many integrations listen for a new order event and copy the order downstream once. Edits, line removals and cancellations raise different events, or none at all, and the connector ignores them. Before designing anything, check what your current connector does when an order is edited after export. Often the honest answer is nothing, and that single fact explains a lot of mysterious fulfilment errors.
A change is easy before picking starts, awkward once items are in a tote, and impossible to apply as an edit once the parcel is manifested with the carrier. The ERP, the warehouse and the 3PL each have their own version of that point. Without knowing where the order is, the person making the change cannot know whether it will take effect, and nor can the customer.
A common workaround is to cancel the original order and create a new one with the changes. It works until a system misses the cancellation, and then both orders ship. It also breaks the link between payment, invoice and fulfilment, which makes refunds and reconciliation harder. Versioned changes to the same order are safer, where the systems allow them.
Changing an order’s value means either charging the customer more or refunding part of the payment, and if a tax invoice has already been issued, the accounting side may need a credit or adjustment document rather than a quietly edited invoice. If the integration updates the order but not the money, the ledger and the payment provider disagree until someone finds it at reconciliation.
Six design elements. Together they let a customer service agent make a change once and know exactly what happened to it everywhere.
One system owns the order, usually the ecommerce platform or an order management layer, and every change creates a new version with what changed, who changed it and why. Downstream systems receive the change rather than a new order. Each system confirms which version it holds, so a mismatch can be spotted and corrected before it ships.
The warehouse or 3PL status is brought back to the order record in near real time: released, picking, packed, manifested, dispatched. The agent sees it before making a change, and the system can refuse an edit that is past the cut off for that change type, offering the right alternative instead of accepting an edit that will not happen.
Address changes, item swaps, quantity changes, shipping upgrades and cancellations each get their own cut off. Before picking: edit directly. Between picking and manifest: send a change request to the warehouse and wait for confirmation. After dispatch: carrier redirect where the carrier offers it, or return and reship. Agents follow the same rules every time because the system enforces them.
Cancelling one line of a multi line order is the change most often mishandled. The line is cancelled in every system holding it, the stock reservation is released, a split shipment is adjusted if part has already gone, drop ship suppliers are told if the line was theirs, and the right amount is refunded including any shipping or discount that was apportioned to that line.
Value increases trigger an additional payment request or charge against a stored payment method, according to your policy. Decreases trigger a partial refund against the original payment. If the invoice has already been posted, the accounting entry follows your agreed approach, typically a credit note or adjustment note rather than an edit, so the GST position in each BAS period stays correct.
If a downstream system rejects or does not confirm a change within a set time, the agent who made it and the operations team are alerted with the order, the change and the system involved. Address changes after an order is placed are also checked against fraud signals, because changing the destination of an already paid order is a known pattern in account takeover fraud.
If your site or agents say an order can be changed until it ships, but the warehouse cannot change orders once picking starts, customers will be told something untrue. Representations about your service are covered by the Australian Consumer Law. Set the published policy from the real cut off points, and let the system tell agents when a change is no longer possible.
Rewriting an invoice that has already been posted, or included in a lodged BAS, makes the GST record unreliable. Changes after posting should generate the appropriate credit or adjustment documents in the period they occur. For business customers that may include issuing an adjustment note. Agree the approach with your accountant and build the integration to it.
Partial refunds calculated by hand often get apportioned shipping, discounts, gift card portions and buy now pay later plans wrong. The refund should be calculated by the same logic that priced the order, and sent back to the original payment methods in the right proportions, so payment reconciliation does not inherit the error.
Cancelled lines that leave a reservation behind reduce sellable stock silently. Over a busy season it adds up to real lost sales. Every cancellation path should release stock in every system that reserved it, and a daily check should compare open reservations against open orders.
Changing the delivery address of a paid order is a common step in account takeover fraud. Require the change to come from the verified account or contact details, check it against your fraud signals, and treat changes to a different state or a parcel forwarding address with extra care.
Some ecommerce platforms and ERP connectors now support order edits natively and pass them downstream correctly. Test yours with real changes before building anything. If the only gap is one change type or one downstream system, the right fix may be small and the rest of this page unnecessary.
We run each change type through your live stack in a test environment and record what every system does. Most clients are surprised by at least one result, and the test report is yours to keep.
We work with your warehouse or 3PL to set real cut off points per change type, then make sure your published policy and agent scripts match them.
Change propagation, confirmations and alerts run on a managed cloud automation layer we operate, with a log of every change and every system’s response.
Additional charges, partial refunds and accounting documents designed with your finance team and accountant so the ledger, the payment provider and the order always agree.
Five steps. Address changes and full cancellations are usually reliable within four to six weeks, with item edits following.
Address, item, quantity, shipping, partial and full cancellation, run through the real stack, with the result in each system recorded.
Which system owns the order, the cut off for each change type in each fulfilment path, and what happens after it.
Changes sent as versions with confirmation from each system, and fulfilment status returned to the order record.
Additional charges, partial refunds and accounting documents following each change automatically.
Alerts on unconfirmed changes, a weekly report of changes by type and outcome, then marketplaces and drop ship suppliers.
Why event handling decides whether changes arrive.
The core order flow that changes have to follow.
Getting changes and cancellations to your logistics provider.
Where the cut off points actually sit.
What happens when a change comes too late.
Holding suspect orders and risky address changes.
Most likely because your integration only sends orders when they are created. Edits raise a different event, or require the integration to check for changes, and many connectors do neither. Test it: edit a test order after it has been exported and see what each downstream system shows. If nothing changes, the gap is in the integration design, not in what your staff did.
Only if your systems cannot handle edits at all, and then with care. Cancel and recreate risks both orders shipping if any system misses the cancellation, and it separates the new order from the original payment. Versioned changes to the same order, confirmed by each downstream system, are safer where your platform and logistics provider support them.
Not as an edit to the order, because the parcel is already in the carrier’s network. Some carriers offer redirection, sometimes for a fee and sometimes only before a certain stage. Otherwise the options are return and reship or delivery as addressed. The integration should know which carrier and service the parcel is with so the agent can offer the right option immediately.
There is no general cooling off or change of mind right for online purchases under the Australian Consumer Law, with exceptions such as unsolicited consumer agreements. Your own published cancellation policy, however, is part of what you have promised and must be honoured, and if you cannot supply what was ordered the customer is entitled to a refund. This is general information, not legal advice.
If no tax invoice has been issued, the order can usually be adjusted and invoiced at the final value. If an invoice has already been issued or posted, the change is normally recorded as an adjustment in the period it occurs, with a credit or adjustment note where required, rather than by rewriting the original. Confirm the approach for your business with your accountant.
This is where manual refunds most often go wrong. An order level discount or free shipping threshold may have been apportioned across lines, and cancelling one line can change whether the remaining order still qualifies. Decide your policy, then have the integration calculate the refund with the same logic that priced the order, so the amount is consistent and explainable.
Address changes and full cancellations through one fulfilment path are typically reliable in four to six weeks, including testing with the warehouse or 3PL. Item edits, partial cancellations with refunds, and additional fulfilment paths such as drop ship suppliers and marketplaces follow in later phases. The time depends heavily on what your logistics provider’s system can accept.
Book a call. We test how your current stack handles each kind of order change, show you exactly where edits are lost, and give you a priced plan to fix it. The test results are yours either way.
All discussions held in confidence. Australian-based consultants.