
A maintenance buyer assembles a basket of replacement parts, then sends screenshots to a manager for approval. The manager agrees by email. When the buyer returns to checkout, the price or availability has changed. The supplier receives an order with a purchase order number, but no reliable record of which version the manager approved.
For Australian and New Zealand trade retailers, wholesalers and distributors, purchasing approval can be the missing step between a usable catalogue and an order that a business customer can place online. The investment decision is whether your store should manage that approval, submit orders for your own team to review, or connect with the customer’s procurement system.
Start with who is making the decision and what they are authorising. A purchase order reference can help reconcile a transaction. It provides little evidence on its own about spending authority, approval conditions or whether the basket has changed.
Key Takeaways
- Identify who approves the purchase and what the decision authorises.
- Test thresholds, changed baskets and unavailable approvers.
- Preserve the accepted request through the ERP handoff.
Identify the decision that is holding up the order
Interview a few customers who still email baskets or call an account manager before ordering. Ask them to walk through a recent purchase. Who selected the goods, who approved the spend, and where was the approval recorded? Include a routine replenishment and an exception such as a high-value or urgent purchase.
Distinguish buyer approval from seller review. A buyer’s manager might authorise expenditure, while the supplier checks availability, price or account status. Both decisions can be necessary, with different owners and different evidence. If a store labels both as “awaiting approval”, customer service may struggle to explain what happens next.
Identify the event that creates a committed order under your operating process. A buyer submitting a request may expect review before any obligation or payment. A supplier receiving the same record may treat it as ready to dispatch. Agree on the meaning of each stage and make the button labels, emails and ERP records consistent.
Use the first workshop to produce a short decision map. For every stage, name the actor, required information, allowed changes and next action. This gives a platform demonstration a concrete purpose and helps reveal whether the current problem is a missing workflow or an unclear commercial policy.
Choose where approval should happen
A workflow within the commerce account can fit customers whose purchasing process is straightforward and who are comfortable managing users there. The buyer selects goods, an authorised colleague reviews the request, and the approved version proceeds through the supported order process. Confirm how the supplier and customer will maintain those roles.
Supplier review can work when the merchant must confirm commercial details before accepting an order. It can support assisted purchasing, but it does not establish that the customer’s manager approved the spend. OSE’s B2B quote-to-order guide explains the related decision of when a purchase needs a reviewed offer.
An integration with the customer’s procurement system deserves consideration when that system already owns approval, budgets and purchase orders. The customer may want to build a basket on the supplier’s catalogue and return it to procurement for authorisation. Establish the required process with that customer before selecting a connector or promising compatibility. OSE’s Coupa integration guide explains one procurement integration context, including the distinction between catalogue and document exchange.
Avoid making every customer adopt the same model. A smaller trade business may need direct ordering by one authorised person, while a national account needs a procurement handoff. Segment the first release around a valuable, supportable buying process. Supporting several models is justified only when your team can explain and operate each one.
Define the approval rules before choosing software

Document the conditions that trigger review. These might include basket value, product category, branch, buyer role or an exception to the usual delivery location. State whether the condition applies to the whole request or selected lines. Use customer-approved examples instead of assuming that all accounts apply the same threshold.
Specify what the amount includes. A threshold based on merchandise value may behave differently when freight, tax or a surcharge is added. For a business buying in different currencies, agree which amount and currency the rule evaluates. Finance and procurement should approve these definitions before implementation.
For an illustrative NZD 2,000 threshold, test requests below, exactly at and above that value. Then add freight that takes the total across the boundary. The expected outcome depends on the agreed rule. These figures are test inputs, rather than a recommended limit or a description of an OSE customer.
Decide how several rules interact. Does a restricted item always need a specialist approver? Must all nominated people agree, or can one person authorise the request? What happens if the same person qualifies as buyer and approver? Ask the implementation team to demonstrate the required behaviour rather than infer it from a feature name.
Keep the approver’s view specific and complete

An approver needs to see the purchasing context, including the company location, selected products and quantities, applicable price, delivery details and relevant references. Include enough product information to distinguish a pack from an individual item. A total alone can conceal a quantity or variant mistake.
Show what the action does. “Approve request” should make clear whether it sends the request to another reviewer, creates an order, or permits the buyer to complete payment. Rejection should give the requester a useful explanation and an agreed route to correct or replace the request.
Give buyers a way to see progress without repeatedly submitting the same basket. Identify the outstanding decision in language the customer understands. Keep internal notes separate from information intended for the customer. A status page is useful only if the people handling enquiries can explain it consistently.
Plan for unavailable approvers. Define how a company updates responsibilities when someone changes role or leaves. Any delegation should follow the customer’s authorised process and preserve a record of who made the decision. Set up an escalation route for an urgent purchase before the first blocked request arrives.
Recheck the request when something changes
An approval applies to a particular commercial request. Define what happens when the product, quantity, price, delivery location or payment arrangement changes afterwards. Some changes may require renewed approval. Others may be allowed within an agreed policy. The system needs a way to recognise the difference.
Consider a fictional request approved for ten units. If the buyer increases the quantity to fifteen, the original approval should not silently authorise the increase unless that is explicitly allowed. Preserve the earlier request and show the changed version to the responsible reviewer. The expected result belongs in the acceptance test.
Availability also needs a policy. Establish whether a pending request reserves stock and, if so, for how long. An approval workflow should not imply a reservation that the stock system never made. Explain how a delayed approval affects price validity and delivery expectations.
A substitute product can create another decision. The supplier may offer an equivalent, but the customer might need a technical or financial review before accepting it. Keep the original request, replacement offer and final accepted lines distinguishable through the supported workflow. Avoid relying on an email that the order system cannot associate with the revised basket.
Compare Adobe Commerce and Shopify against the same cases
Adobe Commerce documents purchase order approval rules for B2B companies. Its guidance describes customer roles and company structure in configuring manager approval. This gives a starting point for a buyer-side workflow. Validate the required conditions, permissions and storefront behaviour in the intended Adobe deployment.
Adobe’s purchase order flow documentation also explains how orders follow the PO process when purchase orders are enabled for a company. Test the path with the payment methods and integrations your customers actually use. A demonstration with an administrator’s permissions does not prove what an ordinary buyer can do.
Shopify documents B2B checkout settings that submit orders as drafts for merchant review. That is a relevant capability when your own team needs to confirm the order. For a customer-side manager hierarchy, establish what the complete solution requires, including any application or development.
Treat a PO number field, seller draft review and buyer spending approval as separate capabilities during evaluation. Ask providers to show the buyer, manager and merchant sessions for the same request. Compare who maintains the rules, how exceptions are supported and how the ERP receives the accepted outcome.
Preserve the accepted decision in the ERP handoff

Agree which system holds the authoritative approval record and which reference travels with the order. Include the company, location, request version and accepted lines, plus the relevant decision reference where supported. Dispatch and finance need enough context to recognise that the order followed the approved process.
Define whether an unapproved request enters the ERP and, if it does, what prevents it from releasing stock or triggering fulfilment prematurely. Some businesses may prefer to send only accepted orders. Others need earlier visibility. Choose the pattern from operational requirements and the capabilities of the deployed systems.
Handle retries as part of the workflow. If the ERP accepts an order but the response is delayed, the integration should recognise the same accepted request when processing resumes. A second click or repeated approval notification should not create another sales order. Agree how staff reconcile a request that is approved online but has no confirmed ERP result.
Credit and account holds remain another commercial check. Customer approval to spend does not establish permission to charge a supplier account. Follow the rules your finance team owns and decide how an affected buyer proceeds. OSE’s B2B credit limits and ERP guide covers that decision and the relevant handoffs.
Pilot one complete purchasing journey
Start with one customer group and a limited set of rules. Use representative orders, named buyer and approver roles, and expected outcomes signed off by the customer and merchant. Include a request that needs no review, one that crosses a threshold, a rejection, a changed basket and an unavailable approver.
Follow each case through the final accepted order and ERP acknowledgement. Check emails, account status, payment and the record available to customer service. Ask the buyer and approver to describe what they believe happened. A workflow that staff understand differently needs clearer labels or a revised process before expansion.
Measure time from a complete request to an accepted order, manual follow-ups, duplicate submissions and corrections caused by changed baskets. Compare similar requests before and after the pilot. Account for product availability and customer purchasing cycles when interpreting the results. Workflow usage alone does not establish incremental revenue.
OSE can help map the buying journey, evaluate platform fit and define the ERP handoff. A useful scope should identify decision owners, acceptance examples and support responsibilities before development starts. Bring your customer’s approval policy and sample requests to a B2B discovery discussion so the proposed implementation follows the process you need to support.
Frequently asked questions
A reference can help reconcile an order, but the approval evidence depends on the customer’s process. Establish who authorises the request, which version they accept and where the decision is recorded. Do not infer that evidence solely from a populated reference field.
They involve different decision owners. Merchant review lets the supplier check an order, while customer approval lets an authorised person within the buying business review the purchase. Some transactions need both stages. Label and test each one explicitly.
Adobe documents B2B company purchase order workflows and approval rules. Confirm the behaviour in your deployed product, company structure and configuration. Test the required thresholds, roles, payment methods and ERP handoff with representative requests before committing to the design.
Define which changes require another decision under the customer’s policy. Preserve the approved version and identify the revised request. Quantity, price, substitute products and delivery changes should be covered in acceptance examples so staff can explain the resulting action.
Consider that model when procurement already controls budgets, authorisation and purchase orders, and the customer wants to retain that process. Agree the catalogue and basket handoff with the customer, then validate the supported integration rather than assuming every connector provides it.