Checkout and My Account
Overview
Checkout and the My Account pages are theme containers, so your agent changes them through the same pull, validate, preview and push loop as any other page. It can restructure their layout and styling, for example a two-column checkout with an order summary that stays in view, or an account overview with a sidebar and recent orders.
The agent skill treats these pages as functional, not decorative. Before a change, the agent records every checkout or account element and its ID. It changes the layout around them, then compares them before and after, so forms, totals, payment fields and account actions keep working.
Example requests
- "Restructure the single-page checkout into two columns with a sticky order summary on the right. Keep every checkout element and its ID. Work on the inactive theme and do not use --live."
- "Give the My Account area a sidebar linking Orders, Subscriptions, Profile and Reviews, and match the store's fonts and colors. Show me a preview of the overview first."
- "Change the checkout label for the coupon field to 'Promo code'."
- "Render the order receipt with the latest test order so I can check the new layout."
Commands
| Command | What it does |
|---|---|
sf files list, sf pull, sf push | Find the theme's checkout and account containers, read them with a baseline, and write them back |
sf preview start, stage, open | Show the changed checkout or account page in your browser without saving it |
sf render --order latest-test | Render order and receipt elements with a test order |
sf orders test-orders | List the account's test orders; real customer orders are never listed |
sf i18n messages get, set, reset | Read and change the built-in messages checkout shows, such as field labels |
sf themes duplicate | Copy the active theme so the agent can work on an inactive copy |
How changes are checked
- On an inactive theme first. The agent works on a copy of the theme, previews it, and you activate the theme in the admin when you are ready.
- The cart, not only the page. For a buy box or checkout change, the agent checks that the cart it produces holds the right item, quantity, variation and price, in a browser opened through a preview link.
- Several states. The skill asks the agent to check the states a change can affect, such as a signed-in and a signed-out customer, conditional sections and modals, and desktop and phone widths. States it could not check are reported to you.
What it cannot do
- Place an order on a live store. The agent stops at the checkout page and never submits the checkout form on a live store.
- Create a test order without your say-so. It may create one only with your explicit authorization, on a storefront confirmed to be a test storefront, using its test payment method. Preview access alone does not authorize checkout.
- Change payment, shipping, tax or coupon settings. Those are done in the admin.
- Change the card number and CVV error messages. They come from the hosted payment fields, not from StoreFront messages.
What needs approval
None of the checkout or account layout commands are approval-gated. Writing the active theme needs --live and publish permission, and built-in message changes need --live and publish permission because shoppers see them at once. See Safety and human approval.
Related documentation
- StoreFront Checkout: the merchant guide to customizing checkout
- Test payments in UltraCart: placing test orders
- Pages and themes: the general page workflow