antelopeintl
Product resources / Product design & architecture
Contents · Choose a section

antelopeintl / PRODUCT SPECIFICATION

Turn a business idea
into a sustainable commerce business.

Explore the components and responsibilities of an AI-assisted commerce workspace, from brand and products to transactions and daily operations.

Brand: antelopeintlSubscription: monthly / yearly

01 / POSITIONING

Positioning & design decisions

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.

Merchant perspective

Start with a brand brief and product data, review design, pricing, shipping and policies, then decide when to publish.

Customer perspective

See products, total prices and seller identity in a familiar language, with traceable orders and after-sales support.

Operational control

Agents organize and suggest; payment collection, refunds, price changes and publication require explicit authorization.

Platform role

Subscription fees and store sales proceeds are recorded separately; merchants collect payments through their own PSP accounts.

Business roles & scope

TopicArchitecture outlinePoints to consider
Business relationshipSoftware services for merchantsPlatform collection and split payments require separate money-flow and responsibility design
Products & fulfillmentStart with ordinary physical goods and a single warehouseAssess digital goods, multiple warehouses and B2B purchasing separately
Market availabilityVerify entity, PSP and initial jurisdictions firstA translated interface does not mean a market is open for transactions
Store generationStructured pages and reviewable versionsNo arbitrary server-side code execution
Transaction coreDeterministic business services separate from the public siteDecide service splits as scale requires
DeploymentPublic site may use static publishing or WorkersThe public site and transaction services have separate responsibilities

02 / DOMAIN & ACCESS

Domains, isolation & 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.

ObjectPurposeBoundary
WorkspaceManages contracts, plans, people and data ownershipEvery business record belongs to an authenticated tenant
StoresManages brand, domain, product display and support policyExisting orders retain seller and policy snapshots from purchase
MarketDefines available languages, currencies and regional rulesActivation requires explicit review, without changing transaction rules by IP alone
ChannelAssigns products and prices to sales entry pointsChannel partitioning is not security isolation
Legal sellerRecords operator, address and contactsThe platform entity does not automatically become the product seller

Isolation across the data chain

  • Scope database queries, cache reads, file downloads and search indexes to a trusted tenant context.
  • Reauthorize asynchronous jobs and verify callback signatures and payment-account mappings.
  • Limit support access by time and purpose and keep auditable records.

Roles & permissions

RoleAllowed scopeAdditional controls
OwnerContracts, members, billing and store configurationPayment accounts and ownership changes need extra verification
AdministratorManage products and orders for assigned storesRefund execution is not granted by default
EditorProduct drafts, content, themes and SEOSeparate permission for price changes and publication
SupportQuery permitted orders and prepare after-sales suggestionsCannot directly complete refunds
Finance approverReconcile and review refunds individuallyApproval must bind order, amount and reason
Agent identityRead-only queries and specified draft toolsMust not inherit owner permissions

03 / MODULE CATALOG

Feature 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.

ModuleGoalCategory
01 · Workspace & storeBrand, members, markets, domains and quotasCore workflow
02 · Identity & accessSign-in, MFA, roles and resource scopeCore workflow
03 · Merchant onboardingSeller details, PSP connection and launch checksCore workflow
04 · AI store buildingPage components, theme parameters and draft versionsCore workflow
05 · Domains & publishingOwnership verification, TLS, preview and rollbackCore workflow
06 · Task orchestrationPlanning, queues, checkpoints and recoveryCore workflow
07 · Agent governanceApprovals, budgets, tool permissions and auditCore workflow
08 · Products & SKUsVariants, categories, images, languages and importCore workflow
09 · Inventory & reservationsInventory ledger, atomic reservations and releaseCore workflow
10 · Prices & promotionsMarket price lists, promotion conditions and allocationCore workflow
11 · Cart & ordersServer-side quotes, checkout and order snapshotsCore workflow
12 · Merchant paymentsPayment adapters, callbacks and reconciliationCore workflow
13 · Risk reviewRule signals, human queue and recordsCore workflow
14 · Returns & refundsAfter-sales requests, individual approval and refund statusCore workflow
15 · Payment disputesDeadlines, evidence and separate chargeback stateCore workflow
16 · Shipping & fulfillmentShipping fees, tracking and partial shipmentsCore workflow
17 · Tax documentsTax zones, categories, snapshots and receiptsCore workflow
18 · Customer accountsOrder lookup, addresses and preferencesCore workflow
19 · AI supportKnowledge sources, identity checks and human handoffCore workflow
20 · Content & SEOCrawlable pages, metadata and sitemapsCore workflow
21 · LocalizationLanguages, time zones, translation and fallbackCore workflow
22 · Multi-currencyDisplay, payment and settlement currencies and roundingCore workflow
23 · Agreements & policiesPlatform and store texts, versions and reviewCore workflow
24 · Consent & privacyPreferences, data requests and retention rulesCore workflow
25 · Subscription entitlementsMonthly/yearly periods, seats and points ledgerCore workflow
26 · Business analyticsOrders, refunds and net sales definitionsCore workflow
27 · Open APIVersioned API, webhooks and retriesCore workflow
28 · Transaction noticesOrder and after-sales messages and delivery statusCore workflow
29 · Security & operationsMonitoring, backups, incident response and recoveryCore workflow
30 · Migration & exportVerifiable imports and data exitCore workflow
31 · Business model extensionsAssess B2B, digital products and new channels laterExtensions

04 / STORE JOURNEY

From idea to store launch

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.

StepMerchant confirmsSystem preparesGate to next step
01 Business directionBrand, products and target customersStructured requirements draftCheck product eligibility
02 WorkspaceEntity, members and subscriptionTenant and access configurationAccount and fees confirmed
03 Product informationImages, variants, prices and inventoryProduct drafts and import reportRequired fields validated
04 Page buildingLayout, copy and visual directionEditable store previewMobile and content review
05 Commerce setupPayment account, taxes, shipping and policiesCheckout rules and market configurationKey information is true and complete
06 Test orderPayment, fulfillment, refund and support drillsAcceptance records and callback auditFailure paths recoverable
07 PublicationApproved version and domainRelease record and policy versionReviewer and version aligned
08 Daily operationsOrder processing and improvement suggestionsWorkspace and action historyKey actions remain access-controlled

05 / AGENT SYSTEM

Agent orchestration & governance

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.

AgentPrepared workDefault restriction
StorefrontPage structure and theme suggestionsCannot change payment code or publish autonomously
ProductDraft attributes, categories, descriptions and translationsCannot invent stock or product certifications
ContentPage summaries, SEO and internal link suggestionsReview before publication
SupportReplies and after-sales suggestions grounded in approved policiesAuthorized personnel must confirm refunds
OperationsSuggestions for inventory and order exceptionsCannot independently declare fraud or close a case

Task execution & approvals

created → planned → validated → awaiting_approval → queued → running → succeeded
Branches: failed / cancelled / needs_attention
  • Execution plans identify resources, permissions, budgets and external effects.
  • High-impact approvals bind a specific action, target, parameters and validity period; changed parameters require new approval.
  • Server-side status reflects actual tool results, with failed tasks resuming from checkpoints.
  • Page drafts can roll back; completed charges, messages and shipping actions need compensating processes.

06 / COMMERCE CORE

Products, inventory & quotes

Products & inventory

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 / expired

Reserve 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.

Server-side quote sequence

Product validation → Market pricing → Discounts & allocation → Shipping → Tax → Rounding
→ Quote snapshot → Customer confirmation → Order snapshot

Calculate partial refunds from original line items and already-refunded portions, not current prices. Validate taxes and shipping against actual market configuration.

07 / TRANSACTION STATES

Transaction & payment states

Orders, payment attempts, shipments, refunds and disputes each have their own states. The interface summarizes them without collapsing parallel facts into one status.

ObjectExample statesTrusted evidence
OrdersDraft → Placed → Confirmed → CompletedPrice, policy and inventory snapshots
Payment attemptAction needed → Processing → Authorized → CapturedPSP response and verified callback
FulfillmentPending → Packing → Partially shipped → CompletedPackage and tracking records
RefundRequested → Approved → Processing → Succeeded / FailedIndividual approval and PSP result
DisputeReceived → Evidence gathered → Submitted → OutcomeDispute event and deadline

Callbacks & idempotency

  • Retries use a stable business key; reject the same key with a different amount or target.
  • Verify and deduplicate webhook signatures and tolerate out-of-order delivery; a browser redirect is not proof of payment.
  • Verify the store's payment-account mapping server-side, rather than changing merchants based on external metadata.

08 / RISK & FULFILLMENT

Risk, refunds & fulfillment

Risk signals support merchant judgment, not replace it. Track return authorization, logistics, payment refunds and dispute evidence separately.

ItemSuggested handlingRetain
Risk signalShow source and reason to authorized staffReview outcome and operator
Return requestCheck order and policy versionRequest, photos and timestamps
Partial refundCheck remaining refundable amount and approve each refundOriginal payment and refund amounts
Chargeback disputePrepare evidence before the deadlineSubmission receipt and later outcome
Partial shipmentTrack status by packageTracking details and customer notices

09 / CUSTOMER CARE

Agent support & customers

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.

Can prepare automatically

FAQ responses, order lookup leads and after-sales summaries.

Requires merchant confirmation

Refunds, price changes, policy exceptions and formal customer commitments.

Handoff record

Pause automated replies when a person takes over, preserving drafts and sources.

Customer scope

Keep knowledge retrieval and customer data scoped by store and permission.

10 / MARKETS & I18N

Multi-currency & localization

Language, displayed price, payment currency and settlement currency are different. Verify products, payments, tax, shipping and consumer policies for each market.

ElementDisplay & rulesTransaction constraint
LanguageMerchants review translations and can fall backProduct facts stay consistent
CurrencyLabel display, payment and settlement separatelyLock exchange rate and rounding in quote
Tax & shippingCalculate by address and product tax classShow confirmable total before checkout
Payment methodsShow according to PSP and merchant-account capabilitiesTranslation 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

SEO & content publishing

Product and content pages should be crawlable and identify language versions while keeping draft previews out of search indexes.

  • Published pages output titles, descriptions, canonical URLs, structured product data and sitemaps.
  • Declare relationships between language versions and maintain redirects when slugs change.
  • Restrict private previews and set noindex; do not rely only on robots crawl rules.
  • AI may draft and suggest improvements, while merchants verify product facts and publication.

13 / ARCHITECTURE

Technical & deployment 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.

LayerResponsibilityDelivery concern
Public websiteBrand, resources, static content and previewsCacheable, reversible and SEO friendly
Merchant adminAccess, products, orders and approvalsAuthentication and resource scope
Commerce servicesQuotes, inventory, payments and refundsConsistency and idempotency
Agent servicesTask orchestration, tool gateway and budgetsIsolation and auditability
Storage integrationRelational data, objects and event queuesBackups, 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 model & 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.

EntityKey ownershipKey records
Tenant / StoreContract and brandMembers, markets and policy versions
Product / VariantProducts and variantsMedia, prices and inventory ledger
Quote / OrderPurchase intentAmount, tax and policy snapshot
Payment / RefundExternal payment accountAttempts, callbacks and reconciliation references
AgentTask / ApprovalInitiator and resourcesBudget, approvals, steps and outcomes

API example

POST /v1/stores/:storeId/orders
Idempotency-Key: <stable-business-key>
If-Match: <resource-version>

Server validation: session → tenant scope → resource version → parameters → side effects

15 / SECURITY & OPERATIONS

Consistency, security & operations

Orders, payments and async tasks need a shared trace ID, with recoverability and security included in delivery checks.

AreaDesign requirement
IdentityShort sessions, admin MFA, least privilege and reauthentication for sensitive actions
DataEncryption in transit and at rest, key rotation and test/production separation
WebOutput encoding, CSP, upload limits and signed downloads
DeliveryDependency review, migration checks and reversible releases
ObservabilityCorrelate orders, payments, callbacks and agent tasks by trace ID
BackupsRegular 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

Subscription pricing & billing

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.

ItemStarterGrowthEnterprise
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
Stores1310
Seats1520
SKU limit1002,50020,000
AI points / month1,0005,00020,000

Allowances & periods

  • Store, seat and SKU counts describe plan capacity.
  • Display the actual yearly charge without presenting its monthly equivalent as a monthly debit.
  • Replenish AI points monthly; pause new tasks when budgets are insufficient without disrupting existing orders.
  • Show effective time, price difference and service end date for cancellation, upgrades, downgrades and refunds.

17 / PRODUCT INFORMATION

Product previews & 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.

PageWhat you can exploreWhat to check
HomepageThe main steps from store concept to operationsOpen the product pages for specific workflows
Workspace previewHow products, stock and orders relate in the interfaceThe displayed records are sample data
Product pagesStore building, management, payments and analyticsCheck each page for the scope of its interactions
PricingPlan periods, amounts and capacitySelecting a plan on the page does not charge or subscribe you
Legal & contactPlatform terms, store policies and inquiry topicsReview the applicable agreement for your circumstances

18 / EVALUATION

What to review

When evaluating a commerce workspace, consider merchant identity, transaction flow, permissions and market needs alongside the relevant plan and terms.

Merchant & team

Identify the store operator, team responsibilities, store count and access permissions.

Products & orders

Review catalog data, inventory states, order handling and after-sales responsibility.

Payments & fees

Separate SaaS fees from store sales proceeds and check payment-provider and billing terms.

Markets & growth

Review language, currency, tax, shipping and data requirements for each target market.

Questions to consider

AreaPoint to review
Accounts & accessWhich actions and data does each team member need?
Inventory & ordersHow do product, inventory and order states relate?
Payments & refundsWho collects store payments and handles refunds or disputes?
Data & marketsHow are policies, languages and data flows managed across markets?

19 / PRIMARY SOURCES

Sources & references

These links lead to technical references and public standards from their issuing organizations for further reading.

  1. 01
    Cloudflare · Workers Static Assets Static site deployment · developers.cloudflare.com
  2. 02
    Cloudflare · Node.js compatibility Runtime compatibility · developers.cloudflare.com
  3. 03
    Vendure · Core Commerce framework and licensing · vendure.io
  4. 04
    Vendure · Channels Channel design · github.com
  5. 05
    OWASP · AI Agent Security Agent authorization · cheatsheetseries.owasp.org
  6. 06
    OWASP · Multi Tenant Security Multi-tenant isolation · cheatsheetseries.owasp.org
  7. 07
    Stripe · Webhooks Callback verification and event handling · docs.stripe.com
  8. 08
    Stripe · Supported currencies Currencies and minor units · docs.stripe.com
  9. 09
    Stripe · PaymentIntent lifecycle Payment states · docs.stripe.com
  10. 10
    Stripe · Refunds Refund flow · docs.stripe.com
  11. 11
    Stripe · Security guide Payment integration boundaries · docs.stripe.com
  12. 12
    Google Search Central · Localized versions Localized pages · developers.google.com
  13. 13
    Google Search Central · Canonical URLs Canonical URLs · developers.google.com
  14. 14
    Google Search Central · Product data Product structured data · developers.google.com
  15. 15
    Google Search Central · Noindex Excluding previews from indexing · developers.google.com
  16. 16
    Google Search Central · Sitemap Sitemaps · developers.google.com
  17. 17
    W3C WAI · WCAG 2.2 Accessibility standard · www.w3.org
  18. 18
    EUR-Lex · GDPR EU data protection text · eur-lex.europa.eu
  19. 19
    EUR-Lex · Directive 2023/2673 Online withdrawal rule text · eur-lex.europa.eu
  20. 20
    European Commission · ODR Platform closure notice · consumer-redress.ec.europa.eu
  21. 21
    IETF · RFC 9110 HTTP conditional requests · www.rfc-editor.org
  22. 22
    Stripe · Subscription webhooks Subscription events · docs.stripe.com
antelopeintl · Product & system design