Merchant perspective
Start with a brand brief and product data, review design, pricing, shipping and policies, then decide when to publish.
antelopeintl / PRODUCT SPECIFICATION
Explore the components and responsibilities of an AI-assisted commerce workspace, from brand and products to transactions and daily operations.
01 / POSITIONING
antelopeintl aims to bring brand-store creation and daily operations into one clear workspace. Merchants set direction and review products and policies; AI prepares editable work while merchants retain responsibility for important business decisions.
Start with a brand brief and product data, review design, pricing, shipping and policies, then decide when to publish.
See products, total prices and seller identity in a familiar language, with traceable orders and after-sales support.
Agents organize and suggest; payment collection, refunds, price changes and publication require explicit authorization.
Subscription fees and store sales proceeds are recorded separately; merchants collect payments through their own PSP accounts.
| Topic | Architecture outline | Points to consider |
|---|---|---|
| Business relationship | Software services for merchants | Platform collection and split payments require separate money-flow and responsibility design |
| Products & fulfillment | Start with ordinary physical goods and a single warehouse | Assess digital goods, multiple warehouses and B2B purchasing separately |
| Market availability | Verify entity, PSP and initial jurisdictions first | A translated interface does not mean a market is open for transactions |
| Store generation | Structured pages and reviewable versions | No arbitrary server-side code execution |
| Transaction core | Deterministic business services separate from the public site | Decide service splits as scale requires |
| Deployment | Public site may use static publishing or Workers | The public site and transaction services have separate responsibilities |
02 / DOMAIN & ACCESS
The workspace is the basic unit for contracts, staff and data isolation; a store holds its brand and domain; a market defines language, currency, tax and shipping strategy. Browser-supplied IDs cannot replace server-side authorization.
| Object | Purpose | Boundary |
|---|---|---|
| Workspace | Manages contracts, plans, people and data ownership | Every business record belongs to an authenticated tenant |
| Stores | Manages brand, domain, product display and support policy | Existing orders retain seller and policy snapshots from purchase |
| Market | Defines available languages, currencies and regional rules | Activation requires explicit review, without changing transaction rules by IP alone |
| Channel | Assigns products and prices to sales entry points | Channel partitioning is not security isolation |
| Legal seller | Records operator, address and contacts | The platform entity does not automatically become the product seller |
| Role | Allowed scope | Additional controls |
|---|---|---|
| Owner | Contracts, members, billing and store configuration | Payment accounts and ownership changes need extra verification |
| Administrator | Manage products and orders for assigned stores | Refund execution is not granted by default |
| Editor | Product drafts, content, themes and SEO | Separate permission for price changes and publication |
| Support | Query permitted orders and prepare after-sales suggestions | Cannot directly complete refunds |
| Finance approver | Reconcile and review refunds individually | Approval must bind order, amount and reason |
| Agent identity | Read-only queries and specified draft tools | Must not inherit owner permissions |
03 / MODULE CATALOG
This catalog organizes 31 areas of the product architecture, from brand setup to after-sales operations, to show how the workflows fit together.
| Module | Goal | Category |
|---|---|---|
| 01 · Workspace & store | Brand, members, markets, domains and quotas | Core workflow |
| 02 · Identity & access | Sign-in, MFA, roles and resource scope | Core workflow |
| 03 · Merchant onboarding | Seller details, PSP connection and launch checks | Core workflow |
| 04 · AI store building | Page components, theme parameters and draft versions | Core workflow |
| 05 · Domains & publishing | Ownership verification, TLS, preview and rollback | Core workflow |
| 06 · Task orchestration | Planning, queues, checkpoints and recovery | Core workflow |
| 07 · Agent governance | Approvals, budgets, tool permissions and audit | Core workflow |
| 08 · Products & SKUs | Variants, categories, images, languages and import | Core workflow |
| 09 · Inventory & reservations | Inventory ledger, atomic reservations and release | Core workflow |
| 10 · Prices & promotions | Market price lists, promotion conditions and allocation | Core workflow |
| 11 · Cart & orders | Server-side quotes, checkout and order snapshots | Core workflow |
| 12 · Merchant payments | Payment adapters, callbacks and reconciliation | Core workflow |
| 13 · Risk review | Rule signals, human queue and records | Core workflow |
| 14 · Returns & refunds | After-sales requests, individual approval and refund status | Core workflow |
| 15 · Payment disputes | Deadlines, evidence and separate chargeback state | Core workflow |
| 16 · Shipping & fulfillment | Shipping fees, tracking and partial shipments | Core workflow |
| 17 · Tax documents | Tax zones, categories, snapshots and receipts | Core workflow |
| 18 · Customer accounts | Order lookup, addresses and preferences | Core workflow |
| 19 · AI support | Knowledge sources, identity checks and human handoff | Core workflow |
| 20 · Content & SEO | Crawlable pages, metadata and sitemaps | Core workflow |
| 21 · Localization | Languages, time zones, translation and fallback | Core workflow |
| 22 · Multi-currency | Display, payment and settlement currencies and rounding | Core workflow |
| 23 · Agreements & policies | Platform and store texts, versions and review | Core workflow |
| 24 · Consent & privacy | Preferences, data requests and retention rules | Core workflow |
| 25 · Subscription entitlements | Monthly/yearly periods, seats and points ledger | Core workflow |
| 26 · Business analytics | Orders, refunds and net sales definitions | Core workflow |
| 27 · Open API | Versioned API, webhooks and retries | Core workflow |
| 28 · Transaction notices | Order and after-sales messages and delivery status | Core workflow |
| 29 · Security & operations | Monitoring, backups, incident response and recovery | Core workflow |
| 30 · Migration & export | Verifiable imports and data exit | Core workflow |
| 31 · Business model extensions | Assess B2B, digital products and new channels later | Extensions |
04 / STORE JOURNEY
Starting with an idea, merchants progressively complete the information a transactional store needs. Each step should produce reviewable work, rather than treating one generated result as a completed launch.
| Step | Merchant confirms | System prepares | Gate to next step |
|---|---|---|---|
| 01 Business direction | Brand, products and target customers | Structured requirements draft | Check product eligibility |
| 02 Workspace | Entity, members and subscription | Tenant and access configuration | Account and fees confirmed |
| 03 Product information | Images, variants, prices and inventory | Product drafts and import report | Required fields validated |
| 04 Page building | Layout, copy and visual direction | Editable store preview | Mobile and content review |
| 05 Commerce setup | Payment account, taxes, shipping and policies | Checkout rules and market configuration | Key information is true and complete |
| 06 Test order | Payment, fulfillment, refund and support drills | Acceptance records and callback audit | Failure paths recoverable |
| 07 Publication | Approved version and domain | Release record and policy version | Reviewer and version aligned |
| 08 Daily operations | Order processing and improvement suggestions | Workspace and action history | Key actions remain access-controlled |
05 / AGENT SYSTEM
Agents may understand goals, prepare drafts and suggest actions. A separate authorization layer decides whether they may read data, call tools or perform external actions.
| Agent | Prepared work | Default restriction |
|---|---|---|
| Storefront | Page structure and theme suggestions | Cannot change payment code or publish autonomously |
| Product | Draft attributes, categories, descriptions and translations | Cannot invent stock or product certifications |
| Content | Page summaries, SEO and internal link suggestions | Review before publication |
| Support | Replies and after-sales suggestions grounded in approved policies | Authorized personnel must confirm refunds |
| Operations | Suggestions for inventory and order exceptions | Cannot independently declare fraud or close a case |
created → planned → validated → awaiting_approval → queued → running → succeeded
Branches: failed / cancelled / needs_attention06 / COMMERCE CORE
Manage product concepts separately from sellable variants. Each SKU records variant, price, stock, media, language and eligible markets; keep an immutable order snapshot at sale.
Available stock = On hand − Reserved − Allocated − Safety stock
Reservation states: held → committed / released / expiredReserve inventory atomically before checkout and allocate it to the order after payment confirmation. Expiry and failure releases must be idempotent. Recheck stock for late payment results, then route exceptions to staff.
Product validation → Market pricing → Discounts & allocation → Shipping → Tax → Rounding
→ Quote snapshot → Customer confirmation → Order snapshotCalculate partial refunds from original line items and already-refunded portions, not current prices. Validate taxes and shipping against actual market configuration.
07 / TRANSACTION STATES
Orders, payment attempts, shipments, refunds and disputes each have their own states. The interface summarizes them without collapsing parallel facts into one status.
| Object | Example states | Trusted evidence |
|---|---|---|
| Orders | Draft → Placed → Confirmed → Completed | Price, policy and inventory snapshots |
| Payment attempt | Action needed → Processing → Authorized → Captured | PSP response and verified callback |
| Fulfillment | Pending → Packing → Partially shipped → Completed | Package and tracking records |
| Refund | Requested → Approved → Processing → Succeeded / Failed | Individual approval and PSP result |
| Dispute | Received → Evidence gathered → Submitted → Outcome | Dispute event and deadline |
08 / RISK & FULFILLMENT
Risk signals support merchant judgment, not replace it. Track return authorization, logistics, payment refunds and dispute evidence separately.
| Item | Suggested handling | Retain |
|---|---|---|
| Risk signal | Show source and reason to authorized staff | Review outcome and operator |
| Return request | Check order and policy version | Request, photos and timestamps |
| Partial refund | Check remaining refundable amount and approve each refund | Original payment and refund amounts |
| Chargeback dispute | Prepare evidence before the deadline | Submission receipt and later outcome |
| Partial shipment | Track status by package | Tracking details and customer notices |
09 / CUSTOMER CARE
Support answers should use published products, policies and authorized order data. Direct customers to a secure order flow for identity verification and hand out-of-scope cases to a person with context.
FAQ responses, order lookup leads and after-sales summaries.
Refunds, price changes, policy exceptions and formal customer commitments.
Pause automated replies when a person takes over, preserving drafts and sources.
Keep knowledge retrieval and customer data scoped by store and permission.
10 / MARKETS & I18N
Language, displayed price, payment currency and settlement currency are different. Verify products, payments, tax, shipping and consumer policies for each market.
| Element | Display & rules | Transaction constraint |
|---|---|---|
| Language | Merchants review translations and can fall back | Product facts stay consistent |
| Currency | Label display, payment and settlement separately | Lock exchange rate and rounding in quote |
| Tax & shipping | Calculate by address and product tax class | Show confirmable total before checkout |
| Payment methods | Show according to PSP and merchant-account capabilities | Translation alone cannot imply availability |
Retain original-currency amounts and exchange-rate basis for orders and refunds; label conversion methods in cross-currency reports.
11 / DISCOVERABILITY
Product and content pages should be crawlable and identify language versions while keeping draft previews out of search indexes.
12 / LEGAL & PRIVACY
Manage platform service contracts separately from merchant consumer policies and retain them by entity, language, market and effective version.
| Scope | Versioned material | Handling principle |
|---|---|---|
| Platform subscription | Service, billing, privacy, data processing and AI use | Clear signed version, rights and duties |
| Store transactions | Purchases, shipping, returns, payments and customer privacy | Retain applicable text at sale |
| Consent records | Agreement version, language, time and action evidence | Reproduce what was shown at the time |
| Privacy requests | Access, correction, deletion and export | Respect lawful retention and audit needs |
13 / ARCHITECTURE
Deploy the presentation layer separately from transaction services such as money and orders. The public site and static assets may use static hosting or Workers; the backend needs an environment suited to database transactions, payment callbacks and queues.
| Layer | Responsibility | Delivery concern |
|---|---|---|
| Public website | Brand, resources, static content and previews | Cacheable, reversible and SEO friendly |
| Merchant admin | Access, products, orders and approvals | Authentication and resource scope |
| Commerce services | Quotes, inventory, payments and refunds | Consistency and idempotency |
| Agent services | Task orchestration, tool gateway and budgets | Isolation and auditability |
| Storage integration | Relational data, objects and event queues | Backups, keys and monitoring |
Check Cloudflare Workers' Node compatibility feature by feature; deploying a static website there does not mean the entire commerce backend can run unchanged.
14 / DATA & API
Data models and APIs should expose tenant ownership, business versions and external facts. Mutating interfaces need scoped authorization, stable idempotency keys and versioned responses.
| Entity | Key ownership | Key records |
|---|---|---|
| Tenant / Store | Contract and brand | Members, markets and policy versions |
| Product / Variant | Products and variants | Media, prices and inventory ledger |
| Quote / Order | Purchase intent | Amount, tax and policy snapshot |
| Payment / Refund | External payment account | Attempts, callbacks and reconciliation references |
| AgentTask / Approval | Initiator and resources | Budget, approvals, steps and outcomes |
POST /v1/stores/:storeId/orders
Idempotency-Key: <stable-business-key>
If-Match: <resource-version>
Server validation: session → tenant scope → resource version → parameters → side effects15 / SECURITY & OPERATIONS
Orders, payments and async tasks need a shared trace ID, with recoverability and security included in delivery checks.
| Area | Design requirement |
|---|---|
| Identity | Short sessions, admin MFA, least privilege and reauthentication for sensitive actions |
| Data | Encryption in transit and at rest, key rotation and test/production separation |
| Web | Output encoding, CSP, upload limits and signed downloads |
| Delivery | Dependency review, migration checks and reversible releases |
| Observability | Correlate orders, payments, callbacks and agent tasks by trace ID |
| Backups | Regular recovery drills; reconcile externally completed payments, refunds and shipments |
Report net sales, taxes, shipping, refunds and chargebacks separately; label chart currency, time zone and period.
16 / SUBSCRIPTIONS
The amounts match the plan references on the pricing page. The annual reference total is 80% of the monthly amount multiplied by 12; the applicable agreement governs taxes and billing.
| Item | Starter | Growth | Enterprise |
|---|---|---|---|
| Monthly | $30 / month | $90 / month | $240 / month |
| Yearly total | $288 / year | $864 / year | $2,304 / year |
| Yearly monthly equivalent | $24 / month | $72 / month | $192 / month |
| Stores | 1 | 3 | 10 |
| Seats | 1 | 5 | 20 |
| SKU limit | 100 | 2,500 | 20,000 |
| AI points / month | 1,000 | 5,000 | 20,000 |
17 / PRODUCT INFORMATION
Explore store design, daily operations, plan capacity and relevant terms across the site. Each interactive example explains the scope of its data and actions.
| Page | What you can explore | What to check |
|---|---|---|
| Homepage | The main steps from store concept to operations | Open the product pages for specific workflows |
| Workspace preview | How products, stock and orders relate in the interface | The displayed records are sample data |
| Product pages | Store building, management, payments and analytics | Check each page for the scope of its interactions |
| Pricing | Plan periods, amounts and capacity | Selecting a plan on the page does not charge or subscribe you |
| Legal & contact | Platform terms, store policies and inquiry topics | Review the applicable agreement for your circumstances |
18 / EVALUATION
When evaluating a commerce workspace, consider merchant identity, transaction flow, permissions and market needs alongside the relevant plan and terms.
Identify the store operator, team responsibilities, store count and access permissions.
Review catalog data, inventory states, order handling and after-sales responsibility.
Separate SaaS fees from store sales proceeds and check payment-provider and billing terms.
Review language, currency, tax, shipping and data requirements for each target market.
| Area | Point to review |
|---|---|
| Accounts & access | Which actions and data does each team member need? |
| Inventory & orders | How do product, inventory and order states relate? |
| Payments & refunds | Who collects store payments and handles refunds or disputes? |
| Data & markets | How are policies, languages and data flows managed across markets? |
19 / PRIMARY SOURCES
These links lead to technical references and public standards from their issuing organizations for further reading.