Read the current draft back against an approved order brief before staff submit it. Match product identity, pack size and unit, then reconcile every cart row with every approved line. Check combined quantities where products repeat. Missing, extra, ambiguous or unreadable lines must remain unresolved until a named person handles them. Give staff the comparison record and current draft; entering the intended number alone does not prove the order is correct.
Define exactly what the approved quantity means
The brief should identify each product, variant, quantity, unit and relevant pack size. “Order twelve” leaves room for disagreement when a supplier offers individual items and cartons. Give each approved line a reference so staff can trace it to the corresponding cart rows.
Keep the approved wording and brief version. If a conversion is needed, the purchasing owner must approve the relationship between units and packs. The agent should not invent a conversion or round up to meet a minimum order.
Also specify whether repeated products represent separate requirements, such as different delivery destinations. Combining them without that context could preserve the total while changing the order's meaning.
Establish where preparation stops
Inspect the actual portal flow before authorising preparation. Determine which actions change a draft and which commit an order. A button labelled “Continue” needs checking just as much as one labelled “Submit”. If preparation cannot be separated from commitment, staff should handle that step.
OpenAI's changelog records the addition of computer use to the Agents API on 29 September 2026, with website access approvals and sign-in handled by the application. That dated announcement does not establish purchasing authority or eligibility for your account. Check current product, plan and region eligibility before deployment. Source: OpenAI API changelog
The verification process below is a proposed workflow to build and check against your portal. Keep final submission with authorised staff, and specify whether the agent may correct draft fields or must report discrepancies without changing them.
Reconcile the whole cart before checking each number
Start with the complete draft, including rows already present before the agent began. Map every approved brief line to its cart row or rows, and every cart row back to the brief. An unmapped brief line is missing; an unmapped cart row is extra. Both need explicit handling.
For repeated products, compare the combined quantity in approved units. Also check each row's destination, variant and delivery choice before deciding whether rows belong together. A correct aggregate cannot justify an unapproved split across destinations.
Do not silently delete extras or merge duplicates. The purchasing owner decides whether they are mistakes or intended separate lines. After an authorised correction, reconcile the complete cart again. Checking only the edited row could leave another duplicate behind.
Read what the portal retained
After entry, let the portal finish validation or recalculation, then read the displayed quantity and unit. Move away from the field if the inspected portal requires that to apply an edit. Compare the retained value with the brief rather than relying on the agent's account of what it typed.
OpenAI's function-calling guide separates a model's requested tool action from execution by application code. In this proposed workflow, keep the same distinction between intended entry and observed result. Source: OpenAI function calling
Read the product identity beside that quantity. Check relevant dates, destination, price and currency where the brief requires them. A recalculated total may help explain the draft, but it does not grant permission to spend.
If labels move, identifiers become clipped or a selector changes, pause the affected check. Recover a readable view or hand it to staff; do not assume the old screen position still identifies the same field.
Use this pre-submission verification script
This template is a proposed operating rule. Its completion condition is a reviewable draft and an explicit disposition for every discrepancy. Staff still decide whether submission is appropriate.
Pre-submission order verification script
Brief reference/version: ______ | Supplier/account: ______ | Draft reference: ______ Prepared by: ______ | Verification time: ______ | Staff reviewer: ______ Permitted draft corrections: ______ | Purchasing owner: ______
- Confirm the supplier, account and delivery destination against the approved brief. Stop before any action that commits an order.
- Inspect the complete cart. Map every approved brief line to cart rows and every cart row to an approved line.
- Record missing lines, extra rows and repeated products. Compare aggregate quantities in approved units, preserving destination and variant distinctions.
- Ask the purchasing owner to resolve ambiguous duplicates, substitutions or pack conversions. Do not silently merge, delete or reinterpret them.
- After entry and portal validation, read back each product identifier, variant, quantity, unit and pack size. Check other fields required by the brief.
- Complete both records below. Use matched, different or unknown; an unreadable value is unknown.
- Assign every discrepancy a named resolution owner. Record unresolved, or resolved with the decision, authority and supporting evidence.
- Make only authorised corrections, then repeat the full reconciliation and affected field checks. Changed draft values or layouts invalidate affected earlier checks.
- Give staff the current draft, records and evidence references. Unresolved required checks block a ready-for-submission recommendation.
- Staff inspect the current values and decide whether to submit. The agent stops before final submission.
Line reconciliation record , repeat for every brief line and every unmatched cart row
| Brief line | Cart row(s) | Product/variant and destination | Expected total and unit | Observed aggregate and unit | Missing, extra or duplicate issue | Evidence reference |
|---|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ | ______ |
Field and resolution record , repeat for every checked field or line issue
| Line/row and field | Expected value | Observed value | State | Evidence reference | Uncertainty or difference | Named resolution owner | Disposition and decision evidence |
|---|---|---|---|---|---|---|---|
| ______ | ______ | ______ | matched / different / unknown | ______ | ______ | ______ | unresolved / resolved: ______ |
Final handoff: ready for staff's submission decision / blocked: ______ Outstanding issues and owners: ______ | Staff review time: ______
Verification records draft accuracy; it does not approve expenditure or prove an order was placed.
Work through ordinary and exception cases
All identifiers, quantities and pack sizes below are hypothetical. The handling rules are proposed, rather than measured results.
Ordinary draft: Brief line A requests twelve individual items of product P, for one destination. The complete cart contains one matching row displaying twelve individual items after validation. Staff record the identity, unit and quantity as matched, reconcile the remaining brief lines, then inspect the current draft before deciding whether to submit.
Wrong pack: The same hypothetical brief meets a row showing twelve cartons, each containing six items. That represents seventy-two individual items. Record different, with the visible pack label as evidence. The purchasing owner confirms the permitted conversion or selects the correct unit; the agent does not assume that two cartons are acceptable.
Duplicate and extra rows: A hypothetical brief requests twelve individual items of P. The cart has two P rows, each displaying twelve, plus an unrelated item Q left from earlier preparation. The aggregate is twenty-four P items, and Q has no approved line. Staff mark both issues unresolved. The purchasing owner authorises the intended correction, after which the whole cart is reconciled again.
Missing or ambiguous information: A hypothetical brief line has no cart match, while another row's clipped identifier could refer to either of two variants. Record the absent line as missing and the identity as unknown. Staff obtain the full identifier and confirm the intended product before preparation continues. An unavailable delivery field remains unknown rather than inheriting a previous order's date.
Keep the handoff valid until staff submit
A comparison belongs to a particular brief and draft state. Another staff member's cart edit or a portal refresh can make it stale. Record what changed and recheck the affected fields, including aggregate quantities when rows change.
Evidence references should lead staff to a readable field view or draft reference. Keep enough context to distinguish identical products on separate rows without capturing unrelated account information.
Structured Outputs can constrain the format of a model's response. That supports a consistent comparison record, but format alone does not prove the observed quantity is accurate. Staff still need inspectable evidence. Source: OpenAI Structured Outputs
Pilot the script with rejected entries, duplicate rows and changed layouts. A useful blocked handoff identifies the unresolved field, its evidence and the person who must decide what happens next.
FAQ about verifying browser-entered quantities
Can two matching rows still produce a wrong order?
Yes. Each row might match the requested quantity while their combined quantity exceeds it. Reconcile the complete cart and compare aggregates using approved units and destination distinctions.
What should staff do when a quantity field is unreadable?
Mark it unknown and block the readiness recommendation. Obtain a readable current view or have staff inspect the field directly, then record the resolution and evidence.
Does a matched record let the agent submit?
No. Under this workflow, staff inspect the current draft and retain the submission decision. Any intervening changes require the relevant checks again.
For implementation options, read the custom-agent workflow guide, agents versus automation comparison and custom AI agent definition.
If your business needs help applying this script to a supplier portal, explore Custom AI agents and AI automation, or get in touch to discuss the draft and staff handoff.