Skip to content

Latest commit

 

History

History
558 lines (348 loc) · 225 KB

CONTRACT.md

File metadata and controls

558 lines (348 loc) · 225 KB

Stall target product contract

Product target

Target approved scope: 16 October 2026. First buyer: a US small retailer or maker selling physical goods in USD through an owned branded online store.

Stall replaces the online-store job sold by Shopify, Squarespace Commerce, BigCommerce and WooCommerce: build and merchandise a store, attract and convert shoppers, take payment, deliver orders, support returns and account for the result. Medusa, Saleor and Fourthwall are additional switching/extension reference points. This is the product being built towards, not a description of the current release. No homepage, UI or running behavior changes are authorized by this document round.

The core records are stores/themes/pages, collections/products/variants/media/custom fields, stock modes/store-managed quantities/stock-provider mappings/holds, carts/quotes, customers/consent/storefront event preferences, promotions/gift balances, tax/delivery quotes, orders/payments, shipments/returns/exchanges/refunds, messages, channel listings, accounting postings and attributable work history. Every record has an explicit store, identity, revision/state and permission boundary appropriate to its job. Historical imports retain provenance and never become current payment or stock authority.

A single switching journey runs from migration and domain cutover through catalog discovery, checkout, fulfillment, service, return and reconciled books. The clauses specify buyer behavior and the public-door evidence needed to call it complete. Provider test environments/network-edge fakes establish local logic only; live account, domain, carrier, wallet-device and hosted delivery acceptance must be recorded separately. Fixtures are test-only; production has no invented stock, orders, provider success or fallback service.

Category Ecommerce platforms (online storefronts)
Incumbents a buyer switches from Shopify, Squarespace Commerce, BigCommerce, WooCommerce, Medusa, Saleor, Fourthwall
First buyer A US small retailer or maker selling physical goods in USD through an owned branded online store

Published clauses

  • HTTP-001 — Real installed and published HTTP surfaces. The emitted Worker serves health, real assets, the installed Lobby, shop documents and genuine HTTP/document 404s. The independent marketing homepage, /run and /docs remain the Markdown-derived run site; its Run actions lead to /run. The RER operations contract in SEED-COMMAND-CONTRACT.md remains binding. Build and deploy never run tests.

    Acceptance evidence: Build and serve the emitted Worker; GET /health, /, /shop and built assets, then unknown document/API paths. Verify successful responses and real 404 status codes; build the run site and follow its public links.

Target clauses

Runtime and store experience

  • DEMO-001 — Hosted demo shop that sends nothing. The homepage's "Try the demo" link opens a hosted demo of the current release (https://demo.run-stall.com/), deployed from this repository's main branch with rer deploy --demo. The production demo keeps its real human (Turnstile) check; hosted automated sample-shop acceptance uses a separately admitted hosted test host with test keys at the same SHA. The production start page alone never counts as sample-shop proof. It holds a lived-in sample US shop seeded once after its owner exists: catalog and stock, weeks of orders in every state, a refund awaiting a person's approval, product drafts, an agent credential and the audit trail. A visitor can buy from the public shop and approve the desk's prepared shipment and refund drafts; payment, stock and mail run against the demo's own simulated Stripe and Pier and Base demo mode, so no request reaches a real provider and no mail is delivered. Demo data and simulated providers exist only under demo mode: a production build or deploy refuses RER_DEMO, and an ordinary installation starts with empty real business state.

    Acceptance evidence: Follow the built homepage's Try the demo link to the production entry, verify a 200 response and see the real human (Turnstile) check. Then, on the separately admitted hosted test host with test keys at the same SHA, verify the sample shop, buy from the public shop, approve the prepared refund and a packed order's shipment, and invite a teammate; verify the order is paid and reserved, the refund and dispatch succeed against the simulated providers, and no outbound provider request or mail leaves. Attempt a production build and deploy with RER_DEMO=1 and verify refusal; start a fresh installation and verify it holds no demo record.

  • STORE-001 — Merchant themes, page builder and custom domain. A merchant chooses a starter theme from a theme library, duplicates it and edits logo, colors, typography, navigation, reusable sections and responsive page templates. An unpublished theme or revision is previewable through a staff preview link; the merchant publishes, switches or rolls back themes without losing pages, menus, collections, products or orders, because content and catalog are stored independently of any theme. The complete theme source and assets export as a documented archive and re-import into the same or another store, with validation that names unsupported or missing sections instead of silently dropping them. A storefront password hides the shop before launch or during migration staging while staff preview keeps working. The merchant connects an owned domain with verified DNS, TLS and canonical redirects. Published themes serve resized, cached images, and the reference theme is measured against Google's "good" Core Web Vitals thresholds at phone width rather than assumed fast.

    Acceptance evidence: In the merchant desk pick a starter theme from the library, create a reusable hero/product section, preview it on desktop and phone, and publish to a verified test domain. Switch to a second library theme and back, confirm every page, menu, collection, product link and order survives, and roll back a revision. Export the theme source and assets, re-import them into an empty store and compare the rendered pages; import a damaged archive and verify a named refusal. Enable the storefront password and confirm public pages, sitemap and feeds are withheld while staff preview works. Follow HTTPS and www/canonical redirects, and record a Core Web Vitals run of the reference theme at 390 pixels.

  • STORE-002 — Navigation, collections and product discovery. Shoppers browse menus, manual or rule-based collections and category landing pages, search product names/SKUs/attributes, and filter/sort by price, availability, variant attributes and collection. Results, counts, empty states and shareable URLs agree with published, sellable catalog data; unpublished products stay private. Search offers predictive suggestions as the shopper types, and merchants tune it with synonyms (for example "tee" and "t-shirt"), boosted or pinned products for a query, and a search report of top queries and queries with no results.

    Current discovery semantics: /shop is the browse and search page and its address holds the whole view (q, collection, category, tag, attr.<name>, option.<name>, min, max, available, sort, page). Results are the published products Pier lists as sellable, 24 per page, with facet counts that apply every other filter; options, price and in-stock are matched on one variant together. A category or collection page is that address with a collection title and description. Search matches words and word prefixes in names, SKUs (including variants'), categories, tags, attributes, variant options and descriptions, widened by synonym groups (terms stored lowercased without punctuation); a pinned product leads its query and still obeys filters, and a boosted product leads other matches. Suggestions start at two characters and never include a product that is not public. The report keeps only normalized query text with counts, never a person, session or address, for up to 5,000 different queries. Menus have two levels and leave out destinations that are not published. Collections, menus, synonyms and pins are changed only by a signed-in owner or administrator, never an agent. ANALYTICS-001 inherits consented session analytics, STORE-001 theme presentation, and STORE-003 search-engine visibility (sitemaps and structured data).

    Acceptance evidence: Publish a varied catalog, navigate collections, search and combine filters on desktop and phone. Change publication and stock, refresh the public results, and verify matching counts, saved URLs and a useful no-results state. Add a synonym and a pinned product for a query and verify both change results; search a term with no results and find it in the search report.

  • STORE-003 — Content, blog, contact, newsletter and search visibility. Merchants manage content pages, blog posts, policies, menus, product/collection SEO titles and descriptions, image alt text, canonical URLs, sitemap, robots policy, social previews, structured product data and permanent redirects. Draft/scheduled content is previewable and changes retain publication history. Moving a product URL preserves discovery through redirects. Every theme includes a contact page whose form delivers each submission, with optional order number, to the store's notification email (reply-to set to the shopper) and to a desk inbox, or to a connected help desk such as sibling HappyToHelp; Cloudflare Turnstile, a honeypot and per-sender rate limits hold spam for review instead of silently dropping it. A newsletter signup block (footer, page section or popup) records an explicit marketing opt-in under CUSTOMER-002 with source, form, page and timestamp, optionally confirmed by double opt-in, and propagates the subscriber to Mango, Klaviyo or Mailchimp through MARKET-001 without duplicating an existing contact.

    Acceptance evidence: Create and schedule a blog post and policy page through the desk, publish a product with SEO metadata, fetch its rendered HTML/sitemap, and rename its slug. Verify old URLs redirect once and unpublished content is absent from public search and feeds. Submit the contact form and confirm it reaches the merchant email with the shopper as reply-to and appears in the desk inbox; submit scripted spam and verify it is held, not delivered or lost. Sign up through the footer, confirm the subscriber has source, page and timestamp, and verify the same consented subscriber appears once in Mango and in a Klaviyo or Mailchimp test account; repeat the signup and verify no duplicate.

  • MOBILE-001 — Accessible mobile shopping and merchant work. The complete catalog-to-receipt, account, return and merchant order workflows work at 390 and 1440 pixels with keyboard and screen-reader labels, visible focus, sufficient contrast and actionable errors. WCAG 2.2 AA is the target. Human-readable state and freshness distinguish unavailable data from zero stock or success; failed actions retain input and prevent duplicate submission.

    Acceptance evidence: Use the built storefront and desk at both widths to buy variants, recover a validation failure, read order status, request a return and process it. Complete the same essential controls by keyboard and inspect accessible names and focus after dialogs/errors. Run an automated WCAG 2.2 AA scan, including its color-contrast rule, on each storefront, checkout, account and desk page at both widths and verify no violations.

  • MOBILE-002 — Native merchant apps and timely order attention. iOS and Android merchant apps provide secure sign-in, order/customer lookup, product/photo edits, stock visibility, barcode-assisted picking, fulfillment including the pickup and local-delivery steps (SHIP-007), returns and approval notifications under the same role checks as the web desk. Offline drafts show stale data and reconcile conflicts before effects; device revocation removes authority and lock-screen notices avoid customer details.

    Acceptance evidence: On each platform receive a new-order notification, scan a purchased SKU, prepare fulfillment offline, change the order elsewhere, and reconnect. Verify the conflict requires fresh approval. Edit a product's title and price and add a photo taken with the device camera, and verify the change goes through the same revision approval and appears on the storefront with the photo served from owned storage. Mark a pickup order ready and picked up from the app (SHIP-007) and verify one notice and one dispatch. Revoke the device and confirm private reads and actions fail.

Catalog and stock

  • CATALOG-001 — Products, variants and media. The desk maintains products, handles, SKUs, variant options/combinations, USD prices and compare-at prices, cost basis, taxable categories, categories/tags/attributes, collections, image galleries and video/alt text. Merchants define typed custom fields (metafields such as size charts, care instructions or ingredients) that themes render on product pages and that imports and exports carry. Products can ask the shopper for personalization (engraving or monogram text with a character limit, a choice list, or a file upload with type and size limits), optionally with a USD price add-on; it is validated before add to cart and carried to the cart, checkout review, order, packing slip, confirmation email and exports, and uploaded files are stored privately under erasure (ERASURE-001). Each variant has independent stock mode and availability (STOCK-001/003), shipping weight/dimensions, and customs description, HS tariff code and country of origin for international labels (SHIP-002). Draft, scheduled, published and archived states preserve historical purchased descriptions/prices and expose only approved current listings.

    Current metadata semantics: optional cost is a nonnegative integer number of USD cents; weight is positive whole grams and dimensions are positive whole millimeters (all three together). HS codes accept 6, 8 or 10 digits and origin accepts two uppercase letters; these format checks make no tax, customs or country-validity verification claim. Up to 20 uniquely keyed custom fields carry a text, finite number or boolean value. Omitted details preserve the prior prepared/current facts; an explicit empty details object clears them. Legacy orders without a description snapshot remain unknown rather than borrowing the current listing.

    Current listing semantics: A product's page is /shop/<handle> (lowercase letters, digits and single hyphens), unique across current and prepared revisions and derived from the SKU when blank. A product has up to three options and up to 100 variants, one per combination. Each variant has its own SKU, unique across products, and may override price, compare-at price, cost, weight, dimensions, HS code, country of origin, customs description and image; a compare-at price must exceed the price it accompanies. Publication requires every variant on sale to be an active Pier item, and each variant's availability is its own Pier item's. Independent stock modes other than Pier-tracked (untracked, store-managed and alternate connectors) are inherited by STOCK-001 and STOCK-003. Images (PNG, JPEG, GIF, WebP) and videos (MP4, WebM) are typed by their content, kept in Stall's database at up to 700 KB each with required alt text, and public only while a published listing references them. Categories (10), tags (30) and attributes (30) are plain text; collections are STORE-002's records, which list a product by SKU or match it by these values. Personalization has up to five fields: text up to 500 characters without control characters, a choice list that accepts only its choices, or a file field that accepts only its selected types (PNG, JPG, PDF), judged by content, up to its limit (at most 700 KB). An add-on price is charged per unit and only the reviewed price is accepted. An uploaded file is private to owners and administrators, attaches to one order, is deleted by customer erasure (ERASURE-001) and, if no order claims it, after 24 hours. A listing is a draft until approved, scheduled while approved with a future publish time, published afterwards and archived when withdrawn; only published listings are public and every order keeps its purchased name, description, variant, personalization and price. When payment is verified Stall makes one plain-text confirmation attempt and records whether it was sent; durable outbox, delivery and bounce evidence and branded templates are inherited by MAIL-001, and carrier packing-slip templates by SHIP-002. The packing slip is a staff-only printable page. Imports carry listing fields through the Stall Details JSON (CATALOG-002 inherits the richer file formats).

    Acceptance evidence: Create a product with size/color variants, multiple images, cost, weight, tax category, HS code, country of origin and a size-chart custom field; publish an approved revision and verify the custom field renders on the product page. Buy one variant, change its current price and archive another; verify gallery/selection and immutable order snapshots through public product and order views. Add an engraving field (20 characters, +$5) and an artwork upload to a product, refuse over-length text and a disallowed file type, buy with valid personalization and verify it with the add-on price on the cart, order, packing slip and confirmation email.

  • CATALOG-002 — Bulk catalog operations and portable files. Merchants import, export and bulk-edit products/variants, collections, prices, publication, tax settings, stock mode, weight, dimensions, HS codes, countries of origin and custom fields. A dry run shows creations, changes, conflicts and rejected rows before an exact reviewed apply; jobs resume without duplicates and offer undo only where later native edits or orders will be preserved. Original source custody and row-level outcomes remain inspectable.

    Cites: CATALOG-001 and SHIP-004.

    Current bulk semantics: the native catalog CSV uses Kind, ID and Value columns for complete product and collection records; the legacy Shopify subset keeps its draft-only behavior. The complete grid reuses native product and variant editors. Native apply is an explicit exact-reviewed human catalog approval, replacing any prepared revision; publication and scheduling require current active Pier items for every live variant and the same listing checks as individual approval. Tax categories and customs fields remain merchant-authored facts, not provider verification. Pier-tracked is the currently supported stock mode; STOCK-001 and STOCK-003 retain other stock authorities and CATALOG-003 retains quantity adjustments. Shipping-profile assignments keep their separate SHIP-004 reviewed grid and catalog CSV, remain unchanged by catalog edits and protect products or variants that undo would otherwise remove. Current local authority is checked on every apply, resume, export and undo. Complete before-images, original source bytes and per-row outcomes travel with the journal; undo preserves later native work, purchased variants and retained collection references without changing orders or provider stock.

    Acceptance evidence: Upload a mixed valid/invalid catalog file, inspect a read-only preview, apply the reviewed rows, resume an interrupted batch, export them and undo untouched changes. Edit/purchase an imported SKU first and verify undo reports the protected row rather than overwriting it.

  • CATALOG-003 — Bulk quantity adjustments through the stock authority. Merchants bulk-edit on-hand quantities per location. Quantity changes from the bulk grid or an inventory CSV are written to each variant's stock authority (STOCK-001/003) with Stall and provider references recorded together. This clause inherits STOCK-001 and STOCK-003. The Pier-connected leg requires Pier's future scoped stock-adjustment command: Stall's current Pier key admits only order.create, order.channelPayment and dispatch.create and cannot call an on-hand adjustment command today. The store-managed leg requires STOCK-003's local stock authority.

    Acceptance evidence: Bulk-edit on-hand quantities in the grid and by an inventory CSV, once with store-managed stock and once with Pier connected, and verify each change appears once in the stock authority's history with a matching reference.

  • STOCK-001 — Live availability through Pier or another stock system. Stall displays variant-level sellable availability from each variant's stock authority and reserves against the selected location/fulfillment policy. A variant may be untracked or use store-managed quantities with no stock system at all (STOCK-003); Pier is an optional first-class adapter, and a documented connector lets a merchant retain another stock system. Stall owns storefront merchandising and retail order experience; Pier owns the Cin7/inFlow-style inventory, purchasing and wholesale order system. Backorder/preorder rules, lead times, safety stock and stale-provider behavior are visible before purchase. Changes that start in Stall (on-hand adjustments from the product editor, bulk editor or inventory CSV, sale reservations, cancellation releases and accepted restocks from RETURN-002) are written to the connected stock system with Stall's and the provider's references recorded together; changes that start in the stock system (receipts, counts, transfers) flow back to availability. Neither side becomes a second warehouse ledger. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Connect Pier, publish variants across two locations, make an external stock change and verify public availability. Adjust a variant's on-hand quantity from the product editor, the bulk editor and an inventory CSV and verify each adjustment lands once in Pier with matching references. Repeat both via the documented alternate adapter; test backorder refusal/allowed lead time, stale stock and duplicate reservation events with matching stock-provider references. Set a safety stock of 2 on a variant with 5 on hand and verify the storefront sells exactly 3 before showing it sold out.

  • STOCK-002 — Expiring checkout holds and stock race resolution. Checkout rechecks availability and creates a bounded stock hold before payment commitment. Holds expire or release after abandonment, failed payment and cancellation; a verified payment converts the same hold into a reservation once. Late payment or shortfall remains an explicit exception with feasible fulfillment, shopper-approved substitution or reconciled cancellation/refund rather than silently overselling.

    Acceptance evidence: Two shoppers attempt the last unit through checkout. Expire one hold and fail another payment; verify releases. Deliver late/duplicate success and lose a reservation response; confirm one reservation or a visible paid-shortfall case resolved by the shopper-approved outcome. While the first shopper's hold is live, verify the second shopper is told the last unit is held, with the hold's remaining time, and cannot pay for it, and that it becomes buyable again as soon as the hold expires or that payment fails.

  • STOCK-003 — Store-managed quantities and untracked items without a stock system. Each variant has a stock mode: untracked (made-to-order or unlimited, optionally with a production lead time shown before purchase), store-managed quantities kept by Stall per store location, or a connected stock system (STOCK-001). With no stock system connected, a merchant can sell, hold, reserve and fulfill untracked and store-managed variants; adjust on-hand counts with a reason (received, correction, damaged, cycle count) from the product editor, the bulk editor or an inventory CSV; see on-hand, committed and available quantities per location with adjustment history; and choose per variant whether to continue selling when out of stock. Store-managed counts are the retail quantities a Shopify-class store keeps, not purchasing, transfers or wholesale, which remain Pier's job. Connecting Pier or another stock system later moves opening balances through a reviewed handoff, after which that system is authoritative and Stall's counts become read-through. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: With no stock system connected, sell and manually fulfill (ORDER-002) a made-to-order untracked variant and a store-managed variant; verify committed and on-hand counts and that the last unit cannot be oversold unless continue-selling is on. Adjust on-hand counts from the editor, bulk editor and CSV with reasons and inspect the adjustment history. Connect Pier, review and apply the opening-balance handoff, and verify later adjustments are written through Pier with matching references while Stall keeps no independent count.

Cart, payment and commercial totals

  • CART-001 — Persistent cart and guest or account checkout. Shoppers add/remove variants, change quantities, retain a cart across refresh/sign-in, and check out as guests or account holders. Native shopping/checkout steps collect US addresses, and international addresses in the destination's format for zones the merchant serves (SHIP-001), plus contact, selected delivery method, an optional order note and a gift message with an optional gift receipt that hides prices. They show reviewed USD item, discount, gift-card, shipping, tax and final payable totals before committing payment. Material changes require review again; stock, price and address errors preserve the basket. Saved carts never grant access to another customer. Order notes and gift messages appear on the order, packing slip and confirmation. Merchants can add their own checkout fields (for example "How did you hear about us?", a preferred delivery date or a gift-wrap choice) as required or optional text, choice or date inputs; answers are stored on the order and appear in the order desk, exports and reports (ANALYTICS-001). Current native HTTP cart defaults pending ct approval: a private HttpOnly guest capability or an independently verified account owns each cart. Sign-in handoff is explicit and allowed only to the same verified mailbox, with no foreign-cart or old guest-cookie access afterward. Current Stripe checkout serves US delivery; a Canadian address can be saved but is refused before payment without losing the basket. Review binds the cart revision, published lines, delivery, current checkout questions and exact USD totals. Required merchant questions apply to every existing public Stripe checkout door. Once a checkout starts, immutable original intent and its idempotency identity survive lost replies and later catalog changes; a restored cart carries history without spending authority and needs a fresh copy/review. Shopper note/gift/answer snapshots are separate from internal staff notes and are erased with customer contact. Gift redemption and provider tax are unavailable, labelled explicitly rather than inferred from a zero applied amount.

    Acceptance evidence: Build a multi-variant cart, reload and sign in, choose a US address and delivery method, add an order note and gift message, apply a discount/gift card and review exact totals. Change price or availability concurrently and verify a fresh review; repeat as a guest, as a different account and with a Canadian address. Verify the note and gift message on the order and packing slip and a gift receipt without prices. Add a required "How did you hear about us?" choice field, verify checkout refuses to continue without it, and find the answer on the order, in the order export and in a report grouped by answer.

  • PAY-001 — US dollar cards, wallets, PayPal, pay-later and manual payments. The merchant connects their own Stripe and PayPal accounts. Checkout supports USD cards, Apple Pay, Google Pay and Link/Shop-style accelerated wallet checkout, PayPal and PayPal Pay Later, and buy-now-pay-later through Stripe's Klarna, Affirm and Afterpay methods, using supported provider adapters and eligibility checks. Pay-later options appear only within each provider's current order-amount and shopper-country eligibility, show the provider's installment terms, and can be advertised on product and cart pages through provider messaging; the merchant is paid by the provider and refunds return through the same method. Merchants can also offer manual methods (bank transfer, cash on delivery, pay at pickup) whose orders stay pending payment until staff record receipt; fulfilling an unpaid manual order requires an explicit merchant setting. Eligible payment choices and unsupported devices are honestly presented; customer payment credentials stay with the processor and wallet. Refunds and receipts retain original method/currency references. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Complete USD purchases with a card, Apple Pay, Google Pay, Link and PayPal through their supported test/eligible-device doors; inspect provider IDs, amount/currency, failure/cancel paths and a same-method refund. Complete a test-mode Klarna, Affirm, Afterpay and PayPal Pay Later purchase and refund each; verify every pay-later option is withheld, with an explanation, below and above its eligibility range. Verify provider pay-later messaging appears on the product and cart pages with installments computed from the current price, updates when the cart changes, and disappears outside eligibility. Place bank-transfer and pay-at-pickup orders and verify they stay unpaid and unfulfillable until staff record payment. A live provider/device acceptance run is required before claiming production wallet readiness.

  • PAY-002 — Authorization, capture, cancellation and disputes. Merchants choose supported immediate capture or authorize-then-capture rules, see pending/authorized/captured/failed/expired/canceled states, and reconcile asynchronous payments, voids, disputes, chargebacks and provider fees. No fulfillment occurs on an unverified browser return or mere authorization. Expired authorization and a disputed payment create accountable staff work. For a dispute the desk assembles evidence (order and receipt, policies, customer communications, carrier tracking and delivery scans) into the processor's evidence fields; staff review and submit it to Stripe or PayPal before the response deadline, and the outcome and dispute fees reconcile to the order. Permitted captures/refunds bind current order and provider state. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Authorize an order without capture, attempt fulfillment, capture once, then process a failed/expired authorization, asynchronous success and dispute event. Assemble and submit evidence for a test dispute on Stripe and PayPal, and verify the processor received it and the won/lost outcome and fee reconcile. Duplicate/out-of-order callbacks must preserve actual processor state, correct balance and a visible owner action.

  • PAY-003 — Verified payment and duplicate-safe paid reservation. A signed payment event must match its raw body, timestamp, event identity, original order/session, exact-cent amount and currency, and canonical processor state before an order is treated as paid. Repeated delivery and lost stock responses reconcile to the same paid order and Pier reservation. A paid shortfall remains recorded; a browser success page alone proves nothing. Changed reuse of an idempotency identity is refused.

    Acceptance evidence: Through public checkout and the signed webhook send unpaid, stale, wrongly signed, changed-total and duplicate events; lose the Pier response after its commit, then reconcile. Inspect one payment/order/reservation and durable paid-before-reservation history.

  • PROMO-001 — Discounts, automatic promotions and controlled budgets. Merchants create each Shopify-class discount type as either a code or an automatic discount: percentage or fixed amount off selected products, variants or collections; percentage or fixed amount off the order subtotal; Buy X get Y (buy a quantity of, or spend an amount on, qualifying items and get specified items free or at a percentage/amount off, with a per-order use limit, including buy-one-get-one); and free shipping with a minimum subtotal or quantity, eligible zones/countries and an optional maximum rate. Each has date windows, customer eligibility/segments, minimums, per-customer/total usage, combination rules across product, order and shipping discounts, and budgets. Merchants can bulk-generate unique single-use codes for influencers or affiliates, export them and see redemption per code. Checkout explains applied/refused promotions, allocates discounts to lines for tax and refunds, records the chosen rule revision and emits qualification/redemption/reversal events. Concurrent baskets cannot exceed a shared cap; refund/cancellation treatment is explicit.

    Approved policy: CT approved the free-shipping-code default on 22 October: owner and administrator management; reserved and used allocations consume caps; restored rules require fresh activation. The same current-authority and exact-cents boundary governs the added native rules. An unpaid reservation is released only after the provider confirms that its checkout expired or never existed; paid use and refunds retain consumption. Product discounts apply before order discounts, then shipping, with both rules consenting to each combination. Fixed product and order amounts apply once to the selected subtotal; fixed Buy X get Y amounts apply to each reward unit. Reward units never qualify themselves and cheapest eligible reward units are selected first. Each order retains the chosen revisions, exact line allocations and original tax references. These semantics do not waive the original acceptance journey or the shared TAX-001 calculation boundary. End-to-end cancellation remains unproved because the supported Pier connection cannot cancel its reserved order; no stock release or canceled-order success is inferred.

    Acceptance evidence: Configure each type once as a code and once as an automatic discount: amount and percentage off a product and a collection, amount off the order, a buy-one-get-one and a spend-$X Buy X get Y, and free shipping over $50. Build qualifying and non-qualifying baskets and verify the reviewed checkout totals, line allocations and tax to the cent. Exercise combination rules, race the last redemption of a capped code, generate a batch of unique single-use codes and refuse a second use of one, cancel one order and partially refund another. Reconcile campaign usage, budget and exact order/tax totals from the merchant report and emitted events.

  • PROMO-002 — Gift cards and stored redemption balances. Merchants sell or issue gift cards, deliver secure codes, inspect a balance ledger and redeem partially across orders alongside another method. Concurrent redemption, cancellation and refund preserve value exactly once; issuance, expiry restrictions and cash-out handling follow the configured US jurisdiction/policy and are explicit to the shopper. Gift cards sold to shoppers follow the federal CARD Act (no expiry earlier than five years after issue or last load, no dormancy or inactivity fee in the first twelve months) unless the store's state is stricter, and the store's state sets cash-out rules, such as California's requirement to pay balances under $10 in cash on request; free promotional cards are labeled as promotional with their own terms. Staff can also issue store credit to a customer outside any return (goodwill, loyalty or a price adjustment) with a USD amount, reason and optional expiry; it shows in the customer's account and applies at checkout like a balance, alone or alongside another method, and return-resolution credit (RETURN-002) uses the same ledger of issue, use, expiry and staff adjustment. Exported balances and migrated cards reconcile without revealing full codes to unauthorized staff.

    Acceptance evidence: Issue a USD gift card, deliver and redeem it partly, race its remaining balance in two checkouts, and cancel/refund the winning order. Inspect the balance ledger, shopper receipt, staff permissions and reconciled migrated opening balance. Try to give a sold card a two-year expiry and verify refusal under the five-year rule, while a promotional card may carry it. With a California store, request cash-out of a $7.50 remaining balance and verify a recorded payout zeroes the ledger, and verify a $15.00 balance is refused cash-out. Issue $20.00 goodwill store credit to a customer with no return, sign in as that customer, see it in the account and apply $12.00 of it at checkout alongside a card; verify the ledger shows $8.00 remaining. Sell a $50.00 gift card through storefront checkout, verify the buyer receives its code by email once payment is verified, and redeem it at checkout on a later order.

  • TAX-001 — US sales tax and exemptions. Stripe Tax, Avalara AvaTax or TaxJar calculates US state/local sales tax using the merchant's configured registrations, ship-from/destination, product tax categories, exemption evidence and shipping/discount treatment. Checkout shows jurisdictional tax before payment; order records preserve the calculation reference and refunds reverse the correct tax. Provider outage or incomplete configuration blocks a taxed sale with a useful explanation, rather than inventing a zero rate. A sales-tax liability report shows, for any filing period, a state overview (gross, taxable, non-taxable and exempt sales, shipping, tax collected, refunds and adjustments, with marketplace-facilitated channel sales separated), then county, city and special-district breakdowns, then the contributing transactions; each level exports as CSV and drills to orders and provider calculation/transaction references, and refunds land in the period they occur. A nexus view tracks per-state sales and transaction counts against the merchant's configured economic-nexus thresholds and warns before one is crossed. Registration and filing stay with the merchant, adviser or a filing service such as Avalara Returns or TaxJar AutoFile, fed by these exports.

    Current implementation semantic: the owner-only HTTP preview door sends complete US destination and ship-from addresses, explicit product tax codes, quantity-extended line amounts and already-discounted shipping to the connected Stripe test account after explicit data-boundary consent. Amounts are exclusive USD integer cents; provider totals and breakdown must reconcile. Active head-office settings, a default tax code and an observed destination-state registration are required. A preview is never a payment, registration, filing or tax transaction. The durable journal keeps no street address; an uncertain calculation is recovered only by retrieving its original reference and matching the full original inputs and line metadata, never by a replacement POST. Restored previews are observation-only and require the original provider calculation. The owner-only consent and restore boundary is approved with riders (ct 25 October 2026). The preview does not enable taxed checkout or substitute for the remaining acceptance journey.

    Approved preview boundary. Only the current native owner may explicitly consent to and request the current tax-preview data transfer. Consent identifies the connected Stripe Tax account and preview-only purpose; destination and ship-from street, city, state, ZIP and country data; line references, amounts, quantities and product tax codes; discounted shipping; and opaque preview and intent references used for calculation custody. It distinguishes what Stall retains from data sent to and handled by the provider. It grants no payment, tax-transaction commitment, registration, filing or legal-certification authority.

    The current preview uses exclusive USD integer cents, quantity-extended line amounts and the supplied already-discounted shipping amount, without applying quantity or shipping discounts twice. It is clearly labelled preview-only. The preview store, history, audit and portable preview records retain minimized opaque custody, attempt and outcome, calculation reference, totals and provider-reported breakdown, without street addresses or raw address-bearing request or response payloads. This preview-retention boundary does not remove the separate order and shipping records required by the commerce contract or claim that Stripe retains no address data.

    Restoring a preview restores historical observation and original-reference custody only. It never replays a calculation or restores consent, credentials, sending authority, current quote validity or sale authority. Any receiving-owner connection and new preview use fresh local authority and explicit consent. An uncertain original calculation is recovered only by retrieving and validating its original provider reference against the original intent; neither retry, restart, restore nor a new request identity may replace it with another calculation. If the original reference or matching evidence is unavailable, uncertainty remains visible and actionable. Restored or expired observations cannot be presented as current checkout tax.

    No local jurisdiction name or zero rate is invented from incomplete provider evidence. The complete TAX-001 checkout, exemption, order-reference, refund, reporting, CSV, nexus-warning and live test-mode receipt obligations remain unchanged. CART-001, PROMO-001 and ORDER-005 inherit this shared calculation boundary when connected; ORDER-003 and TAX-001 retain correct tax reversals and ACCOUNT-001 retains reconciled posting. These defaults are product decisions, not tax or legal certification.

    Native taxed-sale default (ct approval pending). Preview consent grants no sale authority. A separate native owner-only, account-bound, explicitly audited consent enables test-mode taxed sales; each shopper explicitly consents to the calculation data transfer. Configuration and exemption evidence alone grant no sending or payment authority. A customer exemption requires an independently verified native customer email and current, unrevoked, state-matching evidence reviewed by the local owner. Restored evidence needs explicit fresh local review.

    Native remedies and marketplace evidence (ct approval pending). Taxed goodwill needs explicit owner confirmation that it leaves recorded sales tax unchanged, sends no reversal and posts a zero-tax adjustment in its filing period; refunding purchased items or shipping reverses tax. A payment made to a different full address than the reviewed tax address is never fulfilled and no sales tax is recorded for it; the finance-approved remedy refunds the whole payment, tax included, through the same approval and recovery path as any refund. Marketplace-facilitated sales are recorded by the owner with explicit consent as reporting evidence only: no customer, address or payment data, one row per marketplace reference, never replaced once recorded, kept in separate channel rows and totals that are not added to merchant-collected tax, and counted toward configured nexus thresholds. A connected marketplace feed belongs to the channel clauses, which inherit this evidence door.

    Checkout consumes a current calculation bound to exact merchandise, quantity, discounted shipping, customer identity, tax configuration and full address. Tax custody retains keyed address and purchase fingerprints and opaque references, while ordinary paid-order shipping records retain their required address. A changed full payment address blocks tax commitment and fulfillment. Provider-refused or uncertain work never becomes zero tax or a replacement calculation or transaction. Explicit recovery retrieves and validates original provider references. Restored sale authority blocks new checkout until a current owner explicitly enables it or keeps it off; historical observation never supplies that authority.

    Liability reports use signed original provider tax postings and the selected filing period in the shop time zone, with a separate refund posting when the reversal occurs. Sale jurisdictions come only from provider calculation evidence. Stripe's reversal names none, so refund tax is split over the original provider breakdown by what remains unreversed (a derived allocation, ct approval pending); tax with no named jurisdiction stays visibly unallocated. Configured nexus warnings use the selected explicit period, item gross less refunds posted in that period, and distinct sale-order counts; refunds do not erase completed transactions. Either enabled configured measure can trigger the merchant's warning percentage. No statutory threshold, registration, filing or legal certification is inferred.

    Acceptance evidence: Configure two US destinations, taxable/exempt goods, a documented exempt customer and discounted shipping. Check provider-backed totals before payment and a partial-return tax adjustment; interrupt the tax provider and verify checkout refuses an unpriced obligation and reports the cause. After taxed sales to two states (one with county, city and special-district tax) and a partial refund in the following month, run the liability report for each month and verify the state, jurisdiction and transaction levels and their CSVs reconcile exactly to the order records and tax-provider transaction references, with the refund in its own period. Approach a configured nexus threshold and verify the warning. Quote two US addresses in the same ZIP code that fall in different city or special-district jurisdictions and verify each is charged its own address-level rate.

  • RISK-001 — Fraud indicators and human review. Processor fraud signals, address/payment mismatches and order risk appear in a restricted review queue with their provenance. Merchant-configured rules hold risky fulfillment and notify authorized staff; an explicit release/cancel decision records the reviewer. Scores are advisory and never silently assert fraud, capture funds or deny a refund without the configured authority. The current conservative default restricts configuration and review to human native owners/admins and records one in-app alert per order/signal set. Cancel means cancel fulfillment only: payment and Pier reservations remain recorded for separate authorized financial/stock handling. ct approved these review and cancellation semantics with riders on 23 October 2026: owner and administrator review only, one deduplicated in-app alert per order and signal set, and cancellation limited to fulfillment, with payment and Pier reservations left recorded for separate authorized handling. There is no automatic release, cancellation or refund, by design: only a recorded owner or administrator decision releases or cancels a hold, a fresh provider flag reopens review, and a score never denies a refund. ORDER-004 and future SHIP-002/005/006/007 fulfillment effects inherit the hold gate and explicit handling of money and stock.

    Acceptance evidence: Create low-risk and flagged provider test orders, inspect the restricted queue, attempt fulfillment while held and release/cancel with an authorized reviewer. Repeated risk callbacks must not duplicate holds or messages.

Fulfillment, orders and returns

  • SHIP-001 — Shipping zones, live rates, international USD shipping, pickup and delivery. Merchants configure shipping zones for the US (by state/ZIP) and for Canada and other countries served in USD from the same store, with service eligibility, free/flat/weight-based rules, handling cutoffs and delivery promises; checkout rates packages from current variant weight/dimensions through ShipStation, Shippo or EasyPost for USPS, UPS and FedEx domestic and international services. International rates state that duties and import taxes are the recipient's responsibility unless the merchant enables a supported duties-paid (DDP) landed-cost service through the shipping provider, and checkout collects the destination's address format and the phone number carriers require. Destinations outside configured zones and embargoed destinations are refused before payment. Shoppers choose eligible service, local pickup at a named store location (shown with its address, opening hours, pickup instructions and expected ready time) or local delivery inside the merchant's delivery area (set per location by ZIP codes or a radius, with its own fee, minimum order and delivery instructions) with clear price and instructions; changed address/package invalidates stale quotes. Pickup and local-delivery orders are completed through SHIP-007, never through a carrier label. Each location has a daily handling cutoff, handling days and a business-day and holiday calendar; the delivery date or range promised at checkout is computed from them and the service's transit time, is shown on the product page and in checkout, and the paid order keeps the promise it was sold under. Split-source orders show combined charges and feasible dates. Which rates and services apply to which products is set by shipping profiles (SHIP-004); this clause's zones and rules are the general profile every product starts in. Local currencies and regional storefronts are EXPAND-001. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Quote different US ZIPs and package weights with live provider test rates, select pickup/local delivery, change address after selection and verify repricing. Select local pickup and verify the location, hours and instructions are shown and kept on the paid order; enter a ZIP outside the delivery area and verify local delivery is not offered, and below the delivery minimum verify checkout states the amount still needed. Set a 2 p.m. Eastern handling cutoff with one handling day and a holiday the next business day; place orders just before and just after the cutoff and verify promised delivery ranges one business day apart that skip the holiday, kept on each paid order. Quote Canadian and UK addresses in USD with provider rates and verify the duties disclosure. Refuse destinations outside configured zones and show actionable carrier outages; the paid order must retain the selected service and quoted charge. At checkout for a US address verify that live USPS and UPS services are both offered at the provider's current rates, and that a rate changed in the provider test account is reflected in the next quote.

  • SHIP-002 — Purchase, print and void carrier labels. Authorized staff buy and print outbound/return labels through ShipStation, Shippo or EasyPost, prepare manifests and packing slips, and void unused labels with reconciled charges. Labels work out of the box at the shipping provider's own discounted USPS, UPS and FedEx rates with no carrier account of the merchant's own, as Shopify Shipping does; a merchant who has their own carrier accounts and negotiated rates can connect them, and the rate shown names which account it uses. Staff can add parcel insurance for a declared USD value when buying a label, through the provider's insurance (Shippo or EasyPost insurance, or ShipStation's shipping insurance) or the carrier's declared-value coverage; the premium is shown before purchase, counts in the approved spend, reconciles with the label charge, and a lost or damaged insured parcel opens an ORDER-004 claim carrying the insurance reference. Merchants edit the packing-slip template (logo, store and return address, which fields print such as prices, SKUs, images, barcodes, order and gift notes, and a return or thank-you note), preview it on a real order, and every slip printed singly or in a batch (SHIP-005) uses the saved template. International labels carry customs declarations (CN22/CN23 or commercial invoice) generated from each line's customs description, HS tariff code, country of origin, quantity and USD value (CATALOG-001), submitted electronically through the provider where the carrier supports it and printable with the label; a missing HS code or origin blocks purchase with a link to fix the product rather than sending incomplete data. Label purchase binds the order, package, service and approved spend. An uncertain provider response is looked up by the same reference before another purchase; downloadable label data is access-controlled. Labels are bought one order at a time here or as a reviewed batch of many orders (SHIP-005); a merchant who already ships from their own ShipStation or a 3PL buys labels there instead (SHIP-006). Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Buy and print a label for each supported carrier through a connected shipping provider, lose one successful response, reconcile it, then void an unused label and buy a return label. Buy a label to a Canadian address in USD with HS code and country of origin taken from the product, print the customs form and verify its values; remove a product's HS code and verify purchase is refused with the fix path. With no merchant carrier account connected, buy a USPS label at the provider's rate; then connect a merchant UPS account and verify its negotiated rate is quoted and named. Buy a label insured for a $200 declared value, verify the premium in the reviewed spend and the provider charge, and open a lost-parcel claim from it that carries the insurance reference. Edit the packing-slip template to add a logo, hide prices and add a return note, preview it, and verify the printed slip from a single label and from a batch. Verify one charge/label per operation, usable documents and restricted access. Start each purchase from the order's page in the desk and verify the label prints from there with the order's ship-to address, package and service already filled in.

  • SHIP-003 — Split fulfillment, tracking and delivery exceptions. Staff allocate lines to locations/packages, partially fulfill or backorder the remainder, and record carrier/service/tracking per shipment. Provider scans drive shipped, in-transit, delivered, delayed, failed and lost states with timestamp/source; shoppers receive truthful tracking and delivery notices. Carrier delivery is attributed evidence, not a guarantee of physical receipt; shipment edits and duplicates preserve remaining quantities.

    Acceptance evidence: Split a two-line order across locations, dispatch one parcel, then the remainder; receive duplicate, out-of-order, delayed and delivered tracking callbacks. Verify each shopper view/email and remaining quantity, and open an exception when scans go stale.

  • SHIP-004 — Shipping profiles for specific products. Merchants group products or variants into shipping profiles: a general profile every product starts in, plus custom profiles (at least the 99 Shopify allows) for items such as oversized, fragile, free-shipping or local-only goods. Each profile has its own ship-from locations, zones, rates (free, flat, weight- or price-based, carrier-calculated, with optional surcharge or handling fee) and allowed services, and can be pickup-only or local-delivery-only. Products and variants are assigned to a profile in the product editor, the bulk editor and catalog CSV (CATALOG-001/002), and Shopify shipping profiles map across in migration (MIGRATE-001). For a cart that spans profiles, each offered service is priced as the sum of each profile's rate for its own items in that service; a service is offered only when every profile in the cart allows it; a pickup-only or local-delivery-only item removes shipped services for the order and says which item caused it. A variant whose profile does not serve the destination is refused before payment, naming the line and keeping the rest of the basket. Each quote records the profile revisions it used; editing a profile or reassigning a product invalidates open quotes, and the paid order keeps the profile revision and quoted charge it was sold under.

    Current profile semantics: the general profile (general, which holds the shop's earlier flat domestic charge as its one standard service) and up to 99 custom profiles, each with its own ID, name, ship-from label, ZIP-prefix zones (one to five leading digits; none means every US ZIP), up to 20 services and pickup and local-delivery switches. A service has a code, a name and a rate: free, flat, weight bands (grams, from the variant's weight, else the product's) or price bands (the profile's subtotal including add-ons), plus an optional handling fee once per profile in the basket and a surcharge per item. A rate applies once per profile per basket; a weight or price past the last band means that profile does not offer the service. A product or variant is assigned to a profile by SKU (a variant's own assignment wins over its product's), stored apart from product revisions and effective at once. For a basket, a shipped service is offered only when every profile in it offers that service code, priced as the sum of each profile's rate for its own items; a profile with no shipped service removes shipped services for the basket and the quote names its items; a profile whose zones miss the shopper's ZIP code lists its lines as unserved, and checkout refuses a shipped service before any payment, naming them, while the rest of the basket stays. Pickup and local delivery use the shop's one pickup place and one delivery area (ZIP prefixes, fee, minimum) and are offered when every profile allows them; delivery also needs a ZIP inside the area and the minimum met. Each offered service carries a quote key derived from the destination ZIP, the basket, the used profiles' revisions and the computed charge; checkout with a stale key is refused, and the paid order keeps its service, ZIP, quote key, profile revisions and charge. The ZIP is the one the shopper entered in the shop; Stripe collects the delivery address afterwards (pickup collects none) and Stall does not compare the two. Profiles, places and assignments are changed only by a signed-in owner or administrator, never an agent, are audited, travel in the archive and the records export, and the customer's erasure removes an order's quoted ZIP and quote key. Bulk assignment (the Products grid and a catalog CSV with the headers SKU,Shipping Profile) shows every change and applies only the reviewed fingerprint; the catalog CSV is the acceptance's catalog-or-inventory CSV leg, as ct approved on 22 October. Stock-quantity adjustment is CATALOG-003 and STOCK-003. Inherited by later clauses: SHIP-001 (carrier-calculated rates, state zones, per-location pickup and delivery areas, handling cut-offs and promises, address verification), SHIP-002 (labels), SHIP-007 (completing pickup and delivery orders), MIGRATE-001 (mapping Shopify's profiles), CATALOG-002 (the grid and catalog CSV carry the profile column as they widen), CATALOG-003 (the inventory CSV carries the profile column when stock adjustments ship), and every later record kind inherits archive, export, audit and erasure duties.

    Acceptance evidence: Configure a general profile ($6 flat), an oversized profile ($25 flat, UPS Ground only), a free-shipping stickers profile and a furniture profile allowing only local pickup and local delivery. Quote a cart with one general and one oversized item to a US ZIP and verify a single UPS Ground option at exactly $31.00; add a sticker and verify the charge is unchanged; add a furniture item and verify shipped services disappear, pickup and local delivery remain and the cause is named. Send the oversized item to a ZIP its profile does not serve and verify refusal before payment naming that line. Bulk-reassign the oversized products to the general profile through the CATALOG-002 grid and a catalog or inventory CSV, verify the open quote is invalidated and the new quote changes, and verify an earlier paid order still shows its original profile revision and charge.

  • SHIP-005 — Bulk label purchase and batch fulfillment. From the order list, authorized staff select paid orders (up to 100 per batch per ship-from location, as Shopify allows) and create shipping labels as one batch. Before review, Stall skips and names every order it cannot label, with the reason: already fulfilled, no shipping required (pickup, local delivery or digital only, which complete through SHIP-007 instead), invalid or unverified address, missing customs HS code or country of origin on an international line, payment not yet captured or verified, a risk hold (RISK-001), or stock not reserved. One review screen shows each remaining order's package preset and weight, default service (from its shipping profile and rules, editable per order or in bulk) and label cost, plus the batch's total spend against the approved limit; one human approval binds the exact batch revision and each order's draft under ORDER-002. Each label is bought under its own idempotent reference; an uncertain or lost provider response is looked up before any retry, so every order ends with exactly one label, and failures are listed for fixing without re-buying succeeded labels. The batch produces one combined label PDF (4×6 thermal or letter) and one combined packing-slip PDF in the same order, plus a pick list, and can be reprinted. Each labeled order moves to fulfilled with carrier and tracking (SHIP-003), dispatches against its stock authority once, and its shopper gets exactly one shipment notice (MAIL-001). Staff can also bulk-mark orders fulfilled with tracking numbers from a CSV upload when labels were bought elsewhere. Batch history keeps who approved, spend, outcomes and skipped orders. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Select a mixed batch of paid orders: valid domestic orders, one already fulfilled, one pickup-only, one with an undeliverable address and one international order whose product lacks an HS code. Verify each excluded order is skipped with its reason, review per-order services and total spend in the provider test account, change one order's service, and approve the batch once. Lose one provider purchase response and verify reconciliation leaves exactly one label per order and one provider charge each. Download one combined label PDF and one packing-slip PDF and verify their order and count; verify every labeled order is fulfilled with tracking, its stock dispatched once, and each shopper received exactly one shipment notice. Bulk-mark three further orders fulfilled from a tracking CSV and verify the same outcomes.

  • SHIP-006 — Merchant shipping apps and 3PLs as fulfillment connections. A merchant who already packs in their own ShipStation account, or ships through a 3PL such as ShipBob or ShipMonk, connects it as the fulfillment connection for a location or for the whole store. Paid orders cleared of payment and risk holds are sent once, with lines, SKUs, weights, customs data, ship-to address, the shopper's selected service and paid shipping, and order and gift notes. A shipment created there (label bought in ShipStation, or a 3PL dispatch) writes carrier, service and tracking back to the Stall order, records the fulfillment, dispatches stock against the line's stock authority once and sends one shipment notice; partial shipments keep the remaining quantities open. Address and line edits and cancellations in Stall propagate to the connection, and an edit or cancellation the external tool has already shipped against is refused in Stall with the shipment named. Orders routed to a connection are not offered for Stall label purchase, so nothing is labeled twice. A 3PL connection may also be the variant's stock authority through STOCK-001's alternate adapter. Duplicate, late and out-of-order callbacks reconcile by the external order and shipment IDs; connection health and orders stuck unsent or unshipped past a set time are visible as staff work. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Connect a ShipStation test account as the fulfillment connection. Place paid orders and verify each appears in ShipStation exactly once with its service and notes; buy a label there and verify tracking writes back, the Stall order is fulfilled and the shopper gets one shipment notice. Edit an unshipped order's address and cancel another, and verify both propagate; try to cancel a shipped order and verify refusal. Replay the shipment callback and verify no second fulfillment or notice, and verify routed orders are absent from Stall's label batch. Repeat the order-to-shipment journey with a ShipBob or ShipMonk sandbox, including stock read through the 3PL.

  • SHIP-007 — Local pickup and local delivery fulfillment. Pickup and local-delivery orders follow their own fulfillment states and never need a carrier, label or tracking number. A pickup order shows in the order list and a pickup queue with its pickup location: staff set the items aside and mark it ready for pickup, which sends the shopper one ready-for-pickup notice (MAIL-001: email, plus SMS with consent) carrying the location's address, hours and pickup instructions; when the customer collects, staff mark it picked up (optionally recording who collected after an order-number or name check), which fulfills the order. A local-delivery order goes from unfulfilled to out for delivery, which sends one out-for-local-delivery notice with the expected window and delivery instructions, then to delivered, which fulfills the order and sends one delivered notice; a failed attempt records a reason, returns the order to ready for delivery and creates a staff task. Staff print a pick list for pickup orders and a delivery list for the driver (each stop's name, address, phone, delivery instructions, items and order notes, sorted by ZIP or a route order staff set). Each step is an attributable staff action under the same role checks from the order desk, the pickup and delivery lists (several orders at once) and the MOBILE-002 merchant app. Stock dispatches once against each line's stock authority (Pier, the alternate connector or STOCK-003 store-managed counts) at the pickup or delivery location, when a pickup order is picked up or a delivery order goes out for delivery; a partial pickup keeps the remaining lines open. Repeating a step, a double tap or a stale screen observes the current state and sends no second notice or dispatch. A pickup order not collected within the merchant's pickup window (for example 7 days after ready) becomes a staff task with an optional reminder notice, and staff can cancel and refund it under ORDER-004 with a reason, releasing the set-aside stock. The customer's order view and the merchant's history show each state, who set it and when. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Buy a pickup order and a local-delivery order through checkout with a test card. Mark the pickup ready and verify exactly one ready-for-pickup email (and one SMS for a consenting shopper) carrying the location, hours and instructions; mark it picked up and verify the order is fulfilled with no carrier or tracking number and its stock dispatched once at that location. Mark the delivery out for delivery, then delivered, and verify one notice per step and a fulfilled order; print the delivery list and verify each stop's details. Repeat each step from the desk and the merchant app and verify no second notice or dispatch. Leave a second pickup order uncollected past its window, verify the staff task, then cancel and refund it under ORDER-004 and verify one refund and released stock.

  • ORDER-001 — Complete retail order desk: current orders. The merchant desk searches and filters orders by status, customer, date, SKU and channel, and keeps customer/contact/address, original line and total snapshots, payment/stock/fulfillment/return/refund states, notes, tags, assignment and provider references in one history. Staff create manual retail orders, and see overdue work without changing historical truth. Merchant-selected US time zones and USD formatting govern business displays. The shop's named IANA time zone is canonicalized when saved; the initial default is America/Chicago. Desk timestamps use the saved zone and the offset in effect at each event, and “Yesterday” means the preceding calendar date there, including daylight-saving transitions. Stored commercial timestamps and exported timestamp fields remain UTC. Order filters combine: status, customer text, item SKU, a placed-date range and overdue work. A date range is the shop zone's calendar days of placement, both ends inclusive; an order is overdue when it is partly shipped and its latest recorded Pier dispatch (payment time when unstamped) is more than 7 × 24 hours old, a derived label that never changes the order. One history per order lists every audited action with actor and time and the provider references the record keeps. Only a signed-in owner or admin saves the zone; members and agent credentials are refused, the save is audited, and any canonical IANA zone may be saved. Saving a zone rewrites no stored time: labels, “Today” (the zone's current date at each request), “Yesterday” and date filters follow the saved zone from the next request, so an order's placed date can move to another day. A calendar day runs from the first instant of that date in the zone to the first instant of the next, 23 or 25 hours across a transition. Clauses that later add local days, times or date windows (SHIP-001, SHIP-007, PROMO-001/002, RETURN-001, FLOW-001, RECOVERY-001, MAIL-001, ANALYTICS-001, TAX-001, ACCOUNT-001) use this zone unless their own text names another, name it where a shopper sees a time, and resolve a repeated local time to its first occurrence and a skipped one to the first instant after the gap. Customer text matches the order's customer email or recipient name, case-insensitively. Only an owner or admin, or fulfillment/customer-support staff granted ROLE-001 order access, searches. Search covers every order, shows the full match count when the list is truncated (OPS-001), reads no credential, token or checkout request fingerprint, and keeps no separate index, so an erased customer stops matching at once. The channel filter (“Online store”, “Manual”) combines with the others; ORDER-005 and CHANNEL-001/002/004 add their channels when they ship. Notes and tags are internal plain text: a note holds up to 2,000 characters, and an order has at most 50 tags of up to 40 characters. Only a signed-in owner/admin or ROLE-001 fulfillment/customer-support staff adds and reads them; ungranted members and agent credentials are refused. Notes are append-only with author and time, a correction is a new note, and only the owner may redact a note's text with a reason. Each note, tag or redaction is an audited action in the order's history. Notes and tags never reach a shopper or an outside party: no storefront, checkout, notice, receipt, packing slip, customer view, provider or connection payload or API event carries them. They are separate from a shopper's order note or gift message (CART-001). Owner exports and archives include them. Customer erasure replaces each note's text on the erased customer's orders with “Erased with customer contact”, keeping note ID, author and time, and removes those orders' tags and manual payment references; a restored archive keeps them erased (ERASURE-001). Text about a customer on another customer's order is not detected. CT approved this erasure boundary as landed on 22 October: erasing a customer also deletes the notes and tags on their orders; the audit keeps only that notes existed; notes are excluded from customer-facing exports. The ORDER-001/ORDER-006 numeric fallback and the existing PENDING_EFFECT refusal are accepted, with policy unchanged. A manual retail order records a sale already paid outside Stall. A signed-in owner/admin or ROLE-001 finance staff member enters published catalog items at current USD prices and positive whole quantities within checkout's limits, plus the customer's email, name and US shipping address and the shop's configured shipping charge. Members and agent credentials are refused, and creation fails if the server's total differs from the total the staff member reviewed. Its payment is staff-recorded: cash, check, bank transfer or other, for exactly the order total in integer cents, with a received date in the shop zone that is not after today and an optional plain-text reference. It is labelled “Payment recorded by staff, not confirmed by a payment provider” wherever it appears and never counts as a PAY-003 verified payment. Creation reserves stock through the same paid-order Pier reservation, recovery and shortfall handling as a storefront order; shipment approval (ORDER-002) is unchanged. Its refund is a reviewed ORDER-003 refund within the same limits, but the effect is a staff record rather than a processor call: “Refund recorded by staff; Stall moved no money”. It records no_tax_recorded, and Stall sends no confirmation or receipt. Orders awaiting payment, custom lines, discounts and invoices remain ORDER-005 and PAY-001, which reuse this recorded payment and its label. TAX-001, MAIL-001, ACCOUNT-001, ANALYTICS-001 and ORDER-004 cover manual orders when they ship.

    Acceptance evidence: Create a manual order and a storefront order, assign staff and notes, filter an overdue partial shipment, and open its full history. Change a catalog price/customer address and verify historical commercial snapshots and original provider references remain. Save America/New_York as owner and verify a member and an agent are refused. Verify an order placed at 23:30 Chicago time moves to the next date in labels and the date filter while its stored and exported UTC time is unchanged. Verify orders on both sides of a fall-back and a spring-forward transition show their own offsets on the right inclusive dates. Verify a member, an agent and the shop never receive a note or tag, and redact a note as owner. Erase the customer and verify the note text is replaced, the tags and payment reference are removed and authorship is kept, also after archive restore. Search more than 100 orders by email, name and SKU and find the oldest match with the full count. Record a manual order paid by check and verify the staff-recorded label, one Pier reservation, no_tax_recorded, no message sent and the Manual channel filter. Then refund it and verify a recorded refund within ORDER-003 limits with no processor call.

  • ORDER-006 — Complete retail order desk: risk and draft invoices. The merchant desk searches and filters orders by risk (RISK-001). Staff create draft retail orders and send payable invoices (ORDER-005).

    Acceptance evidence: Create an order paid from a draft invoice (ORDER-005), filter orders by risk, and open its full history.

  • ORDER-002 — Exact shipment approval and one dispatch. A human owner/admin reviews an exact shipment draft against a paid, reserved order. Approval is durable before the dispatch effect of each line's stock authority: the Pier dispatch, the alternate stock connector's fulfillment call, or, for untracked and store-managed variants (STOCK-003), a manual fulfillment record with merchant-entered carrier, service and tracking number that drives tracking (SHIP-003) and the shipment notice (MAIL-001). Stale drafts fail and lost responses reconcile to one dispatch with the original reservation, reference and quantities. Repeating a completed approval observes the same shipment. In a label batch (SHIP-005) one reviewed approval binds every order's exact draft in the batch, and each order still dispatches once; an order routed to an external fulfillment connection (SHIP-006) dispatches once from that connection's tracking write-back under the same reconciliation. Pickup and local-delivery orders complete through SHIP-007's attributable staff steps with no carrier or tracking number and dispatch once at their location. A stock-provider connection cannot silently redirect an existing order to another inventory account.

    Acceptance evidence: Prepare a shipment through the desk/command route, reject a stale revision, lose the approved dispatch response, reconcile and repeat approval. Inspect one Pier shipment, released reservation and matching stock ledger quantities. Repeat with the alternate stock connector, and with no stock system fulfill manually with a typed USPS tracking number; verify one fulfillment, the shopper's tracking notice and decremented store-managed stock. Complete a pickup order through SHIP-007 and verify one dispatch at the pickup location with no tracking number required.

  • ORDER-003 — Reviewed line refunds without duplicate money movement. A human approves the exact revision, purchased lines, reason and computed refund amount. Pending and completed refunds count against refundable quantities/value. Approval persists before provider submission, uncertain responses reconcile using the same provider/idempotency references, and repeat approval cannot pay twice. Besides purchased lines, a reviewed refund can return the shipping charge alone (in full or part, up to the shipping paid), or a goodwill amount with a reason (for example a late parcel) with no line returned, as Shopify's refund screen allows; these count against the order's refundable value, carry their tax treatment (TAX-001) and accounting category (ACCOUNT-001), and never change returned or refundable line quantities. A money refund alone does not assert returned stock or restock an item. Every refund capability that exists today conforms; new payment methods and capture modes (PAY-001/002), tax adjustments (TAX-001) and ledger posting (ACCOUNT-001) inherit exact approval, limits and recovery before those capabilities ship. Current untaxed orders record no_tax_recorded and an explicit merchandise, shipping or goodwill category; this does not claim tax calculation or accounting posting. Amounts are positive integer cents, with inclusive limits: pending and succeeded attempts consume the original paid value, shipping refunds additionally consume only original paid shipping, and only item refunds consume purchased quantities. Failed/canceled attempts free their budgets; drafts do not reserve value and are replaced under the order revision. Historical orders without a shipping charge have zero shipping refundable. The human owner/admin or ROLE-001 finance staff member approves within configured limits and approval separation; agent credentials prepare only.

    Acceptance evidence: Refund one line of a shipped two-line order, lose the processor response, reconcile and repeat approval. Reject a stale or duplicate/over-value refund and inspect one processor refund, unchanged retained line and no stock return. On a delivered order refund the shipping charge alone, then a $5.00 goodwill amount with a late-delivery reason; verify one processor refund each, unchanged refundable line quantities, the refundable value reduced by both, and a further amount above the remaining value refused.

  • ORDER-004 — Versioned edits, cancellation and claims. Authorized staff edit eligible unfulfilled lines, addresses and delivery methods under a version check, with recalculated tax/shipping and explicit shopper agreement for changed goods or charges. Cancellation voids or refunds payment, releases reservations and reports carrier/stock work still pending; an uncollected pickup order (SHIP-007) is canceled the same way, releasing its set-aside stock. A lost or damaged parcel claim carries any label insurance reference (SHIP-002). Damage, non-delivery and other claims retain evidence, owner, decision and linked replacement/refund without overwriting the original order.

    Acceptance evidence: Race two edits on an unfulfilled order, obtain shopper approval of a changed total, cancel before and after capture, cancel an uncollected pickup order (SHIP-007) and verify its set-aside stock is released, and resolve a lost-parcel claim on an insured label (SHIP-002) carrying its insurance reference. Verify stale edits fail and each capture/void/refund/stock release and customer notice reconciles once.

  • ORDER-005 — Draft orders, custom lines and payable invoices. For phone, email and commissioned orders, staff build a draft for a new or existing customer with catalog variants, custom line items (title, USD price, quantity, taxable or not, and whether it ships and its weight), line or order discounts with a reason, shipping (rated through SHIP-001/004 or a custom charge) and tax calculated through TAX-001, including customer exemptions; staff may optionally hold stock for the draft (STOCK-002). From the draft staff send an invoice email (MAIL-001) with an optional message and a secure, expiring checkout link. The customer pays through Stall checkout with the PAY-001 methods; if they change the shipping address, tax and shipping are recalculated and shown before payment. A verified payment (PAY-003) converts the draft into exactly one paid order that keeps the draft reference, and the draft then closes. Editing a draft after its invoice was sent creates a new revision and invalidates the old link, which then tells the customer the invoice was updated and pays nothing until a fresh invoice is sent; a second payment through a link whose draft is already paid is refused, and a duplicate payment event reconciles to the same order. Staff can instead record payment by a manual method (PAY-001). The draft list shows each draft's invoice state (not sent, sent, opened, paid, expired), and drafts can be duplicated or deleted without affecting orders.

    Acceptance evidence: Create a draft with a catalog variant, a custom engraved line at a custom USD price, a 10% order discount and a rated shipping charge, and verify provider-backed tax. Send the invoice, open the delivered email's link as the customer, change to a different-state address and verify recalculated tax before paying with a test card. Verify exactly one paid order carrying the draft reference and the custom line. On a second draft send the invoice, edit a line, and verify the old link refuses payment until the new invoice is paid; open the paid first link again and verify a second payment is refused, and replay the payment webhook to verify no second order.

  • RETURN-001 — Customer self-service returns, cancellations and exchanges. An authenticated account or secure guest order link shows order/shipment/refund history and accepts cancellation, return and exchange requests by eligible line/quantity/reason. Merchant policy explains windows, condition, final-sale exceptions, fees, return shipping and available exchange stock. Staff receive review tasks and shoppers see acceptance/refusal and progress; disputed or exceptional decisions require a person. Another shopper cannot access the request or its attachments. Current semantics: the owner publishes one return policy (window in days from the latest recorded dispatch, required condition, a fee shown to shoppers and applied only when staff record the refund, who pays return shipping, final-sale SKUs, exchanges on or off); until it exists only cancellation before fulfillment starts is accepted. A native verified-email account or a private order link opens one paid order, and the server checks every line again for the window, final sale, shipment and quantity not already requested or refunded, refusing an ineligible line with its rule. A return or exchange may carry up to three private photos readable only by that order's customer, a private link for that order and a native owner or administrator. A case is requested, then accepted or refused only by a native owner or administrator person with an explanation the customer reads; no rule, score or agent decides, and a request outside the written policy is refused with its rule and left to the shop to arrange. Accepting a cancellation, a return or a refusal moves no goods, money or order state; accepting an exchange sets one replacement aside under a deterministic Pier command checked against current stock and moves no money. Staff see every case in an in-app list whether or not a workflow rule exists, and the first return or cancellation of an order also writes the FLOW-001 intake record. Customer erasure removes cases and photos. RETURN-002 inherits goods receipt, restocking and the reconciled resolution of an accepted case. These private-link request authority, automatic refusal, exchange-reservation, photo custody and in-app-only staff notification defaults await ct approval.

    Acceptance evidence: As guest and account customers request a cancellation, partial return and size exchange; test expired/final-sale items and another customer's link. Verify staff notification, an explained decision, exchange reservation and customer-visible progress without duplicate requests.

  • RETURN-002 — Physical receipt, restocking and reconciled resolution. Return cases connect authorization, provider return label, tracking, staff inspection/condition, accepted quantities, restock/quarantine/disposal in Pier or the stock adapter, tax/shipping/fee adjustments and the reconciled refund/store credit or exchange shipment. Stock is added only after recorded physical receipt/inspection; money and stock can complete separately but unresolved work stays visible. Duplicate receipt/refund callbacks cannot increase either balance twice.

    Acceptance evidence: Return one damaged and one resellable unit, purchase/track a label, record staff inspection, quarantine one and restock the other, then refund or exchange. Lose stock/refund responses and reconcile to one receipt, one financial resolution and a closed customer-visible case.

Customers, follow-up and channels

  • CUSTOMER-001 — Customer directory, accounts and order history. Merchants manage deduplicated customer profiles, addresses, tags and segments, notes and order lifetime value under permissions. Customers can securely register or sign in, recover access, manage their addresses and see only their own imported and new orders, tracking, returns, gift balances and refund status. Guest-to-account linking requires verified ownership; historical migration never grants access just because names match. CT’s 23 October invitation and identity rider applies: invitations are single-use and expire, and a usable customer account exists only after independent email verification. The current slice uses native email verification and one-use email-link recovery. Public account requests require explicit necessary-account consent and individual owner approval before a native invitation is sent; no imported login or password grants authority. Owner-enabled self-signup remains unavailable pending a supported native signup capability. Unverified request identity data expires after seven days, request metadata after thirty days; requests and rate-limit data stay local and never travel in archives or business exports. Those new intake and retention defaults await ct approval. Imported historical USD orders require an exact source reference, reconciled totals and an explicitly approved current preview; they supply history and paid totals without payment, stock or sign-in authority. Gift and goodwill balances use a mailbox-bound append-only USD ledger, with exact human-reviewed cents and reasons, separate from directory merges. No checkout redemption, expiry, outbound delivery, cash-out or refund is implied; PROMO-002 and MAIL-001 inherit those obligations. The balance custody and retained opaque financial journal after erasure await ct approval. Directory deduplication uses normalized exact email, and an explicit owner or administrator reviewed merge combines merchant metadata only: each mailbox still sees only orders and addresses for its independently verified email. Lifetime value is paid USD order totals less succeeded refunds; order count includes paid orders, and saved tag, minimum spend, minimum count and state segments are recomputed on every read. Customer-support staff may manage directory metadata, while imports and merges require an owner or administrator; agent credentials grant no directory or customer-session access.

    Acceptance evidence: Import two similar customer records, resolve a duplicate, place guest/account orders and link only after verified email ownership. Sign in as each customer, recover access and attempt foreign order/address/return reads and writes through direct APIs. Tag customers, build a segment by tag, total spent, order count and state, and verify membership updates after a new order and a refund; verify each customer's lifetime value and order count equal the sum of their orders net of refunds.

  • CUSTOMER-002 — Consent, preferences and customer privacy. Shoppers control email/SMS marketing consent separately from necessary order notices, with timestamp, source, channel and withdrawal history; consent is captured at checkout, account, the newsletter signup and contact form (STORE-003) and popups, never pre-ticked. A storefront privacy banner and persistent preference link govern analytics and advertising cookies, pixels and server events (CHANNEL-003): the merchant chooses notice with opt-out (the US default, honoring Global Privacy Control and "Do Not Sell or Share" requests under California's CPRA and similar state laws) or opt-in by visitor region; refused categories stop those pixels and events, Google Consent Mode reflects the choice, and the choice is recorded with policy version. Import preserves provable consent and leaves unknown consent unsubscribed. Account export/deletion and owner erasure requests expose retained financial records and provider follow-up; suppression propagates to connected marketing systems and survives restore. Sensitive customer data is limited by staff role. CT’s 23 October consent/privacy rider applies: marketing categories remain denied until the shopper explicitly chooses against the current policy; consent records the wording’s policy version and capture time, imports preserve suppression, and privacy requests require owner review. The current HTTP slice requires an independently verified native customer session with explicit email and SMS choices; public capture never asserts an arbitrary mailbox. Owner-imported affirmative consent needs a dated source/reference and cannot lift a local withdrawal or erasure suppression. Visitor categories start denied until an explicit current-policy choice; Global Privacy Control persists an advertising/do-not-sell refusal. Region is currently visitor-selected, not geolocated, and no pixel/conversion provider is installed. Restored visitor history grants no pixel authority. Account requests create audited owner work and move no money, delete no account and send no provider action; owner erasure retains financial IDs and records separate provider follow-up. STORE-003, MARKET-001, RECOVERY-001, MAIL-001 and CHANNEL-003 inherit these channel, suppression and current-policy gates before their capture/send/event doors ship.

    Acceptance evidence: Import subscribed/unsubscribed/unknown contacts, change preferences at checkout, account and the footer signup, unsubscribe through a delivered message and inspect downstream suppression. Refuse analytics and marketing on the banner in one visit and send Global Privacy Control in another; verify no pixel, server conversion event or ad cookie is sent while checkout works, then accept and verify events resume only from that point. Request access/erasure and restore an older archive with the later journal; verify no marketing reactivation or foreign customer access.

  • CUSTOMER-003 — One-click reorder from order history. A signed-in customer's account lists their orders newest first with date, items, total, status and tracking (CUSTOMER-001), and each past order offers Reorder. One click builds a cart (CART-001) holding the same variants, quantities and still-valid personalization, with the order's shipping address preselected, at current prices and availability; a line whose variant is archived, unpublished or sold out is left out and named, and every price change since the original order is shown before checkout. Reorder never charges, holds or reserves stock or skips checkout review: the shopper reviews current totals, tax and shipping and pays through PAY-001 like any order. A secure guest order link offers the same reorder into a guest cart; nobody can reorder or read another customer's order. Current native HTTP account reorder uses the independently verified mailbox, creates a separate unreviewed cart and rechecks source-order custody in the write transaction. It retains original quantities only where the whole quantity remains available, names unavailable or invalid-personalization lines, and records original versus current unit cents including add-ons. Past order-bound file uploads require a new upload; no file capability is copied. Only the prior shipping address is preselected; previous checkout answers, notes, gifts, discounts and payment authority are not reused. CT approved the owner-invited independently verified mailbox boundary on 23 October. A verified owner of a paid order may explicitly issue a one-order guest link, lasting one day by default and at most seven days. Issuing another link replaces the old one; the customer can revoke it. Only a keyed digest is retained, links never travel in archives or business exports, and erasure or a changed order mailbox invalidates them. The browser receives the capability in a URL fragment and removes it from the displayed address. Guest reorder creates a fresh cart under its separate HttpOnly guest capability, even in a signed-in browser. Current checkout questions, shipping and enabled tax require fresh review; the source order supplies no spending authority.

    Acceptance evidence: Sign in as a customer with two past orders, open order history and verify both with their dates, totals and status. Reorder a three-line order after one variant's price changed and another sold out; verify the cart holds the two available lines at current prices with the price change and the sold-out line named, and that no payment, hold or reservation exists before checkout. Complete checkout and verify a new order with its own payment while the original order is unchanged. Reorder from a guest order link, then try to reorder another customer's order through the direct API and verify refusal.

  • MAIL-001 — Transactional confirmations and delivery evidence. Branded email through SendGrid or the owner-selected Base mail adapter delivers order/payment confirmation, ready-for-pickup (with the location, hours and pickup instructions), picked-up, out-for-local-delivery and local-delivered notices (SHIP-007), shipment/tracking, delivery, cancellation, return/exchange and refund notices, with a downloadable PDF receipt or invoice from the message and the customer's order view. Staff receive a new-order email by default, with recipients configurable per store. Shoppers who opt in to SMS (CUSTOMER-002) receive shipment, ready-for-pickup, out-for-delivery and delivery texts through Twilio, with STOP handling. A shopper can ask to be notified when a sold-out variant returns; one back-in-stock message goes out when sellable availability returns, and requests expire. Notices derive from committed order transitions and include accurate totals/status and secure links. Merchants edit each notification's template (logo, colors, subject and body copy with order variables), preview it with a real order, send a test and turn optional notices on or off; required order notices cannot be disabled. Mail sends from the merchant's own domain once its SPF, DKIM and DMARC records verify; until then it sends from the installation's verified domain with the merchant's address as reply-to, and a domain that fails verification cannot be selected as sender. Durable message IDs, provider acknowledgment, delivery/bounce/complaint outcomes and failed-work tasks distinguish submitted from delivered; marketing suppression does not silently suppress necessary service mail. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Buy, split-ship, deliver, return and refund an order through public doors; inspect the corresponding provider messages, safe order links and the PDF receipt, and confirm the default staff new-order email. With SMS consent verify shipment and delivery texts and STOP. Mark a pickup order ready and a local-delivery order out for delivery and delivered (SHIP-007), and verify one notice per step carrying the location, hours and instructions. Edit the order-confirmation template's logo, color and copy, preview it, send a test, and verify the next delivered confirmation matches. Add a sender domain, publish its DNS records and verify DKIM and SPF pass in the delivered message's headers; verify an unverified domain cannot be selected. Request a back-in-stock notice on a sold-out variant, restock it and verify exactly one message. Repeat callbacks, inject a bounce and lose a send response; verify deduplication, visible uncertainty and staff follow-up without falsely claiming inbox receipt.

  • RECOVERY-001 — Abandoned-checkout recovery to a valid basket. Merchants configure consent-aware recovery timing, templates, frequency caps and incentives. An eligible abandoned checkout receives a secure expiring cart link; returning shoppers get current prices, stock, tax and delivery options with changes explained. Payment, unsubscribe, erasure or merchant pause cancels pending recovery; duplicate jobs do not resend. Reports attribute recovered orders and costs without counting unrelated purchases.

    Acceptance evidence: Abandon guest/account checkouts, advance the configured schedule, receive one recovery message and return through its link after price/stock changes. Buy, unsubscribe and erase before later steps; verify suppression, expiry, renewed review and accurate recovered-order attribution.

  • MARKET-001 — Mango and consent-aware lifecycle marketing connections. Stall connects catalog, customer consent/segments, order, checkout and refund events to sibling Mango, and supports Klaviyo and Mailchimp email/SMS stacks. Mapping previews, scoped authorization, backfill, suppression and delivery outcomes are inspectable. Mango owns cross-campaign marketing work; Stall owns commerce eligibility, checkout recovery and order truth. No sale or external contact list silently creates marketing consent. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Authorize Mango and each supported marketing adapter, preview a segment/event backfill, place and refund an order and withdraw consent. Inspect matching event identities and suppressed contact state downstream; revoke the connector and verify pending sends stop and failures remain actionable.

  • CHANNEL-001 — Google Shopping, Meta/Instagram, TikTok Shop and Pinterest. Merchants publish approved product/variant media, USD price, availability and shipping/tax attributes to Google Merchant Center/Shopping, Meta/Instagram Shops, TikTok Shop and Pinterest catalogs (for shoppable Pins and catalog ads), with per-channel mapping, validation and rejection repair. Where a channel accepts orders, channel orders, cancellations, fulfillment, returns and refunds synchronize to the same retail order and stock reservations. Meta's Facebook and Instagram Shops adapter is a catalog feed plus website checkout: product taps open Stall's product page and checkout with the source attributed, because Meta ended in-app checkout for US shops; Google and Pinterest are likewise feed surfaces whose purchases complete on the website, while TikTok Shop takes orders in-app and synchronizes them. Feed-only surfaces state that limit explicitly; remote and direct sales cannot both spend the last unit unnoticed. Ad pixels and conversion events for the same platforms are CHANNEL-003. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Connect each named channel, publish a variant, inspect a rejection and correct it, then change price/stock. In each supported order sandbox import an order and duplicate event, ship/refund it and verify remote status, one reservation and channel-attributed analytics; test revoked channel access. Open a product from the Meta test catalog and verify it lands on Stall's product page and completes in Stall checkout with Meta recorded as the order source.

  • CHANNEL-002 — Marketplace adapters without becoming a marketplace. Optional Webgility-compatible Amazon, eBay and Walmart integrations map listings/SKUs, orders, fees, fulfillment and returns into the same commerce/accounting records. Conflicts, provider limits, channel-specific policy and stale inventory are explicit. Stall remains the merchant's online-store product and does not operate a buyer/seller marketplace. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Connect each selected marketplace through Webgility or its supported adapter, backfill and replay an order/refund, change stock and reconcile fees. Show one retail order/stock effect and matching ledger entries, with a visible unresolved mapping case.

  • CHANNEL-003 — Ad pixels, conversion APIs and custom storefront events. Merchants connect GA4, Google Ads conversion tracking with enhanced conversions, the Meta Pixel with the Conversions API, and the TikTok pixel with the Events API through their own accounts, and can add sandboxed custom pixels (for example Pinterest or an affiliate network) in a customer-events manager. The storefront and checkout emit one standard event stream (page view, product view, search, add to cart, begin checkout, add shipping and payment info, purchase, and refund where the platform accepts it) carrying variant IDs, quantities, USD value, currency and order ID. Browser and server copies of an event share an event ID so each platform deduplicates them; purchase fires once per verified paid order (PAY-003), never from a browser success page alone. Hashed customer identifiers are sent only with marketing consent, and CUSTOMER-002 consent and Global Privacy Control govern every pixel and server event. Each connection shows delivery status, platform diagnostics and rejected events; custom pixels run sandboxed with no access to payment fields or other pixels' data. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Connect GA4 (DebugView), Google Ads conversion diagnostics, the Meta Pixel and Conversions API (Events Manager test events) and the TikTok pixel and Events API (test events). Browse, search, add to cart, begin checkout and buy; verify each platform receives each event once with matching event ID, order ID and USD value, with browser and server copies deduplicated. Replay the paid webhook and reload the receipt page and verify no second purchase; refund the order and verify the refund event where supported. Refuse analytics and marketing consent, and separately send Global Privacy Control, and verify no pixel or server event fires; install a custom pixel and confirm it receives subscribed events but cannot read payment fields.

  • CHANNEL-004 — Embeddable Buy Button and checkout links. Merchants generate an embeddable Buy Button, product card or collection widget for another website (a blog, WordPress or a landing page) and shareable checkout links that preload chosen variants, quantities and an optional discount. Embeds show live published price and availability, add to a Stall cart and complete payment in Stall's checkout with its tax, shipping, consent and payment rules; orders are attributed to the Buy Button or link channel in ANALYTICS-001. Each embed is restricted to the merchant's allowed domains, carries no credentials, and stops selling when its product is unpublished or sold out. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

Current door semantics: the existing human owner or administrator generates and revokes public configurations through the documented same-origin HTTP door. Each script has its own exact HTTPS origin list, requests public catalog data without credentials or tracking and opens a separate native cart for explicit checkout review. Product cards and collections resolve current published variants; neither a copied control nor a stale price bypasses native stock, personalization, required-field, shipping, tax-consent or payment checks. Restored configurations are inert and must be generated afresh locally. No new provider account or outgoing provider job is added: native Stripe and Pier work retains INTEGRATION-001 custody and original-identity recovery. Orders and commercial exports preserve the distinct buy_button and checkout_link channel values, which ANALYTICS-001 inherits.

Acceptance evidence: Generate a Buy Button and a collection widget, embed them on a test page on an allowed external domain, and buy through them; verify the order, stock and channel attribution. Open a checkout link with two preloaded variants and a discount and verify the reviewed totals. Embed on a disallowed domain and verify refusal, then unpublish the product and verify the button stops selling.

  • REVIEWS-001 — Verified reviews, upsells and cross-sells. Merchants collect verified-purchase reviews with star ratings, text and photos natively or through Judge.me, Yotpo, Okendo or Loox adapters, moderate abuse with a visible policy, reply publicly, and merchandise related products, bundles, upsells and cross-sells against current price/stock. Product pages show the rating and reviews with Product, Review and AggregateRating structured data so search results can show stars. Requests obey consent/contact rules. Existing reviews move in through MIGRATE-007 and stay labeled as imported with their source's provenance. Paid incentives, imported reviews or AI-generated text cannot masquerade as a new verified customer review.

    Acceptance evidence: Fulfill an order, send a permitted review request via the native door and the Judge.me and Yotpo adapters, collect a photo review, moderate a reported review and show purchase provenance. Fetch the product page HTML and validate its review structured data. Add a recommended bundle to cart, exhaust one component and verify the offer updates without overselling. Set manual related products on one product and automatic related products (same collection and frequently bought together) on another; verify each product page shows only published, in-stock related products, sell one out and verify it drops from the recommendations, and add a cart-page cross-sell and verify it lands once in the basket at its current price.

Reporting, accounting and migration

  • ANALYTICS-001 — Sales, conversion and contribution margin. Merchants inspect date/channel/product/variant/customer reports and traffic-source reports (sessions, conversion and sales by referrer, source and medium, UTM campaign, source, medium and content, landing page, device and location, under a stated last non-direct-click attribution window) for visits, product views, add-to-cart, checkout, payment conversion, gross/net sales, discounts, tax, shipping collected/cost, fees, refunds, gift liability and contribution margin using recorded cost data. Funnels disclose consent-limited/unknown traffic, bot exclusions, attribution window and historical import provenance. Reports drill to orders and export; canceled, test, imported and duplicate events never inflate new conversion.

Adopted analytics boundary pending ct approval: native human owner or administrator report access only; current-policy explicit analytics choice, with no marketing authority; 30-minute sessions and a stated 30-day last non-direct-click window. Capture retains minimized events and sessions for 30 days, then removes browser correlation while retaining commercial source labels. Withdrawal and customer erasure remove linked capture and order attribution. Restored observation grants no visitor, cost-consent or import authority. Conversion discloses its eligible paid live order numerator and observed consented session denominator in the same shop-date window; unlinked sales and absent costs remain labelled unknown. Historical imports retain owner-supplied original references, create no live sale or new conversion, and never imply provider confirmation. ACCOUNT-001 retains the separate obligation to produce actual accounting posting references.

CHANNEL-004 supplies the distinct buy_button and checkout_link values in current orders and commercial exports. Future channel reports consume those recorded values; this does not claim a traffic report or pixel implementation.

Acceptance evidence: Arrive through a UTM-tagged email link, a search referrer and a direct visit, and buy after two of them; verify the traffic-source report attributes sessions, conversion and sales to the right campaign, referrer and landing page. Follow a known visitor-to-refund journey, import historical sales, replay events and compare channel/date totals with orders and processor/accounting references. Remove cost/analytics consent and verify unknowns are labeled rather than fabricated margin or visits. Open the best-sellers report for a date range and verify products and variants ranked by units sold and by net sales after refunds match the orders exactly, and that its conversion rate equals paid orders over sessions for the same window.

  • ACCOUNT-001 — Reconciled QuickBooks Online and NetSuite posting. QuickBooks Online maps customers, products, sales receipts/invoices, taxes, shipping, discounts, gift-card liability, refunds, processor fees and payouts to the merchant's reviewed accounts. Exportable sales/order/payment CSVs support accountants; NetSuite posting is available through Webgility or a documented ERP adapter. Sync exposes pending/posted/rejected/uncertain states, original remote IDs and a reconciliation report; a changed mapping or duplicate event never silently double-posts revenue. Before this capability ships new provider work, it inherits INTEGRATION-001: installation-local secret custody, least privilege, mapping/data-boundary previews, durable original intent/correlation/attempt/outcome and recovery without replacement uncertain effects.

    Acceptance evidence: Preview account/tax mappings, post a sale, gift redemption, partial refund, fee and payout to QuickBooks Online and the selected NetSuite adapter sandbox. Replay, lose a response and correct an account rejection; reconcile net sales, tax liability and cash to provider and exported records.

  • MIGRATE-001 — Full reviewed Shopify migration. A Shopify switching merchant previews and imports products/variants/media/collections and product/variant metafields mapped to custom fields, customers/addresses/consent, historical orders/lines/payments/refunds/fulfilments, shipping profiles (SHIP-004), product reviews from the merchant's review app (MIGRATE-007) and URL redirects with source IDs, count/value reconciliation and explicit unsupported/conflict rows. Store content moves with it: pages (such as About, FAQ, Shipping and Returns, Contact) and store policies (refund, privacy, terms of service, shipping); blogs and their articles with body, images copied into owned storage, author, tags, excerpt, SEO fields and original published date; and the main, footer and nested navigation menus, re-linked to the migrated products, collections, pages and articles. These are read through the Admin API (Page, Blog, Article and Menu objects) because Shopify's CSV exports omit them, and each keeps its original handle or gets one redirect. Active discounts transfer with the same rules so codes already handed out keep working at cutover: code and automatic discounts, amount and percentage off products, collections or the order, Buy X get Y, free shipping over a threshold, with their date windows, eligibility, minimums, combination rules, usage limits and each code's remaining usage, including bulk single-use code batches whose already-redeemed codes stay refused (PROMO-001), read from Shopify's discount export and the Admin API. Discounts that cannot map, such as app-owned discounts or Shopify Functions or Scripts logic, are listed in the coverage report (MIGRATE-006) with the codes affected, never dropped. Gift card balances are transferred or individually reconciled (MIGRATE-006). Incremental cutover catches changes before DNS switch. Historical financial/stock events are read-only provenance and never re-charge, reserve stock, send recovery mail or pretend to prove new conversion. Current reviewed product import/undo guarantees are retained.

    Acceptance evidence: Use Shopify exports and authorized Admin API data for a representative store, including metafield definitions and values, shipping profiles, a Judge.me review export, content pages and policies, two blogs with articles, the main and footer menus, and discounts covering a code discount, an automatic discount, a Buy X get Y, free shipping over a threshold and a partly redeemed single-use code batch; dry-run counts/values and redirects, apply/resume, reconcile customers/orders/refunds/balances and custom fields, then import the cutover delta. Verify each page and article renders at its original handle (or through one redirect) with its published date, author, tags and images served from owned storage, and each menu links to the migrated objects. Apply each migrated discount in checkout and verify the same rules and remaining usage, and that an already-redeemed single-use code is refused; verify an app-owned discount and a Shopify Functions discount are listed in the coverage report with their codes. Open old links and customer history; verify no external money/stock/mail effects and undo preserves later native work. Time the migration of a representative store of 500 products with variants, 2,000 customers and 5,000 orders from connecting the Shopify source to a reconciled, cutover-ready store (dry run, review, apply and delta) and verify it completes within four hours of elapsed time, recording the measured time.

  • MIGRATE-002 — Squarespace Commerce migration. A Squarespace Commerce merchant migrates products/variants/images, customers/profiles and consent evidence, historical orders/fulfillment/refunds, content and URL redirects through available exports and authorized APIs. The migration preview names source omissions and offers reviewed supplemental mappings for content, balances or records absent from a native export. Counts, USD totals and old URLs reconcile before cutover; source passwords/payment secrets do not transfer.

    Acceptance evidence: Import a representative Squarespace store via its available export/API doors, supplement missing source fields in the preview and reconcile variant/customer/order/refund counts and values. Cut over old URLs, verify history and customer reactivation, and prove imports cause no payment, stock or email side effects.

  • MIGRATE-003 — BigCommerce migration. A BigCommerce merchant migrates catalog/options/variants/media/categories, customer/address/consent data, orders/transactions/refunds/shipments, coupons/gift liabilities and redirects using reviewed export/API mappings. App-owned fields and unsupported objects are listed for explicit mapping. Original IDs and USD totals reconcile and a cutover delta preserves later work without importing source authority or replaying commerce effects.

    Acceptance evidence: Preview and apply a BigCommerce export/API migration containing variant options, partial shipment/refund, a gift liability and redirects; reconcile source counts and totals, rerun the delta and verify no duplicate objects, stock reservations, charges or notices.

  • MIGRATE-004 — WooCommerce and extension migration. A WooCommerce merchant migrates products/variations/media/categories, customers/consent and order/refund/fulfillment history using CSV and authenticated REST exports; maps permalinks to redirects; and gets a per-extension inventory of discounts, gift cards, subscriptions, reviews (imported through MIGRATE-007) and custom fields. Unsupported extension data has a reviewed adapter/supplement path and explicit cutover work rather than disappearing. Secrets, password hashes and stored payment credentials are excluded.

    Acceptance evidence: Import a WooCommerce store with variable products, a refunded order and representative extension/custom fields. Inspect omissions/mappings before apply, reconcile source values and URL redirects, then repeat the delta and customer activation without replaying historic sales.

  • MIGRATE-005 — Open-engine and creator-store move-in. Medusa, Saleor and Fourthwall merchants can map their authorized export/API data into the same reviewed migration process for available products/variants, customers, orders, fulfillment/refunds, content and redirects. The preview inventories provider-owned production, memberships and subscription records, lists inaccessible data and supports reviewed supplements/partner handoff. No adapter invents source consent, passwords, processor authority or missing fulfillment evidence.

    Acceptance evidence: For each named source preview an authorized export/API sample and source-field coverage, apply and resume its mapped catalog/customer/order history, reconcile totals/redirects and explicitly resolve unavailable creator-production/subscription records before cutover.

  • MIGRATE-006 — Cutover completeness, source limitations and outstanding liabilities. Every migration maps source store/entity IDs, paginates to completion, groups multi-row products/orders correctly and distinguishes stock-bearing variants from modifiers. Media is copied into owned storage before retiring source URLs. A coverage report lists export/API omissions, inaccessible fields, custom/extension data and unresolved records; nothing is silently discarded or labeled fully migrated while unresolved. Content pages, policies, blog articles and navigation menus are counted in the coverage report like commerce records. Live discount codes carry their rules, remaining usage and redeemed single-use codes, so no code becomes reusable or invalid at cutover, and a code redeemed on the source after an import is caught by the cutover delta. Product/collection/content redirects reject loops and collisions. Customer access requires reactivation/reset, not imported passwords. Issued gift balances reconcile as liabilities with secure carryover/reissue and duplicate-redemption prevention. Subscription schedules and processor authority require provider-approved transfer or renewed authorization before billing; historic orders never authorize new charges. A resumable cutover delta and rollback preserve native changes and prevent duplicate source IDs.

    Acceptance evidence: For each source in MIGRATE-001/002/003/004/005 import continuation rows, variants/modifiers, guest orders, unknown consent, a partially refunded order and a gift liability; interrupt pagination and resume. Retire a source image URL and follow old product/content URLs. Redeem a migrated single-use code on the source after the first import, run the delta and verify it is refused in Stall; verify pages, articles and menus appear with counts in the coverage report. Inspect count/value/omission reports, resolve collisions, activate a customer and verify no password, new charge, renewal, stock or message side effect comes from historical data.

  • MIGRATE-007 — Product review and rating migration. A switching merchant imports existing product reviews from their review app so product pages keep their stars from day one. Stall reads the Judge.me CSV export (product handle or ID, rating, title, body, reviewer name and email, date, verified flag, photo URLs and merchant reply), which other review apps also accept, and Yotpo, Okendo, Loox, Stamped and Shopify Product Reviews exports, plus the Judge.me and Yotpo APIs where the merchant authorizes them; WooCommerce and BigCommerce native reviews come through MIGRATE-003/004. Reviews map to products by handle, SKU or source product ID using the migration's source-ID map, and reviews that match no product are listed as orphans with a reason and can be re-mapped before apply. Each review keeps its original date, rating, title, body, reviewer display name and merchant reply; its verified status is kept as the source app's claim (shown as verified by that app) and never counts as a new Stall verified purchase. Photos and videos are copied into owned storage before the source app is canceled (MIGRATE-006). Reviewer emails are held for review-request eligibility under CUSTOMER-002 and never create marketing consent. Imported reviews render with structured data and an imported label, never trigger review-request or other mail, and feed product ratings. A dry run shows counts, orphans and duplicates; re-running the import matches by source review ID, or by content hash when the source has no ID, so it creates no duplicates; undo removes only imported reviews.

    Acceptance evidence: Dry-run and import a Judge.me CSV export and a Yotpo export for a migrated catalog, including a review for a deleted product and a photo review. Verify the orphan is listed, each review maps to the right product by handle or ID, keeps its original date and source verified status, and its photo is served from owned storage after the source URL is retired. Fetch the product page and validate the structured data and the imported label; confirm no review-request or marketing mail was sent and the imported reviews are not counted as new verified purchases. Re-run both imports and verify no duplicates, then undo one import and verify native reviews remain.

  • EXPORT-001 — Business CSVs and complete merchant exit. Authorized merchants export every supported business record in documented CSV/JSON formats plus the complete archive: current/pending products, locally retained customer contacts, orders/line details, payment/refund history, shipments and integration reconciliation. Each future clause that adds a record kind inherits export coverage before shipping: CATALOG-001 adds variants/media references, CUSTOMER-001/002 adds accounts/consent, RETURN-001/002 adds returns, PROMO-001/002 adds discounts/gift liabilities, STORE-003 adds redirects, and ANALYTICS-001 adds saved reports. Absent record kinds are explicitly excluded; EXPORT-001 does not claim those capabilities exist. Exports explain schema, currency/time zones and exclusions, never silently truncate, and let a new operator account for outstanding work. Exporting customer data requires an explicit role; credentials never travel.

    Acceptance evidence: Export a populated shop through the desk/API and open its product/customer/order/payment CSVs and complete archive in an independent reader. Reconcile records and exact totals, verify explicit bounds/exclusions and refuse an unauthorized export.

Roles, integrations and dependable operations

  • ROLE-001 — Staff and app least privilege. Owners invite/revoke staff with distinct catalog, fulfillment, customer-support, marketing, finance and administrator permissions, plus customer self-access and scoped app credentials. Server-side checks guard every private read, mutation, bulk job and export; role changes/revocation invalidate stale authority. Refund limits and approval separation are configurable, and staff never acquire provider credentials from the UI. Current functional grants are installation-local, owner-managed and transaction-fenced by revision. Fulfillment and customer support inherit ORDER-001 internal notes, tags and search; finance inherits paid manual orders and ORDER-003 refund preparation/approval. Owner-only redaction, erasure, connection custody and whole-business exports remain restricted. New functional grants start with a zero refund ceiling and another-person approval; native administrators retain their prior behavior until configured. Customer self-access uses the independently verified native email and returns minimal own-order summaries, never staff annotations or payment authority. ct approved these defaults with riders on 23 October 2026: single-role grants managed only by the owner, a zero refund ceiling and another-person approval unless the owner changes them, refunds needing separate approval, customer custody through the independently verified native email, scoped apps issued only by the owner, and revocation or downgrade taking effect on the next request. API-001 supplies separately revocable scoped integration credentials; future CUSTOMER-001/002 and all new private doors inherit these checks.

    Acceptance evidence: Invite each role, perform its permitted workflow and try foreign customer, finance, bulk/export and direct API actions. Downgrade/revoke an active session/app grant during a prepared job and verify the next effect is refused without leaking private records.

  • AGENT-001 — Human approval of exact agent drafts. The human owner grants and revokes scoped, expiring agent access. An agent may prepare product, shipment and refund drafts; a signed-in human owner/admin approves their exact revision before publication, dispatch or money movement. Revocation, expired grants and stale revisions fail through the direct transport. Agents cannot approve themselves, grant authority, export/restore private data or erase a customer.

    Acceptance evidence: Grant an agent credential, prepare a product draft, attempt its approval/export/erasure as the agent and reject each, approve as a human, then revoke the grant and retry direct reads/writes. Prepare shipping/refund drafts through the same policy and require exact human approval.

  • API-001 — Documented headless API and signed events. An owner can build a custom/headless storefront using versioned catalog/cart/checkout/customer/order APIs and scoped integration credentials. Signed order/customer/stock/promotion/return events have stable IDs, minimal payloads, delivery history, subscription filtering and replay controls. Inbound signatures, origin checks, rate limits and idempotency prevent event or request reuse from creating duplicate commerce. Extensions and provider adapters do not require sharing administrative sessions. Current v1 apps require owner issuance, exact origin/scopes and independently authenticated native customer custody; customer email supplied in a body grants no access. Endpoint consent and each delivery/replay are explicit owner actions. Current events are order revisions, native customer creation, changed observed Pier availability, actual free-shipping promotion changes/qualification/redemption and native return requests/received-goods records, carrying only stable event/resource IDs, kind and occurrence time. RETURN-001 adds further return-state events before those capabilities ship. These authority and outbound-consent defaults await ct approval; connection-pinned outbound transport remains a partial gap.

    Acceptance evidence: Use a documented external storefront client to buy and view its own order, subscribe to signed events and reject a tampered delivery. Replay and reorder callbacks, revoke its credential and verify one commercial effect and bounded access.

  • FLOW-001 — Event and scheduled workflows with visible follow-up. Merchants configure order, customer, stock, promotion and scheduled triggers with conditions, quiet hours, responsible staff and due dates. Actions create tasks, notify staff, invoke approved integrations or prepare drafts under role/budget limits. Return/cancellation requests notify staff; confirmed returns drive stock work and sales drive accounting. Dry runs explain matching records; loops, duplicates and uncertain external effects stay visible and can be paused or reconciled. Current conservative defaults use owner/admin-managed rules, internal tasks/in-app alerts and explicit human preparation of a shipment draft from an open order task. Preparation binds current task/rule/assignee/functional authority, order revision and risk; a durable rule/order receipt prevents replay and output-revision loops. Assignment and completion never approve shipment or move stock or money. Confirmed received goods create assigned stock follow-up, not an assertion of restock. Other draft and reconciliation follow-ups require the separately authorized commerce door. Native return/cancellation requests use the independently verified customer email. Quiet hours and daily schedules use ORDER-001 shop time and its repeated/skipped-time rule. Restore preserves work history but removes local activation authority. These defaults await ct approval; RETURN-001/002 and ACCOUNT-001 still owe physical/financial resolution and accounting effects, and approved integration/budget actions remain required here.

    Acceptance evidence: Configure low-stock, overdue fulfillment, return-request and scheduled reconciliation rules; dry-run and activate them, replay events and stop a rule with pending work. Inspect one task/effect per event and correct owner/due date, not a silent failed background job.

  • INTEGRATION-001 — Owned connections and recoverable external work. Owners connect, test, rotate and revoke provider accounts, preview data mappings and see which data crosses each boundary. Secrets remain installation-local and encrypted under managed secret custody; connected apps have least privilege. Every outgoing payment, stock, label, mail, channel and ledger job has durable intent, provider correlation, attempts and a terminal or uncertain outcome. For current Stripe checkout/refund writes, the installation saves a commercial-only prepared intent before atomically claiming its only network write. Demonstrably unsent prepared work may make its first request after configuration is fixed; an unknown result is recovered only by reading its original provider reference or a bounded metadata-matched lookup. An absent, ambiguous, unavailable or truncated lookup never authorizes a replacement write. A recorded response means a reference was observed, not that payment or refund succeeded. Recovery queries the original operation before retry; backoff applies only to proven retryable work, and no automatic replay can duplicate an uncertain charge, shipment or message. Current Pier order creation, payment handoff and dispatch record the original deterministic command ID, commercial fingerprint, Pier installation/customer, provider correlation, committed attempts and observed or uncertain result. Recovery reads the original installation’s current order/shipment state first, then replays the identical command ID and intent under Pier’s atomic durable-receipt protocol: it retrieves the original result or commits its first effect if absent. Changed intent is refused; a new command identity is never substituted. Same-owner key rotation preserves Pier’s command actor; a different actor remains subject to Pier’s refusal. Matching complete dispatch observations may close the original uncertain shipment without another command. DONE covers every currently shipped Stripe/Pier capability; PAY-001/002, STOCK-001/003, SHIP-001/002/005/006/007, MAIL-001, MARKET-001, CHANNEL-001/002/003/004 and ACCOUNT-001 inherit these custody, mapping, least-privilege and recovery obligations before adding a capability/provider/job.

    Acceptance evidence: Revoke/rotate an account during queued work, lose successful responses at each provider edge and restart the worker. Inspect pending/uncertain work, reconcile by original reference, and prove no new effect identity or secret appears in UI, logs, exports or restored authority.

  • SECURITY-001 — Guarded native commerce doors. The shop's native sessions guard desk, import and data endpoints on the server. Public catalog/checkout and signed provider events are explicit external doors; browser mutations require the configured origin. A member, anonymous caller or revoked agent cannot gain private commerce access, approval or owner-only data authority by calling transport directly. Inputs are bounded and secrets/card details never belong in client bundles.

    Acceptance evidence: Call private state, product commands, imports and exports anonymously/as a member; attempt cross-origin browser mutation and an agent approval; revoke the grant and repeat. All fail without the prohibited write or private response, while public catalog and valid checkout remain usable.

  • DATA-001 — Validated archive and inactive receiving authority. Browser and RER CLI archives preserve the complete supported product data, commercial/approval/provider history, import source custody and erasure journal. Validation of version/schema/integrity and semantics precedes atomic restore into empty product data; the receiving owner, sessions and provider configuration remain local. Source agent tokens, sessions and connection secrets never become destination authority, and restore never repeats a charge, shipment, refund or message. Tampering and nonempty destinations fail without partial publication.

    Acceptance evidence: Export a populated shop with imports and commerce history, restore through the public portability doors into an empty installation and reconcile records. Attempt changed bytes and a second restore, then try source session/grant credentials at the destination; verify refusal and no provider replay.

  • ERASURE-001 — Owner-directed contact erasure and backup fencing. The human owner confirms customer contact erasure after resolving unshipped orders and uncertain shipment/refund effects. The authorized transaction removes email, address and checkout request fingerprint, invalidates outstanding archive copies and writes the portability redaction fence and audit action while retaining anonymous commercial history. A later source journal makes restore reject a pre-erasure backup. Provider-held records and already downloaded/offline copies need separate owner action; an isolated old archive cannot know about later erasure.

    Acceptance evidence: Attempt erasure before shipment and with wrong confirmation, then resolve work and erase. Inspect retained totals/approvals with no contact/address/fingerprint; restore a post-erasure archive and refuse an old archive when supplied the later journal, with no partially restored rows.

  • AUDIT-001 — Durable attributable commercial action history. Current product prepare/approve, shipment, refund, reconciliation, agent-grant/revoke and customer-erasure actions retain actor or agent-grant identity, opaque subject, action and time alongside immutable approval/provider references. History survives customer contact erasure and product archive transfer. The UI may page history but must not imply its display window deletes records or makes the store's audit tamper-evident.

    Acceptance evidence: Run a purchase, human approvals, reconciliation, agent grant/revoke and erasure through public commands, read activity and export/restore the shop. Verify relevant actor/action/time and approval/provider references remain without restoring erased customer contact.

  • OPS-001 — Owned installation, recovery and explicit operating limits. The merchant can install, set up, run, build, verify, export/import, diagnose and deploy the shop through Base's pinned RER command path while retaining owner data/settings. Health, provider readiness, background-job backlog, durable failed/uncertain outcomes and storage limits are visible. Backups and restore drills include outstanding work; costs separate hosting/storage, processors, tax, carrier, channel and AI usage. No author license check or kill switch controls ordinary shop operation; optional providers are named dependencies, not hidden telemetry. This applies to every capability that exists today. New server paths and provider/background capabilities (OPS-002, PAY-001/002, TAX-001, SHIP-001/002/005/006/007, MAIL-001, MARKET-001, CHANNEL-001/002/003/004, ACCOUNT-001 and AI-001/002/003/004/005) inherit readiness, durable outstanding outcomes, backup/recovery, explicit limits and separate cost declarations before shipping; this clause does not claim those capabilities exist. Configured connections are distinguished from timestamped provider observations, which remain historical after restore or rotation. Current lists cap at 100 with full counts and explicit truncation; the automatic payment check considers at most 20 orders created within the preceding 25 hours, and older outstanding orders remain visible for manual reconciliation. No sustained-throughput or maximum-store-capacity claim follows from these processing bounds.

    Acceptance evidence: Follow the fresh-clone RER journey, retain owner/data/settings across reruns, export/restore, stop/restart and diagnose an unavailable required provider. Inspect health and outstanding jobs, bounded storage/cost declarations and outside requests; no claim of capacity, zero egress or hosted readiness is inferred from a local build.

  • OPS-002 — Run Stall on the owner's own computer or own server. A merchant runs Stall on their own computer or on a server they control. On a computer with git, the one line npx -y @runeditrun/rer dev just-every/run-stall clones, installs, sets up a local owner and starts the shop with empty real business state, and rer deploy publishes the same checkout to the owner's own Cloudflare account. A documented production path runs the built shop on an owner-operated Linux server (a VPS or on-premises machine) with durable database storage, HTTPS on the owner's domain, a supervisor that restarts it after a crash or reboot, backups through the DATA-001 archive and upgrades that apply migrations; it keeps serving without the development server's idle stop and needs no account from Stall's authors. Every path keeps owner data and settings across restarts and upgrades.

    Acceptance evidence: On fresh macOS, Linux and Windows (WSL2) machines with git, run the one-line start and verify the shop opens with a local owner and no demo data. Deploy the same checkout with rer deploy to an owner's Cloudflare account, sign in and buy through checkout. Follow the server guide on a fresh Linux VPS: serve the shop over HTTPS on a test domain, take an order, reboot the server and verify it returns with the order intact, leave it idle for more than 12 hours and verify it still serves, then upgrade to a newer release and verify migrations apply and the data remains.

  • BASE-001 — Preserved Base guarantees with scoped replacements. Base authentication, input safety, portability, erasure, audit and independent ownership remain obligations. Current hosted Stripe card custody replaces local card handling; Pier owns physical stock/dispatch; plain-text descriptions replace arbitrary product HTML. Current archives exclude installation authority rather than cloning it and the receiving owner reconnects providers. BASE-001 is done once every product door Stall supports today is shown to conform: native authentication and authorization, hostile plain-text/import safety, archive, erasure and audit coverage, and secret exclusion. These are limited product policies, not blanket exemptions: every future clause adding rich content, theme/content/media, customer accounts or a new provider/integration must meet these guarantees, including sanitization, authorized uploads, scoped egress, credential exclusion and erasure coverage, before it can ship. Current conformance does not mark any future feature as passing.

    Acceptance evidence: Demonstrate conformance through every currently supported product door: exercise native authentication and direct-door authorization, archive/erasure/audit journeys, hostile plain-text product/import text and unsupported input, and inspect export/client bytes for secrets and authority. BASE-001 is done only when all those current doors conform. Before any future rich-content/media/provider clause ships, exercise its public upload/render/connect/erase doors under the same guarantees and document any explicit replacement with evidence; absent future features are not passing acceptance.

  • OPEN-001 — Free and open source under the MIT license. Stall is free and open source under the MIT license: the repository's license and the package declare MIT, and anyone may run, modify and redistribute it. Every capability that exists today ships in the open-source product with no license key, seat, product, order or revenue cap, per-transaction fee, paid gate or upgrade prompt from Stall's authors. Each future clause that adds a capability or provider inherits this obligation before shipping, including PAY-001, SHIP-001/002, MAIL-001, MARKET-001, ACCOUNT-001 and EXTEND-001; OPEN-001 does not claim those capabilities exist. Paid third-party services a merchant connects (Stripe and PayPal processing, Stripe Tax/Avalara/TaxJar, ShipStation/Shippo/EasyPost labels, SendGrid/Twilio, channel and accounting apps, hosting) are billed by those providers, and Stall names the provider and links its pricing before the connection is enabled. Stall replaces Shopify, Squarespace Commerce, BigCommerce and WooCommerce through MIGRATE-001/002/003/004; it is not affiliated with them.

    Acceptance evidence: Verify the repository's LICENSE is the MIT license and package.json declares MIT. Install from the public source with no account or key from Stall's authors, publish 200 products, add 10 staff and take 1,000 test-mode orders with no payment, license, cap or upgrade prompt and no fee added by Stall to any order. Begin enabling each supported provider (Stripe and Pier today) and verify its name and pricing before activation; repeat this journey when PAY-001, SHIP-001/002, MAIL-001, MARKET-001, ACCOUNT-001 or EXTEND-001 adds a provider.

Product separation and specialist extensions

  • BOUNDARY-001 — Separate products with usable commerce connections. Stall remains a complete storefront/retail commerce product. Pier owns multi-location warehouse inventory, purchasing and wholesale operations; Stall consumes availability and submits reservations, dispatches, quantity adjustments and accepted returns, and keeps simple store-managed retail counts only when no stock system is connected (STOCK-003). Mango owns the broader marketing product. A merchant may use other stock/marketing systems through documented adapters; neither sibling is required to sell, edit pages, manage customers or operate Stall's commerce record. Shared code never merges their products.

    Acceptance evidence: Operate the storefront/order desk with a documented alternate stock/marketing adapter, then connect Pier/Mango and inspect the handoffs. Verify warehouse purchasing/wholesale work and cross-campaign marketing open the linked product while retail orders and recovery remain manageable in Stall.

  • EXTEND-001 — Subscriptions, POS, digital downloads and creator fulfillment partners. Optional specialist adapters cover recurring product subscriptions via Stripe Billing or a subscription provider, physical POS via Square/Stripe Terminal, and creator production/print-on-demand via Fourthwall or Printful/Printify where their supported interfaces permit. Digital download products sold alongside physical goods deliver files from owner storage through expiring, download-limited links after verified payment, with no shipping or stock, and a refund revokes the link. The shopper sees renewal/fulfillment/cancellation terms and the merchant sees linked orders, refunds and stock/accounting effects. Required partner apps, agreements, payment-device/native work and unsupported source objects are explicit delivery work; partner ownership never excuses a broken commerce handoff.

    Acceptance evidence: Connect the selected subscription, POS and production provider test accounts; renew/cancel a subscription, complete/refund a POS sale and track a made-to-order product. Buy a digital download with a physical item, download it within its limit, exceed the limit and refund to verify the link stops. Reconcile linked retail orders, tax, stock and payouts, and surface provider rejection without claiming fulfillment.

  • EXPAND-001 — Multiple stores, regions and currencies. A merchant can operate separate branded storefronts/channels with regional price lists, languages, currencies, domains, tax/delivery settings and staff access while retaining an explicit source for each order. USD/US is the first supported buying journey, and selling to Canada and other countries in USD from the same store is already SHIP-001/002; this clause adds local currencies, languages and regional storefronts, which use configured providers and jurisdiction rules rather than silently reusing US defaults. Exchange/refund amounts retain original currency and reported conversion basis.

    Acceptance evidence: Create a second storefront with a different catalog/price list, locale and currency; buy, partially refund and report in each. Verify domain/catalog/role isolation, original-currency reconciliation and refusal of a region lacking configured tax or delivery support.

  • B2B-001 — Business buying without absorbing wholesale operations. Business customers can use approved company accounts, tax-exemption evidence, contract price lists, quote requests, purchase-order references and approved net terms in the storefront. Pier or the merchant's wholesale/order-credit system owns wholesale fulfillment, procurement and credit policy; Stall presents linked quote/approval/payment status and does not grant terms itself. Accounting and tax mappings reconcile the accepted business order.

    Acceptance evidence: Approve a company buyer, submit a quoted basket/PO, receive authorized pricing/terms from Pier or a wholesale adapter and accept it in the store. Reject an unauthorized employee or expired exemption; reconcile the approved order, shipment and QuickBooks invoice without a second wholesale ledger.

Push further: agents operate the commerce job

  • AI-001 — Operate order exceptions to shopper-approved closure. An agent joins live payment/authorization, hold/reservation, location availability, warehouse, carrier scans and promised delivery data to detect oversells, stalled fulfillment or delays. It explains the actual order state to the verified shopper with source timestamps, prepares feasible substitute goods or delivery choices and tracks acceptance through fulfillment or cancellation/refund. Merchant approval binds substitution, spend and money decisions; the shopper explicitly agrees to changed goods/date/price. Unavailable evidence creates a staff task, never an invented delivery promise.

    Acceptance evidence: Create a paid stock shortfall and a carrier delay. Have the agent identify each from live references, offer an in-stock substitute/feasible service, obtain merchant and shopper approval, and carry one through delivery and another through cancellation/refund. Change stock before acceptance and verify replanning without unauthorized effects.

  • AI-002 — Manage returns end to end. An agent applies the merchant's versioned return policy to order, delivery and customer-supplied condition evidence, gathers missing facts, prepares eligibility/fee/exchange options and provider labels, and follows scans to staff inspection, accepted restock/quarantine, refund and accounting reconciliation. Staff confirm physical receipt/condition and disputed eligibility; a human approves money movement and replacement shipment against current state. The agent closes a case only when stock and financial/provider references agree and the shopper is informed.

    Acceptance evidence: Ask for a return in the authenticated customer experience, let the agent prepare policy-grounded options and a label, record a human inspection that changes one item's condition, then approve resolution. Lose a restock/refund response and confirm the agent reconciles both once and leaves a refused/disputed case with an assigned human.

  • AI-003 — Improve profitable conversion with measured experiments. An agent reads consented funnel/channel reports, variant cost, stock/lead time, shipping/payment fees, return rates and promotion outcomes to propose merchandising, bundle, placement or content experiments with contribution-margin forecasts. It cites the data/window and missing costs, proposes a small budget and rollback, and measures actual net margin and conversion after refunds. The merchant approves publication, prices, audience and discount spend; preapproved stop rules halt a losing experiment without silently raising spend.

    Acceptance evidence: With seeded measured store data (test-only visits, orders, variant costs, refunds and stock confined to the test suite) configure an experiment, inspect the agent's source-backed proposal and unknowns, approve a bounded change, then observe conversion lift with margin erosion/returns. Verify stop/rollback, stock feasibility and an honest inconclusive result where sample or cost evidence is inadequate. Repeat on a live store's recorded data before claiming production readiness.

  • AI-004 — Recover failed integration work without invented success. An agent correlates signed event IDs, immutable order revisions, provider payment/stock/label/mail/channel references and accounting entries to explain missing or contradictory work. It queries the original operation, proposes a scoped correction/replay and verifies resulting totals. Owners approve mappings, material ledger corrections and any irreversible effect; already-approved safe reconciliation can run within a revocable policy. An uncertain charge or shipment is never retried under a new identity just to make a dashboard green.

    Acceptance evidence: Lose a successful processor/stock/label/ledger response and supply an out-of-order event. Inspect the agent's cited diagnosis and proposed correction, approve the material action, and verify one external effect and matched stock/money/ledger totals. Revoke policy during work and confirm it stops before a new effect.

  • AI-005 — Grounded merchandising and channel preparation. An agent proposes product copy, alt text, structured attributes, SEO, collection grouping and channel mappings from approved merchant facts, images and variant data. It flags unsupported claims and missing size, material and safety information, previews changes and feed validation, and never fabricates inventory, certifications or customer reviews. Merchant approval publishes the exact revision; measured conversion and margin feedback can inform the next proposal without granting autonomous publication.

    Current door semantics: personally credentialed external agents submit cited changes from an approved catalog-only source bundle. Text retains source values exactly, joined with a middle dot; image text cites the merchant's exact uploaded image description. The signed-in human owner or administrator previews a selection and approves its exact proposal revision. Product and collection sources are fenced in the publication transaction. The derived Google product draft reads timestamped Pier availability and reports missing evidence or validation failure; it grants no connected-channel publication. CHANNEL-001 and CHANNEL-002 retain connected publication and synchronization duties. Measured feedback may guide an agent's choice of supported changes without granting publication authority; AI-003 retains measured experiment duties. Product-only provenance travels in exports and archives; restored proposals are history and require fresh preparation.

    Acceptance evidence: Provide an incomplete product and image set, inspect proposed text and attributes with source citations and unanswered questions, approve selected changes and validate the channel draft. Edit a source fact before approval and verify the stale draft cannot publish; fabricated certification and review requests remain unapproved.

Honest boundaries

  • Money and tax infrastructure: Stripe/PayPal and wallets hold payment credentials and move funds; Stall owns checkout, permissions and reconciliation (PAY-001/002/003). Tax calculation connects Stripe Tax, Avalara or TaxJar (TAX-001); merchant registration, legal nexus decisions and tax filing remain with the merchant, adviser or contracted filing partner. Those are provider handoffs, not reasons to omit calculated checkout tax or refund adjustments.
  • Physical operations: USPS/UPS/FedEx and shipping providers supply rates, labels and tracking (SHIP-001/002/003). Staff or fulfillment partners confirm physical receipt and condition (RETURN-002). A database status alone is not proof of delivery, returned goods or safe merchandise.
  • Neighboring products: Inventory/warehouse purchasing and wholesale operations remain in Pier; cross-campaign marketing remains in Mango (BOUNDARY-001). Accounting books live in QuickBooks Online/NetSuite (ACCOUNT-001). Stall still completes its own customer-facing order, return and recovery workflows and exposes failures across those connections.
  • Specialist breadth: Recurring billing, physical POS and creator production use the usable adapters in EXTEND-001; business buying and international/multiple storefront expansion have explicit B2B-001 and EXPAND-001 requirements. Provider apps, agreements, native/device work and partner API limitations are engineering work with visible acceptance, never grounds to fold or shrink Stall.
  • Shopper conversations: live chat and a shopper messaging inbox belong to the help-desk product, sibling HappyToHelp or Gorgias/Zendesk, which receive Stall's contact-form submissions (STORE-003) and verified order context through API-001; Stall still sends every order notice itself (MAIL-001).
  • Incumbent-only networks: Shop Pay's saved-shopper network and Shop Pay Installments belong to Shopify and cannot be migrated; Link, PayPal and the pay-later methods in PAY-001 replace them, and saved-buyer conversion has to be rebuilt. Pirate Ship has no public label API, so labels use ShipStation, Shippo or EasyPost (SHIP-002) or manual fulfillment with a typed tracking number (ORDER-002).
  • Ownership and capacity: Large media lives in owner-controlled object storage with bounded processing jobs, not an unbounded Worker request; uploaded content must have authorized access, safe rendering, portability and erasure (BASE-001). Hosting/load/cost, email inbox receipt, live wallet eligibility and carrier delivery are measured separately. No scale, compliance certification or guaranteed conversion claim follows from a local test.

Migration mapping references

The target adapters must verify the merchant-specific source version, permissions and extraction coverage. Official references informing that work are Shopify product CSV and order exports, Squarespace products and orders, BigCommerce management APIs and customers/subscribers, WooCommerce REST, Medusa Admin, Saleor GraphQL and Fourthwall commerce APIs. Export formats can omit data that another authorized API or reviewed supplement must recover; those references establish source surfaces, not completed Stall adapters (MIGRATE-006).

Homepage claims

Every capability claim on the homepage built on the owner-approved structure page-s1 (src/site/landing/, 18 October 2026; one shop, Fog & Clay, through one kiln batch) maps to the clauses that promise it, with the code that backs it today. A claim's status is done when every mapped clause is done (backed by code), missing when every one is missing (contract, not yet in code), and partial otherwise (partly in code). The sample shop, orders and figures in the drawings (kiln.ts) are illustrations, not claims; the honest-limits strip ("No warehouse purchasing, live chat or Etsy listings.") states what Stall leaves to Pier and the help desk (Honest boundaries, BOUNDARY-001) and is true of the code today. 42 claims: 8 done, 24 partial, 10 missing.

# Section Claim Clause(s) Backing in code today Status
1 Hero "Stall puts your shop online" HTTP-001 src/routes/shop.tsx; src/stall/ui/shop.tsx done
2 Hero "storefront" STORE-001, STORE-002 src/stall/ui/shop.tsx; src/stall/discover.ts (one fixed branded shop with collections, search and product pages; no theme library) partial
3 Hero "checkout" CART-001, PAY-003 src/stall/checkout.ts; src/stall/stripe.ts; src/stall/payments.ts partial
4 Hero "sales tax" TAX-001 — partial
5 Hero "labels and tracking" SHIP-002, SHIP-003 src/stall/fulfilment.ts (approved shipment with a reference) partial
6 Hero "returns" RETURN-001, RETURN-002 src/stall/refunds.ts (person-approved line refunds) partial
7 Hero "the carts people left behind" RECOVERY-001 — missing
8 Hero "100% free, open source" / "Free and open source, MIT licensed." OPEN-001 LICENSE; package.json; src/stall/ui/connect-forms.tsx (provider costs before connecting) done
9 Hero "alternative to Shopify, Squarespace Commerce and BigCommerce" MIGRATE-001, MIGRATE-002, MIGRATE-003 src/stall/imports/* partial
10 Hero "Try the demo" DEMO-001 src/demo.ts; src/stall/demo/*; src/site/shell/links.ts; tests/ui/demo-journey.mjs done
11 Hero Drawn: the shop page on the booth wall ("Fog mug · $38 · 3 left", Add to cart) STORE-001, STOCK-001 src/stall/ui/shop.tsx (published products with live Pier stock) partial
12 Sunday · Move in "Products, customers, orders and redirects come over from Shopify in one import." MIGRATE-001, MIGRATE-006 src/stall/imports/csv.ts; src/stall/imports/service.ts (product CSV only) partial
13 Sunday · Move in Drawn: variants and gift cards imported; products missing a weight flagged and fixed MIGRATE-001, CATALOG-001 src/stall/imports/service.ts (dry run, apply, journal and undo) partial
14 Sunday · Move in Drawn: git clone …, cd stall, rer install, rer setup, rer dev start Stall on your own computer OPS-001, OPS-002 SEED-COMMAND-CONTRACT.md; rer-project.json; tests/clone-journey.mjs partial
15 Friday 9:40 PM · New batch "Photos, prices and stock for the new batch" CATALOG-001, STOCK-001 src/stall/products.ts (exact-cent prices, reviewed publication); src/stall/media.ts (galleries); src/stall/pier.ts (stock) partial
16 Friday 9:40 PM · New batch "set to go live on its own" (scheduled publishing) CATALOG-001 src/stall/listing.ts (a publish time); src/stall/products.ts done
17 Friday 9:40 PM · New batch Drawn: channels Online store, Google Shopping, Instagram CHANNEL-001 — missing
18 Friday 10:00 PM · The drop "Apple Pay, Google Pay, cards" PAY-001 src/stall/stripe.ts (Stripe hosted Checkout; wallets untested) partial
19 Friday 10:00 PM · The drop "and codes" PROMO-001 src/stall/promotions/index.ts (bounded free-shipping codes only) partial
20 Friday 10:00 PM · The drop "Each mug is held for ten minutes at checkout." STOCK-002 src/stall/checkout.ts; src/stall/payments.ts (check before checkout, reservation after payment; no hold) partial
21 Friday 10:00 PM · The drop Drawn: the collection page STORE-002 src/stall/discover.ts; src/stall/collections.ts; src/stall/ui/shop.tsx done
22 Friday 10:00 PM · The drop Drawn: discount, shipping rate and sales tax in the checkout total CART-001, PROMO-001, SHIP-001, TAX-001 src/stall/checkout.ts (product lines only) partial
23 Friday 10:43 PM · Sold out "When a hold runs out, the mug goes back on sale" STOCK-002 src/stall/payments.ts (shortfall shown after payment) partial
24 Friday 10:43 PM · Sold out "and the shopper gets a note with what is still in stock." RECOVERY-001 — missing
25 Friday 10:43 PM · Sold out Drawn: carts left, came back and recovered dollars RECOVERY-001, ANALYTICS-001 tests/api/commerce.test.mjs; recovery remains unimplemented partial
26 Interlude "38 orders while you slept" (orders complete without you) PAY-003 src/stall/payments.ts (signed webhook records payment and reserves stock); the count is sample data done
27 Saturday 8:00 AM · Packing day "Live USPS and UPS rates" SHIP-001 src/stall/shipping-charge.ts (owner-set free or flat shipping; no live carrier rates) partial
28 Saturday 8:00 AM · Packing day "addresses checked" SHIP-001, SHIP-005 src/stall/shipping-charge.ts (owner-set shipping; no address verification) partial
29 Saturday 8:00 AM · Packing day "labels printed" (every label in one run) SHIP-002, SHIP-005 — missing
30 Saturday 8:00 AM · Packing day "and tracking emails sent." SHIP-003, MAIL-001 src/stall/fulfilment.ts (shipment reference; no email) partial
31 Tuesday 2:14 PM · The order agent "The order agent reads the carrier exception" AI-001, SHIP-003 src/stall/orders.ts (shortfall and lost-response states) partial
32 Tuesday 2:14 PM · The order agent "checks live stock" STOCK-001 src/stall/pier.ts partial
33 Tuesday 2:14 PM · The order agent "offers the customer a real choice" AI-001 — partial
34 Tuesday 2:14 PM · The order agent "and you tap Ship." AGENT-001 src/stall/api.ts; src/stall/fulfilment.ts (a person approves the exact draft) done
35 Tuesday 2:14 PM · The order agent Drawn: replacement shipped, the price difference refunded and a carrier damage claim filed ORDER-003, ORDER-004, SHIP-002 src/stall/refunds.ts (line refunds) partial
36 Oct 27 · Returns "Customers start a return from their account." RETURN-001, CUSTOMER-001 src/stall/returns/cases.ts; src/stall/ui/return-help.tsx (account and private-link order page) partial
37 Oct 27 · Returns "Label, receipt, restock and refund stay in one record." RETURN-002, AI-002 src/stall/refunds.ts (reconciled refunds, no restock) partial
38 Oct 31 · Month end "Sales tax ready to file" TAX-001 — partial
39 Oct 31 · Month end Drawn: nexus over the last 12 months by state TAX-001 — partial
40 Oct 31 · Month end "and every sale posted to QuickBooks." ACCOUNT-001 — missing
41 Oct 31 · Month end Drawn: a payout line matched to its refund ACCOUNT-001 — missing
42 Closing "Open source online shops for makers." OPEN-001 LICENSE; package.json done

Status

Judged from the code and tests at commit 66ce5e9be39baa833aa221018ba6a044e758dfb6 (28 October 2026).

The per-clause rows below record the current implementation, named public-door proofs and remaining work. Historical source audits do not certify later capabilities. MIGRATE-007 is PARTIAL under CT's 26 October ruling; its export proof has been extended in this round without waiving any original duty. Exact-SHA Verify and the fleet publication and landing gates remain required. ANALYTICS-001 remains partial pending ct approval of its adopted policy boundary; its current row and named public-door proofs supersede the historical audit baseline.

done means the stated current slice has implementation and a relevant checked-in public journey/test. partial means cited code implements only part or the full public journey remains unproven. missing means no implementation of the named promise was found. Target/provider acceptance remains required by ACCEPTANCE.md. New product data must extend archive, security, audit and erasure coverage; current done slices do not automatically prove future records. Existing seed metadata describes the current release and does not limit this target.

22 October, sx-stall-c12: ct's 21 October ORDER-001 split uses its approved parser fallback because pinned rer check refuses lowercase suffixes: ORDER-001 is the current-order clause (a), ORDER-006 is risk/draft invoices (b). Its full ruled acceptance is unchanged. New staff records inherit archive/export/audit/erasure duties; current providers receive no internal notes/tags or staff payment reference.

22 October, sx-stall-c15-land: PROMO-001 and RETURN-001 move from missing to partial under ct's 22 October ruling on their API slices, using ct's Evidence and Gap wording: PROMO-001 for explicit free-shipping codes through documented HTTP doors, RETURN-001 for customer request intake only (the owner/admin received-goods record is RETURN-002 work, not RETURN-001 evidence). Neither is done until every acceptance point passes, including the named screens at 1440 and 390.

Clauses Done Partial Missing Total
Published 1 0 0 1
Target and push further 23 28 27 78
All 24 28 27 79
Clause Title Kind Status Evidence Gap
HTTP-001 Real installed and published HTTP surfaces published done src/server.ts; src/base/static-assets.ts; tests/runtime.mjs; tests/ui/journey.mjs
DEMO-001 Hosted demo shop that sends nothing target done src/demo.ts; src/stall/demo/providers.ts; tests/api/demo.test.mjs; tests/ui/demo-journey.mjs; .github/workflows/demo-acceptance.yml DEMO-001 HTTP tests cover seed-once, sample history/drafts/grant, outbound-free purchase/approvals/invite, empty ordinary installs and production build/deploy refusal. Hosted acceptance follows the built homepage link to production’s real human-check entry and exercises the exact-SHA sample shop on the separate admitted test-key host, then removes that host.
STORE-001 Merchant themes, page builder and custom domain target partial src/stall/ui/shop.tsx; src/stall/ui/primitives.tsx A fixed branded storefront exists; the theme library, switching, duplication, export/re-import, visual building, storefront password, domain management, revision controls and a measured performance run are absent.
STORE-002 Navigation, collections and product discovery target done tests/api/commerce.test.mjs — 'STORE-002: collections, menus, search, filters, synonyms and pins agree with the published sellable catalog' proves hand-picked and rule-based collections, menus, search by name, SKU, variant SKU and attribute, combined filters with consistent counts, sorts, pagination, publication and stock changes reaching the public results, the no-results state, synonym and pin effects, suggestions that exclude private products, the search report, owner/admin-only changes and archive restore. tests/ui/discovery-journey.mjs proves, at 1440 and 390, the desk's collection, menu, synonym, pin and search-report screens and the shop's collection landing page, filters, saved URLs, predictive suggestions, no-results state and live stock and publication changes.
STORE-003 Content, blog, contact, newsletter and search visibility target missing No implementation found. Target journey not implemented, including the contact form and newsletter signup.
MOBILE-001 Accessible mobile shopping and merchant work target partial src/stall/ui/shop.tsx; src/stall/ui/app.tsx; tests/ui/journey.mjs The existing narrow shop/desk journey covers both widths; expanded flows and full accessibility conformance are unimplemented or unverified.
MOBILE-002 Native merchant apps and timely order attention target missing No implementation found. Target journey not implemented.
CATALOG-001 Products, variants and media target done tests/api/commerce.test.mjs — 'CATALOG-001: variants, galleries, handles and listing states sell the exact variant and keep immutable order history' proves variants with their own SKUs, prices, compare-at prices and customs/weight facts, a multi-image gallery with alt text and its content-typed upload refusals, handle uniqueness, publication only against active Pier items, public media only while published, the exact variant purchase, a later price change and variant archive that leave order snapshots intact, scheduled and archived states, and variants and media through export and archive restore. tests/api/data.test.mjs — 'CATALOG-001: exact approved metadata stays private until publication, renders typed facts and travels without losing purchased descriptions' proves cost, weight, dimensions, tax category, HS code, origin and the size-chart custom field; 'CATALOG-001: personalization is validated, priced and carried to the order, packing slip, confirmation, exports and erasure' proves the 20-character +$5 engraving and artwork upload, refusal of over-length text and disallowed or mismatched files, the add-on price on the checkout total, order, packing slip, confirmation email and exports, private staff-only files, archive restore and erasure. tests/api/commerce.test.mjs — 'STORE-002: collections, menus, search, filters, synonyms and pins agree with the published sellable catalog' proves the collections a product joins. tests/ui/catalog-journey.mjs proves, at 1440 and 390, the desk editor for variants, images, custom fields and personalization, approval, the product page's gallery, option choice, size chart and personalization checks, the basket and order summary, the order's selection and the packing slip.
CATALOG-002 Bulk catalog operations and portable files target done tests/api/imports.test.mjs — 'CATALOG-002: exact rejected-row acknowledgement applies only valid rows with complete source custody', 'CATALOG-002: bulk catalogue review, bounded resume and undo preserve native edits and custody', 'CATALOG-002: undo preserves a real paid order and its published product while reversing unused imports', and 'CATALOG-002: reviewed metadata CSV survives resume and restore, exports exact facts, and protects later native work on undo' prove mixed previews, exact apply, full native product and collection fields, current authority, bounded resume after transfer, duplicate-safe replay, complete CSV and JSON exports, original source and rejected-row custody, and undo preserving native edits, paid variants, collection references and later shipping assignments. tests/ui/bulk-products-journey.mjs proves basic and complete grid and native file edits, full field review, stale-review refusal, bounded retained-source resume, native CSV download, per-row outcomes and protected undo through the merchant desk; its changed screens are captured at 1440 and 390. Push Verify loads this journey in the review-browser shard.
CATALOG-003 Bulk quantity adjustments through the stock authority target missing STOCK-003's store-managed stock authority and Pier's future scoped stock-adjustment command are required; Stall's current Pier key cannot call it. No executed grid/CSV journey proves once-only quantity adjustments in either authority with matching references. Inherits STOCK-001/STOCK-003.
STOCK-001 Live availability through Pier or another stock system target partial src/stall/pier.ts; src/stall/connections.ts; src/stall/payments.ts; tests/api/commerce.test.mjs Pier bin availability and paid-order reservations exist; the owner connects Pier (address and Pier-issued key) and Stripe on Settings → Provider connections, sealed in Stall's database and read per request (src/stall/connections.ts), with server settings as an override; selling still requires Pier (checkout binds every order to the Pier origin/customer). Configurable location/backorder policy, Stall-originated quantity adjustments and alternate adapters are absent.
STOCK-002 Expiring checkout holds and stock race resolution target partial src/stall/checkout.ts; src/stall/payments.ts; src/stall/pier.ts; tests/api/commerce.test.mjs — payment survives a lost Pier response and duplicate delivery reserves only once BLOCKED on Pier: the current Stall-scoped credential permits only order.create, order.channelPayment and dispatch.create. Pier must expose atomic bounded basket holds with expiry/release/conversion and deadline observations; its owner-only physical holds have no expiry or atomic conversion. Prepayment holds, expiry/failure/cancellation releases, competing-shopper remaining-time/payment refusal and shopper-approved shortfall closure remain unproved. A local second stock ledger would violate STOCK-001 authority.
STOCK-003 Store-managed quantities and untracked items without a stock system target missing src/stall/checkout.ts; src/stall/fulfilment.ts No implementation found: checkout and dispatch require Pier; untracked variants, store-managed counts and the opening-balance handoff are absent. Full connected-write acceptance is blocked on Pier scoped adjustment/handoff authority: native owner imports/counts exist, but the supported Stall-issued key cannot call them. Local stock modes, manual fulfillment and owner-file handoff remain same-seed implementation work.
CART-001 Persistent cart and guest or account checkout target partial tests/api/commerce.test.mjs — “native carts retain guest and account custody, exact checkout review and required field snapshots across retry” proves multi-line guest refresh, explicit verified sign-in handoff, foreign account/origin/caller-email refusal, native US address and preserved Canadian-address refusal, required text/choice/date-field schema and choice enforcement through the legacy checkout, exact item/shipping/discount/tax-status totals, price/unpublication errors preserving the cart, original Stripe checkout recovery after a lost response and later price change, shopper note/gift/field order snapshots, owner exports/grouped-answer reports, guest/account purchases, archive capability exclusion and customer erasure. HTTP slice only; storefront still uses its older tab basket/hosted address flow, and there are no native cart/address/field screens or 1440/390 proof. Canadian delivery, true gift-card/store-credit redemption (PROMO-002 ledger), provider tax, notes/messages on packing slips/confirmations, price-hidden gift receipts, field answers in the order-desk UI and provider-side address-change review remain unproved. Guest capability custody, explicit same-mailbox claim and restored-cart copy defaults await ct approval; no screen waiver or DONE claim.
PAY-001 US dollar cards, wallets, PayPal, pay-later and manual payments target partial src/stall/stripe.ts; src/stall/refunds.ts; tests/api/commerce.test.mjs Stripe card Checkout/refunds use USD; named wallets, PayPal, pay-later, manual methods and complete US payment acceptance are unimplemented or untested.
PAY-002 Authorization, capture, cancellation and disputes target partial src/stall/stripe.ts; src/stall/payments.ts; src/stall/orders.ts Canonical paid-session retrieval exists; distinct authorization/capture, void, dispute evidence and fee lifecycle handling is absent.
PAY-003 Verified payment and duplicate-safe paid reservation target done src/stall/checkout.ts; src/stall/payments.ts; src/stall/pier.ts; tests/api/commerce.test.mjs; tests/api/local-payments.test.mjs An online shop verifies signed webhooks; a shop on the owner's computer, which Stripe cannot reach, connects without a webhook secret (an invented one is refused) and confirms each payment by reading the Checkout Session from Stripe on the customer's return, every minute and on Reconcile, with the same session, amount and currency checks. Paid orders reserve in Pier with each line's unit price and USD, then send their Stripe payment reference through a separate scoped command without changing the reservation identity.
PROMO-001 Discounts, automatic promotions and controlled budgets target partial tests/api/commerce.test.mjs — 'promotion rules price code and automatic product, variant, collection, order, quantity rewards, spend rewards and bounded shipping through checkout quotes' proves both methods, exact selected-line cents, quantity and spend rewards, collection and variant targeting, destination and maximum-rate refusals, verified current segment eligibility and refused combinations; 'combined discount purchases bind net tax, odd-cent line refunds, single-use races and campaign events without duplicating paid totals' proves combined code and automatic allocations, original-line tax, exact net Pier price bands, partial refunds, unique single-use CSV codes, second-use refusal, an atomic code race and deduplicated campaign totals and events; existing 'free shipping promotions reserve real checkout budgets atomically and redeem only verified paid orders' and 'unpaid checkouts hold promotion budget only until Stripe reports they can no longer be paid' retain authority, cap, expiry and replay proof. tests/api/data.test.mjs — 'staff, customer carts, events and workflow history transfer without restoring authority and erase attributable follow-up' proves export, restored authority refusal and erased usage bindings. tests/ui/promotion-journey.mjs proves code and automatic rule editing, combinations, downloaded single-use codes through a paid checkout, code usage and reconciled campaign reports. Assertions run at 1440; changed screens are captured at 1440 and 390. Held Stripe Tax test-mode calculations, paid sale and original-line reversal were also exercised with the receipt retained separately by the fleet; payment remains on the network-edge fake. End-to-end cancellation and its stock and tax reconciliation remain unproved: the pinned Pier Stall credential authorizes order creation, payment evidence and dispatch, but not order.cancel. A supported scoped Pier cancellation door is required; no alternate warehouse credential or local stock ledger is used. Fully free baskets and refunds of zero-paid reward lines have no completed public journey. The existing positive-payment checkout and refund doors still require a positive provider amount. Production payment acceptance and downstream provider or accounting duties remain with PAY-001, TAX-001 and ACCOUNT-001. PROMO-001 stays PARTIAL; no original acceptance point is waived.
PROMO-002 Gift cards and stored redemption balances target missing No implementation found. Target journey not implemented.
TAX-001 US sales tax and exemptions target partial tests/api/operations.test.mjs — 'TAX-001: address-level Stripe previews preserve categories and discounted shipping without inventing rates' proves owner HTTP previews of two states and different streets in one ZIP, explicit product codes, exclusive USD cents, discounted shipping, matching references and durable totals; 'TAX-001: uncertain Stripe calculations recover only original intent after restart and archive restore' proves lost-response observation and original-reference recovery with no replacement POST; 'TAX-001: preview authority, consent, incomplete configuration and provider failures refuse unpriced tax' proves owner-only explicit boundary consent and useful configuration, credential and provider refusals. Stripe HTTP edge fake only; no live receipt. tests/api/operations.test.mjs — 'tax settings save exact local ship-from, SKU categories and nexus thresholds behind current owner authority' proves saved configuration, stale-write refusal, denied callers, audit and archive transfer. 'customer tax exemption evidence keeps exact owner review, optimistic revisions and inert portable custody' proves documented evidence, revocation, historical restore and erasure. tests/ui/tax-settings-journey.mjs proves settings, consented previews and useful provider refusal at 1440 and 390. tests/api/operations.test.mjs — 'taxed checkout binds address-level tax to exact payment and original paid-order references' proves two-state and same-ZIP address-level amounts, explicit taxable and non-taxable codes, existing net-shipping treatment, jurisdiction display data, exact payment, original paid-order references, stale-quote refusal and provider refusal before payment. 'tax exemptions require current evidence and an independently proven customer identity at quote and payment' proves evidence-bound exemption, guest refusal and revocation. 'tax refunds post in their own shop-zone filing period and liability CSVs and nexus reconcile to original orders' proves partial merchandise and shipping tax reversals, deterministic cents, shop-zone month boundaries, state and named sale-jurisdiction reports, contributing references, three CSV exports and configured threshold warnings. 'uncertain sale tax survives archive restore as original-reference observation without replacement or checkout authority' proves original Tax transaction retrieval after response loss and restore, preserved reporting and no new POST or restored sale authority. tests/ui/tax-commerce-journey.mjs proves owner enablement, jurisdictional tax before payment, paid-order tax, reviewed partial refund, reports and order drilldown at 1440 and 390. Provider-edge fakes cover the rest of the sale slice. Authentic Stripe Tax test-mode receipt (account acct_1URgLjDg8BoejKxo, held US test key through the injector): scripts/tax-live-receipt.mjs drives the real Worker with only the Stripe Tax calls reaching the actual Stripe API (payment stays on the local fake) and its recorded output is docs/tax-001-test-mode-receipt.json. It activated nothing itself: the fleet activated Stripe Tax (settings request req_PPHKhCjKEN80H9: head office in California, exclusive default behavior, general tangible goods default code) and registered California (taxreg_1UUbZXDg8BoejKxoGALMHzfb, request req_0C0mtNiD35Hbzy) and Washington (taxreg_1UUbnGDg8BoejKxogNqGetRe, request req_BqKJF5V3LaY8Ep). The receipt proves, against the real API: a consented owner preview; two addresses in ZIP 94063 charged their own address-level rate (198 and 188 cents on the same basket); taxed paid sales to Washington (state, county, city and district tax) and California with Stripe Tax transactions created from the quoted calculations; a documented exempt customer quoted at zero tax while the same guest quote carried 205 cents; shipping discounted by a promotion taxed once (211 against 228 cents); a partial line refund reversed through a real reversal transaction; and the liability report's state, jurisdiction and transaction CSVs reconciling exactly to the posted provider transactions with the reversal attributed over the original jurisdictions. The authentic labels it exposed (a nontaxable-coded line is reported as not_collecting with no taxable amount) are accepted only for such a line and its apportioned shipping; any other unpriced obligation still refuses. 'tax refunds post in their own shop-zone filing period and liability CSVs and nexus reconcile to original orders' now also proves refund tax split over the original provider jurisdictions with nothing unallocated and the last partial shipping return clearing every jurisdiction exactly. 'marketplace-facilitated sales are recorded as separate reporting evidence that counts toward nexus and never replaces existing evidence' proves owner-only consent, separate channel rows and totals, nexus counting, replay and conflict refusal and archive restore. 'taxed goodwill needs explicit confirmation, leaves recorded tax unchanged and posts a zero-tax adjustment' and 'a payment to a different address than the reviewed tax address is refunded in full with no tax recorded and never fulfilled' prove the two native remedies. tests/ui/tax-commerce-journey.mjs additionally proves the jurisdiction refund rows, marketplace entry, goodwill confirmation and different-address refund screens at 1440 and 390. Remaining unproved: provider-reported refund jurisdiction detail (Stripe's reversal names no jurisdiction, so Stall splits refund tax over the original sale's provider breakdown by what remains unreversed, a derived allocation awaiting ct approval); marketplace-facilitated sale ingestion from a connected marketplace (only the owner-recorded evidence door exists; marketplace connections belong to the channel clauses); the following-month refund and provider-outage points are proved by edge fakes because a live account cannot cross a month or fail on demand. Adopted defaults awaiting ct approval, in addition to the owner enablement, shopper consent, independently proven exemption identity, fresh local restore authority and configured-period nexus measurement defaults: (1) pro rata refund jurisdiction attribution from the original provider breakdown; (2) taxed goodwill needs explicit owner confirmation, never changes recorded tax and posts a zero-tax adjustment, while refunding items or shipping reverses tax; (3) a payment to a different full address is refunded whole under finance approval with no tax recorded and the order never fulfilled; (4) marketplace-facilitated sales are owner-recorded, content-minimal reporting evidence in separate channel rows and totals that count toward configured nexus. Native tax mode remains test-only; only the held US test account and test keys were used. TAX-001 stays PARTIAL; no original point is waived. CART-001, PROMO-001 and ORDER-005 inherit only this shared calculation boundary; their wider scope is unchanged. Approved preview riders remain in force.
RISK-001 Fraud indicators and human review target done tests/api/operations.test.mjs — “RISK-001: restricted advisory queue holds fulfillment, records human review and deduplicates callbacks” proves canonical low and flagged provider-test observations with provenance, the owner and administrator-only restricted queue (anonymous, member and agent credential refused), configured hold and refusal of shipment preparation and approval, authorized release and cancel recording the reviewer, one in-app alert per order and signal set despite repeated callbacks, cancellation moving no money and no Pier reservation, no automatic release or refund, a later flag leaving a separately authorized refund unaffected, audit history, and restore. tests/ui/risk-journey.mjs (run by tests/ui/staff-journey.mjs) — “riskJourney” proves the rules form, held, released and canceled queue with its fulfillment-only cancellation notice at 1440 and 390.
SHIP-001 Shipping zones, live rates, international USD shipping, pickup and delivery target partial src/stall/shipping-charge.ts; src/stall/checkout.ts; src/stall/stripe.ts; tests/api/commerce.test.mjs Owner-configured free/flat domestic US shipping is reviewed, charged through Stripe and retained on orders for shipping-only refunds. Zones, live carrier rates, international destinations, pickup/local delivery, profiles and handling promises remain absent; no postage or rate verification is claimed.
SHIP-002 Purchase, print and void carrier labels target missing No implementation found. Target journey not implemented.
SHIP-003 Split fulfillment, tracking and delivery exceptions target partial src/stall/shipment-sync.ts; src/stall/ui/order-panel.tsx; tests/api/commerce.test.mjs Owner refresh reads actual Pier partial/full dispatches, carton tracking and delivery status; split shipments are aggregated by order line. Stall can still prepare/approve a whole-order Pier dispatch. Carrier label purchase, tracking emails and wider delivery exceptions remain absent.
SHIP-004 Shipping profiles for specific products target done tests/api/shipping.test.mjs — 'SHIP-004: profiles price mixed baskets per service, refuse unserved lines before payment, and bulk reassignment invalidates open quotes while paid orders keep their profile revision and charge' proves the four configured profiles quoting one general and one oversized item to a US ZIP as a single UPS Ground option at exactly $31.00, the sticker leaving it unchanged, a furniture item removing shipped services while pickup and local delivery remain and the cause is named, the oversized item refused before payment (no provider session) for a ZIP its profile does not serve while the rest of the basket still quotes, bulk reassignment through the reviewed grid door and the catalog CSV invalidating the open quote and changing the next one, the earlier paid order keeping its profile revisions and $31.00 charge, an edited profile invalidating open quotes, free, flat, weight, price, handling and surcharge rates, 99 custom profiles and no more, the pickup order collecting no address, owner/admin-only changes, strict fields, and archive restore and records export. tests/ui/shipping-journey.mjs proves at 1440 and 390 the desk's profile form, pickup and delivery places, assignment review by grid and CSV, the product editor's profile, and the shop's ZIP quote, free-shipping item, furniture basket and unserved ZIP.
SHIP-005 Bulk label purchase and batch fulfillment target missing src/stall/fulfilment.ts No implementation found: fulfillment prepares and approves one whole-order Pier shipment at a time; batch selection, labels and combined documents are absent.
SHIP-006 Merchant shipping apps and 3PLs as fulfillment connections target missing No implementation found. Target journey not implemented: no ShipStation or 3PL order export or tracking write-back exists.
SHIP-007 Local pickup and local delivery fulfillment target missing src/stall/fulfilment.ts No implementation found: fulfillment has only an approved whole-order Pier shipment; pickup and local-delivery states, notices, lists and uncollected-order handling are absent.
ORDER-001 Complete retail order desk: current orders target done tests/api/commerce.test.mjs — 'ORDER-001: time zones and revision-checked staff assignments survive transfer without granting authority' proves owner zone save, member/agent refusal, canonicalization, UTC-preserving relabelling, inclusive 23/25-hour dates, assignment, history, changed catalog/provider-address snapshots and transfer; 'warehouse dispatches refresh into Stall without a second dispatch; partial work stays unfinished' proves the overdue partial filter and original dispatch references; 'manual paid sales reserve once, preserve commercial truth and record reviewed refunds without moving money' proves manual/storefront channels, check payment label, current price/shipping review, one recoverable Pier reservation, no_tax_recorded, no message, privacy and bounded recorded refunds with no processor call. tests/api/data.test.mjs — 'ORDER-001a: internal notes and tags require human staff, exact revisions and owner redaction', 'EXPORT-001: owner downloads independent-readable business CSVs, exact totals and complete commercial JSON', 'human confirmation erases contact details and outstanding archive copies', 'post-erasure archive restores commercial history and the import journal', and 'ORDER-001a: erasure removes a recorded payment reference and manual annotations through archive restore' prove note/tag authority, redaction, exports, attributable erasure and restored exclusion. tests/ui/journey.mjs → tests/ui/order-desk.mjs — orderDeskJourney proves manual entry/review, assignment/notes/tags/history, redaction, staff payment/refund labels, shop exclusion, zone relabelling, event-specific spring/fall offsets and erased attribution at 1440/390. tests/api/commerce.test.mjs — 'OPEN-001: an owned installation publishes 200 products, adds 10 staff and takes 1000 paid orders without author fees or gates' proves email/name/SKU search beyond 100, oldest matches and full counts; exact-candidate heavy-slot scale run sx-stall-c12-search-1000-20261021.
ORDER-006 Complete retail order desk: risk and draft invoices target missing Risk records/filter (RISK-001) and draft orders/payable invoices (ORDER-005) remain absent. Current paid manual and storefront orders are ORDER-001.
ORDER-002 Exact shipment approval and one dispatch target partial src/stall/fulfilment.ts; src/stall/pier.ts; tests/api/commerce.test.mjs Current whole-order approval checks Pier first; an already shipped or partly shipped order names its state and requires the remaining work in Pier. Key and restore refusals retain Pier’s reason. Actual Pier dispatches are read back on owner refresh; alternate-connector dispatch and manual fulfillment with typed tracking are absent, and carrier/partial-fulfillment breadth remains SHIP-002/003.
ORDER-003 Reviewed line refunds without duplicate money movement target done src/stall/refunds.ts; src/stall/refund-values.ts; src/stall/ui/refund-form.tsx; src/stall/shipping-charge.ts; tests/api/commerce.test.mjs; tests/ui/journey.mjs Named ORDER-003 HTTP and 1440/390 browser journeys prove item, partial/full shipping and goodwill refunds, exact revision approval before effects, lost-response recovery, repeat approval, pending/succeeded limits, full-value exhaustion, unchanged line quantities and no stock return. Paid shipping is a real owner-configured flat USD checkout charge; historical charge and refund categories survive exports/archive. Tax adjustments and ledger posting are inherited by TAX-001/ACCOUNT-001 before shipping.
ORDER-004 Versioned edits, cancellation and claims target partial src/stall/store.ts; src/stall/fulfilment.ts; src/stall/refunds.ts Revision checks exist for current drafts/effects; general edits, cancellation and claims are absent.
ORDER-005 Draft orders, custom lines and payable invoices target missing src/stall/checkout.ts No implementation found: orders start only from storefront checkout; staff drafts, custom lines and invoice links are absent.
RETURN-001 Customer self-service returns, cancellations and exchanges target partial tests/api/returns.test.mjs — “RETURN-001: eligible-line requests, policy, human decisions, exchange reservation and progress for account and guest customers” proves, through the documented HTTP doors and a real Pier Worker, the public policy and its owner-only revisioned save, per-line eligibility with the refusing rule (final sale, ended window, unshipped, quantity already requested), account and private-link partial return, size exchange and cancellation, refusal of another customer's order, another order's link and an unpublished policy, one case for a repeated request even through the link, private photos (type, size, custody, owner read, foreign refusal), the staff list without a workflow rule, person-only decisions with a required explanation (member, agent and stale revision refused), exchange reservation set aside once and refused when stock is gone, customer-visible explained progress, no order, payment, refund or stock change from requests or non-exchange decisions, export of cases and photo details, archive restore and erasure. tests/api/operations.test.mjs — “FLOW-001: current-source rules, native customer requests, cron, quiet pause and visible failed follow-up” proves the documented POST /api/stall/customer-requests intake and its configured task and notification. tests/api/data.test.mjs — “staff, customer carts, events and workflow history transfer without restoring authority and erase attributable follow-up” proves requests transfer with workflow history and customer erasure removes them. tests/ui/request-journey.mjs — “RETURN-001 policy, account and private-link requests, explained decisions and progress at 1440 and 390” proves the Settings policy form, the policy explanation, exchange request with a photo, cancellation, final-sale refusal, private-link request, another customer seeing none of it, the staff decision list and both customers reading the explained decisions and progress. Account and private-link order, shipment and refund history are CUSTOMER-003 evidence. Adopted conservative defaults await ct approval: possession of a private order link authorizes requests and photo reads for that one order; a request outside the written policy is refused automatically with its rule and no exception path exists in Stall; accepting an exchange reserves replacement stock in Pier on a person's decision and nothing releases it if the original goods never return (RETURN-002); photos are held privately until erasure with no expiry; staff notification is the in-app review list, with assigned tasks only through a configured FLOW-001 rule and no outbound message. Account holders are owner-invited or owner-approved registrants (CUSTOMER-001); open native signup remains CUSTOMER-001's Base dependency. Received goods, restocking, refunds and any fee are RETURN-002 and the refund workflow.
RETURN-002 Physical receipt, restocking and reconciled resolution target partial src/stall/refunds.ts; tests/api/commerce.test.mjs Reconciled line refunds deliberately avoid restocking; return authorization, labels, inspection and restock workflow are absent.
CUSTOMER-001 Customer directory, accounts and order history target partial tests/api/data.test.mjs — “customer directory resolves duplicates without granting account access and derives live net-value segments” proves normalized duplicate preview and apply, explicit directory-only merge, staff and agent refusals, tags and notes, paid order counts, net lifetime value and live tag/spend/count/state segments after purchase and refund; “native customer account recovers verified access, isolates addresses and preserves directory erasure through transfer” proves verified guest ownership, one-use native recovery, own-order and foreign-order isolation, US and Canadian versioned address custody, own return intake, export, archive and erasure and foreign restored-session refusal. tests/ui/customer-account-journey.mjs proves native account history and own address management at both widths. tests/ui/customer-directory-journey.mjs — “CUSTOMER-001 customer directory, reviewed merge, live segments and support metadata at 1440 and 390” proves import review, metadata-only merge, tags, notes, live paid-order and refund segment membership, merchant address editing with mailbox custody, staff restrictions and account-menu tooltips at both widths. tests/api/customer-registration.test.mjs — “public account requests require an owner decision and the real native email confirmation before access” proves explicit consent, no unreviewed account or mail, owner-only approval, single-use activation, immutable duplicate requests and expiry. tests/api/customer-history.test.mjs — “reviewed historical imports preserve exact facts without live effects and belong only to a newly proven native mailbox” proves reviewed exact-source import, stale preview refusal, own imported and new history, current net directory totals, foreign refusal, export, erasure and restore without authority. tests/api/customer-balances.test.mjs — “reviewed native balance commands are exact, replay-safe and visible only to the independently proven mailbox” proves exact cents, replay and stale-review refusal, independently verified mailbox custody, metadata-merge isolation, business export, transfer and erasure. tests/ui/customer-registration-journey.mjs, tests/ui/customer-history-journey.mjs, tests/ui/customer-balances-journey.mjs and tests/ui/customer-order-status-journey.mjs prove public request and native activation, reviewed historical import and own history, gift balances, current tracking, refund status, return intake and received-goods facts, with foreign-account refusal at 1440 and 390. Owner-enabled self-signup needs a supported Base native signup capability that can create a verification-pending member under durable owner enablement without a live inviter session. The supported individually owner-reviewed request path is proved. New defaults await ct approval: explicit necessary-account consent, owner approval before invitation, seven-day unverified identity retention and thirty-day request metadata retention; owner or administrator exact-cents balance approval, independently verified mailbox custody and an opaque immutable financial journal after erasure. Broader return policy and decisions remain RETURN-001; gift redemption and cash-out remain PROMO-002, delivered mail remains MAIL-001.
CUSTOMER-002 Consent, preferences and customer privacy target partial tests/api/data.test.mjs — “customer consent is explicit at every HTTP capture door and privacy refusal, GPC and erasure survive restore” proves subscribed/unsubscribed/unknown import with affirmative proof/refusals, separate channel history and withdrawal at checkout/account/newsletter/contact/popup HTTP doors, foreign identity/origin/role refusal, policy version/region settings, category/GPC preference mapping without outbound calls, checkout while refused, private account export and audited erasure requests without automatic effects, post-erasure suppression restore and refusal of an older archive with the later journal. HTTP slice only. No banner/persistent preference link or consent-capture screens at 1440/390, no delivered-message unsubscribe, geolocation or installed Google/pixel/conversion event resumption proof, and no automatic account deletion. Downstream suppression is MARKET-001/account-blocked (Mango/Klaviyo/Mailchimp). CT’s 23 October rider covers deny-until-current-policy-choice categories, wording version/time, import suppression and owner-reviewed privacy requests. The verified-session-only public capture and visitor-selected region defaults still await ct approval. Necessary mail delivery remains MAIL-001; no screen waiver or DONE claim.
CUSTOMER-003 One-click reorder from order history target done tests/api/commerce.test.mjs — “verified account reorder names current price and stock changes without spending before a new checkout” proves two-order history with dates, totals and status, newest-first ordering, current-price and stock changes into a separate unreviewed cart, valid personalization and shipping address reuse, named unavailable and fresh-upload omissions, no payment or stock effect before checkout, a distinct paid order preserving the original, foreign authority refusal, expiring and revocable one-order guest links, and restore without link authority. “native carts retain guest and account custody, exact checkout review and required field snapshots across retry” proves native guest cart custody, current field snapshots, guest-link erasure and exclusion from archives and business exports. tests/api/operations.test.mjs — “taxed checkout binds address-level tax to exact payment and original paid-order references” proves native Reorder cannot bypass enabled tax, carries the exact current address-level tax into review and payment, and retains its original explanation after cart edits. tests/ui/customer-account-journey.mjs — “customer account history, fresh reorder checkout, guest links and upload refusal at 1440 and 390” proves newest-first history with dates, items, status and totals, named current-price and sold-stock changes, persisted separate cart with no premature payment or stock effect, fresh checkout questions and current delivery review, a distinct paid order preserving its source, guest order and guest cart review, foreign-order refusal and fresh-file refusal at both widths.
MAIL-001 Transactional confirmations and delivery evidence target missing No implementation found. Shared sign-in mail infrastructure does not implement order/customer transactional notifications.
RECOVERY-001 Abandoned-checkout recovery to a valid basket target missing No implementation found. Target journey not implemented.
MARKET-001 Mango and consent-aware lifecycle marketing connections target missing No implementation found. Target journey not implemented.
CHANNEL-001 Google Shopping, Meta/Instagram, TikTok Shop and Pinterest target missing No implementation found. Target journey not implemented.
CHANNEL-002 Marketplace adapters without becoming a marketplace target missing No implementation found. Target journey not implemented.
CHANNEL-003 Ad pixels, conversion APIs and custom storefront events target missing No implementation found. Target journey not implemented.
CHANNEL-004 Embeddable Buy Button and checkout links target done tests/api/commerce.test.mjs — 'merchant checkout links preload native carts, preserve reviewed discounts and channel, and refuse stale sale authority' proves preloading, exact discounted totals, paid reservation, channel filters and exports, native custody, response-loss recovery, revocation and inactive restore; 'Buy Button, product card and collection embeds restrict exact origins and recheck native stock and publication' proves all three generators, exact-origin refusal, live prices, variants, stock and unpublishing; 'checkout links retain explicit guest tax consent and reserve promotions against tax-inclusive payments' proves guest consent refusal and exact taxed payment with one promotion use. tests/ui/buy-link-journey.mjs proves allowed external embeds and purchases, the two-variant discounted link, taxed and untaxed reviewed totals, Orders channel filtering, domain and availability refusals, revocation and account tooltips at 1440 and 390. docs/BUY-LINKS.md documents the HTTP generator and boundaries.
REVIEWS-001 Verified reviews, upsells and cross-sells target missing No implementation found. Target journey not implemented.
ANALYTICS-001 Sales, conversion and contribution margin target partial tests/api/commerce.test.mjs — “first-party analytics attributes consented sessions and verified orders without replayed, bot or invented visits” proves UTM, search, direct, source dimensions, exact conversion and consent unknowns; “sales reports reconcile refunds, ranked products, historical imports, exact costs and CSV drilldowns” proves refund money, history replay, channel and date totals, reference drilldown, exact margin, both rankings and exports; “analytics reports refuse foreign authority and restore historical observation without visitor or cost authority” proves access and inert archive restore; “checkout links retain explicit guest tax consent and reserve promotions against tax-inclusive payments” proves exact tax and shipping discount observations with test-payment exclusion. tests/ui/analytics-journey.mjs proves Reports, consent, cost settings, historical preview, drilldown, CSV and account tooltips at 1440 and 390. ct approval pending for the adopted 30-day capture retention, minimized commercial source retention and native owner or administrator report-access boundary above. Native accounting posting evidence remains ACCOUNT-001; absent references are labelled unknown. No original acceptance point is waived.
ACCOUNT-001 Reconciled QuickBooks Online and NetSuite posting target missing No implementation found. Target journey not implemented.
MIGRATE-001 Full reviewed Shopify migration target partial src/stall/imports/csv.ts; src/stall/imports/service.ts; tests/api/imports.test.mjs Only a bounded six-column product CSV stages simple unpublished products; full Shopify objects, media, variants, customers, orders, content pages, blogs, menus, discounts and redirects are absent.
MIGRATE-002 Squarespace Commerce migration target missing No implementation found. Target journey not implemented.
MIGRATE-003 BigCommerce migration target missing No implementation found. Target journey not implemented.
MIGRATE-004 WooCommerce and extension migration target missing No implementation found. Target journey not implemented.
MIGRATE-005 Open-engine and creator-store move-in target missing No implementation found. Target journey not implemented.
MIGRATE-006 Cutover completeness, source limitations and outstanding liabilities target partial src/stall/imports/service.ts; src/stall/imports/targets.ts; tests/api/imports.test.mjs Current product import binds reviewed source/native snapshots and protects undo; complete cross-platform cutover, media, redirects, customer activation and outstanding liability handling are absent.
MIGRATE-007 Product review and rating migration target partial tests/api/imports.test.mjs — 'Review move-in preserves source provenance, owned photos, exact mapping, replay and selective undo' proves both documented exports against a migrated catalog, handle and ID mapping, named orphans and remapping, original dates, exact Yotpo display name and affirmative Judge.me source verification, owned photo and MP4 MIME and bytes after source retirement and independent restore, complete current review facts and source identities in the owner business export and archive, no mail or marketing consent, no new verified purchases, duplicate-safe replay, selective undo and unchanged attributable import and undo activity after transfer. 'Review import authority, stale approvals and failed media never leak or partially apply' proves caller and origin refusals, exact reviewed apply, private email exclusion, atomic media refusal and revocation during media preparation leaving no import, review or media records. 'Review import source maps, owned data and erasure survive transfer without re-importing erased reviewers' proves portable source maps, private email, media removal on erasure, refusal of a pre-erasure review archive with the later journal, exact stored rating, title, body, name, date, source verification and reply for Okendo, Loox and mapped Stamped fields, and complete nonduplicated history across the 100-row window. tests/ui/review-import-journey.mjs — 'MIGRATE-007 emitted Worker journey', now loaded in push Verify's review-browser shard, asserts both dry runs, remapping, exclusions, reviewed apply, original dates and replies, imported and historical source-verification labels, Product, Review and AggregateRating JSON-LD in initial HTML, duplicate detection, selective undo, native-review preservation, inert hostile title, body, display name and reply, and complete-count history with older-import navigation, plus account and gallery tooltips at 1440 and 390. Network-edge media fakes prove only the documented export slice; no live provider adapter is claimed. Judge.me and Yotpo authorized API import adapters and native BigCommerce and WooCommerce review intake remain unimplemented or unproved; their duties remain MIGRATE-007 requirements and are not explicitly inherited in both receiving entries. Stamped mapped fields and the legacy Shopify subset are documented source-format boundaries, not complete native-export proof. CUSTOMER-002 retains request eligibility and REVIEWS-001 retains native collection, moderation and permitted requests. Connection-pinned media egress remains an unresolved runtime boundary under API-001 and the Base guarantees. Qualifying exact-SHA push Verify of the newly loaded review browser journey remains required before landing. All original MIGRATE-007 requirements remain.
EXPORT-001 Business CSVs and complete merchant exit target done src/stall/exports.ts; src/stall/tools.ts; src/stall/ui/business-exports.tsx; docs/BUSINESS-EXPORTS.md; tests/api/data.test.mjs; tests/api/commerce.test.mjs Owner-only downloads cover every current product/draft, unerased customer contact, order/line, payment/refund, shipment and reconciliation record in eight CSVs and whitelisted JSON, alongside the complete restore archive. Named EXPORT-001 HTTP tests independently read CSVs, reconcile exact totals, refuse unauthorized callers, exclude credentials/erased contacts and retain 200 products/1,000 orders without truncation. Formats, UTC/original currency, spreadsheet safety, resource bounds and absent record kinds are explicit; future record clauses inherit export before shipping (ct, 19 Oct).
ROLE-001 Staff and app least privilege target done tests/api/commerce.test.mjs — “functional staff grants isolate workflows, customer records and stale prepared authority” proves each of the six roles' invitation and permitted workflow, refusal of foreign customer, private, finance, bulk, export and direct API actions, owner-only single-role grant management, a zero refund ceiling and another-person approval by default, refund limits, downgrade and revoke taking effect on the next prepared-job request, and verified native-email customer isolation. “headless storefront scopes bind independent customers, one purchase and signed filtered event replay” proves owner-only app issuance, scoped app and customer isolation and app revocation during a prepared cart. tests/api/data.test.mjs — “staff, customer carts, events and workflow history transfer without restoring authority and erase attributable follow-up” proves transferred authority stays inactive. tests/ui/staff-journey.mjs proves owner permission forms, scoped workspaces and downgrade at 1440 and 390.
AGENT-001 Human approval of exact agent drafts target done src/stall/api.ts; src/stall/products.ts; src/stall/fulfilment.ts; src/stall/refunds.ts; tests/api/commerce.test.mjs; tests/api/data.test.mjs AGENT-001 in tests/api/commerce.test.mjs exercises all three agent-prepared drafts through HTTP, owner/admin exact-revision approvals, stale-revision refusal before effects, forbidden authority/export/restore/erasure, and revoked/expired reads and writes.
API-001 Documented headless API and signed events target partial docs/HEADLESS-API.md; tests/api/commerce.test.mjs — “headless storefront scopes bind independent customers, one purchase and signed filtered event replay” proves versioned catalog/cart/quote/checkout/customer/order doors, independent customer ownership, scopes/origin/refusal, one purchase under replay/reordered callbacks, HMAC/tamper rejection, stable replay and prepared-cart revocation; “free shipping promotions reserve real checkout budgets atomically and redeem only verified paid orders” proves actual signed filtered promotion events. tests/api/operations.test.mjs — “FLOW-001: current-source rules, native customer requests, cron, quiet pause and visible failed follow-up” proves real confirmed-return events. tests/api/data.test.mjs — “staff, customer carts, events and workflow history transfer without restoring authority and erase attributable follow-up” proves portable history without restored authority. Connection-level DNS rebinding protection requires native egress with address pinning/TLS hostname verification, unavailable in the current Workers fetch runtime; a Base/server networking primitive or provisioned egress service is required. RETURN-001 inherits additional lifecycle events as those states ship. Owner-only grants, independent native customer custody and explicit per-delivery consent await ct approval; no automatic delivery authority is inferred.
FLOW-001 Event and scheduled workflows with visible follow-up target partial tests/api/operations.test.mjs — “FLOW-001: current-source rules, native customer requests, cron, quiet pause and visible failed follow-up” proves low-stock/overdue/request/promotion/confirmed-return/scheduled rules, dry-run/activation, real cron, deduplication, quiet pending pause, assignment/due dates, visible failure, DST, bounded stock follow-up and explicit revision-bound shipment preparation with revoke/pause/risk/concurrency/loop fences. tests/api/data.test.mjs — “staff, customer carts, events and workflow history transfer without restoring authority and erase attributable follow-up” proves commercial draft/return history without restored authority and erasure stopping follow-up. tests/ui/staff-journey.mjs → tests/ui/workflow-journey.mjs proves editor/dry-run, task, pause, staff completion and exact shipment-draft review/recovery at 1440/390. Sales accounting and approved integration/budget effects remain unimplemented: ACCOUNT-001 needs missing NetSuite/Webgility sandbox authority, and arbitrary safe outbound egress needs the Base/server primitive named in API-001. Physical return stock movement remains RETURN-001/002/Pier work; current confirmation creates assigned stock follow-up only. Adopted owner/admin management, verified native requests/receipts, explicit human-only shipment preparation and fresh local activation after restore await ct approval. Wider actions remain required.
INTEGRATION-001 Owned connections and recoverable external work target done src/stall/connections.ts; src/stall/integration-work.ts; src/stall/stripe-recovery.ts; src/stall/pier-work.ts; src/stall/pier.ts; src/stall/ui/provider-boundaries.tsx; tests/api/operations.test.mjs; tests/api/pier-work.test.mjs; tests/api/data.test.mjs; tests/ui/integration-journey.mjs Current Stripe checkout/refund and Pier reservation/payment/dispatch work has durable commercial intent, original correlations, committed attempts and observed/uncertain outcomes. Stripe uncertain recovery only reads original references or bounded exact-match lookup; Pier first reads current state then replays the identical command under its atomic durable-receipt protocol, or observes a validated original complete dispatch. Revoked keys block replay, same-owner key rotation and restart/archive restore retain identities, and no replacement effect is created. Owner-managed encrypted local connections, fixed data-boundary previews, history and commercial-only CSV/JSON/archive are proven through named HTTP/browser journeys. Response observation is not payment/refund/delivery success. Future PAY-001/002, STOCK-001/003, SHIP-001/002/005/006/007, MAIL-001, MARKET-001, CHANNEL-001/002/003/004 and ACCOUNT-001 inherit these obligations before shipping.
SECURITY-001 Guarded native commerce doors target done src/stall/access.ts; src/stall/api.ts; src/stall/tools.ts; tests/api/commerce.test.mjs; tests/api/imports.test.mjs; tests/api/data.test.mjs
DATA-001 Validated archive and inactive receiving authority target done src/stall/tools.ts; src/stall/portability-policy.mjs; tests/api/data.test.mjs
ERASURE-001 Owner-directed contact erasure and backup fencing target done src/stall/erasure.ts; src/stall/portability-policy.mjs; tests/api/data.test.mjs
AUDIT-001 Durable attributable commercial action history target done src/stall/access.ts; src/stall/api.ts; src/stall/store.ts; tests/api/commerce.test.mjs; tests/api/data.test.mjs
OPS-001 Owned installation, recovery and explicit operating limits target done src/stall/operations.ts; src/stall/ops-providers.ts; src/stall/ui/operations.tsx; docs/OPERATIONS.md; tests/api/operations.test.mjs; tests/runtime.mjs; tests/clone-journey.mjs; tests/ui/journey.mjs Named public journeys cover emitted database health, real RER retained owner/data/settings and independent CLI archive restore, read-only provider outages, scheduler failure/recovery, outstanding refund/payment archive recovery without duplicate effects, and Settings at 1440/390. Actual bounds, growth/retention, storage observations, provider costs and outside requests are explicit; future capabilities inherit the obligation.
OPS-002 Run Stall on the owner's own computer or own server target partial src/site/run.json; scripts/installer/local.mjs; deploy.json; tests/clone-journey.mjs The one-line local start and own-account Cloudflare deploy exist; there is no own-server production path (rer dev and rer preview are rer-managed servers with a 12-hour idle stop), and the one-line start has no recorded fresh-machine acceptance.
BASE-001 Preserved Base guarantees with scoped replacements target done src/stall/imports/description.ts; src/stall/portability-policy.mjs; tests/api/imports.test.mjs; tests/api/data.test.mjs; tests/api/commerce.test.mjs; tests/ui/journey.mjs Current supported doors conform: named BASE-001 import/data/browser journeys exercise hostile plain text, unsupported input, owner-only saved connections, credential exclusion, inactive receiving authority, erased contacts, durable audit and native direct-door guards. Rich content/media/new-provider obligations remain conditions on future clauses, not claims those features exist (ct clarification, 19 Oct).
OPEN-001 Free and open source under the MIT license target done LICENSE; package.json; src/stall/ui/connect-forms.tsx; tests/api/commerce.test.mjs; tests/ui/journey.mjs MIT source/package, fresh public-clone install and named OPEN-001 HTTP journey: 200 published products, 10 signed-in staff and 1,000 paid/reserved USD orders with exact totals and no author fee/destination. Settings names Stripe/Pier and links processing, license and hosting pricing before saving; postage is explicitly separate. The no-gate and provider-disclosure requirements continue to apply when future capabilities/providers ship; no absent shipping-label connector is claimed.
AI-001 Operate order exceptions to shopper-approved closure push-further partial src/stall/payments.ts; src/stall/orders.ts; tests/api/commerce.test.mjs Paid/shortfall states and manual lost-response recovery exist; detection agent, grounded shopper replies, options and closure workflow are absent.
AI-002 Manage returns end to end push-further partial src/stall/refunds.ts; tests/api/commerce.test.mjs Revision-approved reconciled refunds are a foundation; policy reasoning, labels, return receipt, restock and agent follow-through are absent.
AI-003 Improve profitable conversion with measured experiments push-further missing No implementation found. Target journey not implemented.
AI-004 Recover failed integration work without invented success push-further partial src/stall/orders.ts; src/stall/stripe.ts; src/stall/pier.ts; tests/api/commerce.test.mjs Manual Stripe/Pier reconciliation preserves original identities; agent diagnosis, label/mail/channel/ledger recovery and policy execution are absent.
AI-005 Grounded merchandising and channel preparation push-further done tests/api/commerce.test.mjs — “AI-005: an agent proposes cited merchandising and a human publishes only selected exact changes” proves incomplete product and image facts, copy, alt text, structured attributes, SEO, grouping, source citations, unanswered questions, selective exact approval and channel validation; “AI-005: unsupported claims, stale sources and revoked authority cannot publish merchandising” proves stale product and collection refusal, fabricated inventory, certification and review refusal, and human authority. tests/api/data.test.mjs — “AI-005: product-only proposal provenance travels without agent or approval authority” proves export, archive, restore, credential exclusion and customer-source refusal. tests/ui/merch-proposals-journey.mjs — source and refusal, selective review, approved selection and stale refusal journeys prove the native screens at 1440 and 390. tests/ui/merch-seo-journey.mjs — native SEO journey proves emitted HTML metadata, unpublished exclusion and image tooltips at both widths.
BOUNDARY-001 Separate products with usable commerce connections target partial src/stall/pier.ts; src/stall/api.ts Pier is a separate product adapter today, but mandatory; Mango and alternative-provider handoffs are absent.
EXTEND-001 Subscriptions, POS, digital downloads and creator fulfillment partners target missing No implementation found. Target journey not implemented.
EXPAND-001 Multiple stores, regions and currencies target missing No implementation found. Target journey not implemented.
B2B-001 Business buying without absorbing wholesale operations target missing No implementation found. Target journey not implemented.