Order Addendum lets government buyers on Mbizmarket increase or reduce quantities on an order that’s already running. The seller just accepts or declines, and the addendum document writes itself.
Real screen from the Addendum design file. All company and user data is fictional.
The only way to change a running order was to cancel it and reorder, even when part of the goods had already shipped.
One request with a final-quantity field, the legal +10% limit shown before you hit it, a simple accept-or-decline for sellers, and an auto-generated, e-signed document.
No more cancel-and-reorder just to change a quantity, with every change on record and capped by the regulation.
in orders that didn’t need to be cancelled, because the quantity can change on the same PO.
of admin per addendum: paper and wet signatures became a generated document with e-signatures.
on average to fill in a request, because the +10% cap is visible right in the form.
Government orders often need adjusting once they’re running: what arrived turns out to be enough, or the need grows. Before Addendum, the only option was to cancel and reorder, even when part of the goods had already shipped.
Commitment officers or managers who request the change.
Store admins who accept or decline within a deadline.
Keep an eye on every addendum from the admin panel.
An addendum isn’t just editing a number. The order may be in transit, some goods already received, an invoice already out, and any change to a government contract’s value is capped by regulation. The design had to keep this safe for both sides and still auditable.
Under Perpres 46/2025, Article 54. The rule doesn’t cap reductions, so the system limits them to 99%.
The new quantity can’t go below what’s been received, and shipping and invoices have to follow once it’s agreed.
While it’s pending, other actions on the order are locked so data doesn’t collide, like complaints or receipt confirmation.
Buyers adjust orders without starting over, sellers just decide, and Mbizmarket keeps deals moving on the platform.
A normal UX process, but every step was checked against order status, invoices and regulation.
I mapped why buyers cancelled orders, and what happened to goods already shipped and invoices already issued.
Buyer and seller flows with five addendum statuses, including the deadline and what’s locked while waiting.
One pattern across every touchpoint: buyer and seller web, mobile, admin panel, email and the printed document.
Failure scenarios checked one by one, especially things happening at the same time, then fixed before handoff.
“Today Addendum only changes quantities. The pattern is ready for what comes next.”
The next most-requested changes are delivery schedule and price. The pattern can stay the same: a limit you can see from the start, one decision from the seller, and a document the system writes for you.
Real screens from the Addendum design file. All data is fictional.
