PURCHASE WORKFLOW
Agent checkout
Agent checkout is a purchase workflow in which software interprets purchase instructions, applies limits, performs checkout work, and returns an order result. It can use APIs, tools, or browser automation.
AGENT CHECKOUT / BROWSER CONTROL
Agent checkout vs browser automation
Use agent checkout when the main goal is a completed purchase with product constraints, checkout states, and a separate payment approval step. Use browser automation when the main goal is to control a website interface. The two methods can work together: an agent checkout system can use browser automation as one part of its checkout process.
- RESPONSIBLE ORGANIZATION
- Shopstack
- LAST CHECKED
02
DEFINITIONS
EXECUTION METHOD
Browser automation
Browser automation controls a browser to open pages, select elements, enter text, and read results. It is a general method. It does not by itself define purchase rules, approval, or the required order result.
03
DECISION MATRIX
SIDE-BY-SIDE
Different layers, different jobs.
These methods are not direct replacements. One defines a purchase workflow. The other controls a browser.
| DECISION POINT | AGENT CHECKOUT | BROWSER AUTOMATION |
|---|---|---|
| 01Primary purpose | Complete a purchase under stated limits. | Operate a website interface. |
| 02Typical input | A product URL, customer data, and purchase constraints. | A sequence of UI steps or a goal for the browser. |
| 03Scope | Purchase policy, checkout state, help, and order result. | Clicks, text input, page reads, and browser navigation. |
| 04Navigation | The checkout layer can use APIs, tools, or a browser. | The browser layer opens pages and operates the website UI. |
| 05Recovery | Checkout state shows if the system must wait, ask, or stop. | The product team must define retry and recovery rules. |
| 06Sensitive fields | Routes protected input through a typed user boundary. | The product team must define how it handles protected data. |
| 07Exact-total decision | The user approves or rejects the exact amount separately. | Browser control does not by itself authorize a payment. |
| 08State | Canonical checkout states tell the application what to do. | Page state and action results describe the browser session. |
| 09Reconciliation | Returns the checkout result that the merchant makes available. | The product team must define its order record and result. |
| 10Best fit | Products that must offer a controlled purchase workflow. | Testing, data entry, and other general website tasks. |
04
USE-CASE GUIDE
SELECT A LAYER
Start with the result that you need.
- 01
Choose agent checkout
Use it when the product must accept purchase constraints, manage checkout state, request help, and return an order result.
- 02
Choose browser automation
Use it when the product must test a site, enter data, or do a general UI task that has no purchase-specific lifecycle.
- 03
Use both
Let the commerce layer own purchase rules and state. Let the browser layer operate merchant pages when a browser is necessary.
05
CONTROL BOUNDARY
SHOPSTACK LIMIT
Browser activity is not payment approval.
Shopstack is a checkout execution layer for AI agents. It can pause for help or payment approval. Activity and intent describe current work. They are not extra checkout states, and they do not grant payment authority. A message cannot approve payment. Final authorization must enter through the separate, trusted payment approval boundary.
queuedstartedhelp_requiredapproval_requiredsubmittingcompletefailedcancelled
Shopstack uses these eight checkout states. activity and intent are progress information only.
Limits of this comparison
- This guide compares system roles. It does not measure speed, merchant coverage, or checkout success rate.
- Merchant pages and checkout rules can change. Results depend on the merchant, item, location, and purchase request.
- This page does not claim that Shopstack supports every merchant or every website exception.
06
PRIMARY SOURCES
CHECKED AUGUST 28, 2026
Definitions and control rules.
READY TO BUILD
Give your agent a purchase workflow.
Start with the public setup. Keep payment approval at its trusted boundary.
READ THE SETUP GUIDE