Problem solved
Commerce and campaign systems often disagree about availability. AtlasCommerce creates one tenant-scoped evidence trail from provider catalogue state to campaign eligibility.
Beta · entitlement required
Keep campaigns aligned with what the store can actually sell.
AtlasCommerce connects permissioned commerce catalogues to the AtlasLoopOS operating loop. It normalizes product and inventory evidence, raises governed low-stock signals, and prevents new product-linked campaign execution when availability is unsafe.
The stable internal key and API prefix remain atlasinventory. The authenticated application route remains /products/atlasinventory for compatibility.
Intended users
Commerce operators, growth teams, agencies, and campaign reviewers who need inventory-aware execution without giving an AI permission to change campaigns autonomously.
Current Beta boundary
Three catalogue providers are executable. The first fully hardened low-stock event and campaign-protection path is WooCommerce.
Major workflows
One observable path from store authorization to campaign safety.
01
Connect a store
Workspace owners or admins authorize a supported provider. WooCommerce read credentials are validated before encrypted service-only storage.
02
Synchronize the catalogue
An initial full sync and later manual or scheduled reconciliation normalize product, price, stock, categories, images, variants, availability, timestamps, and sync evidence.
03
Monitor inventory
For the hardened WooCommerce path, known stock at or below the configured threshold opens one inventory event and creates or refreshes a tenant-scoped AtlasSignals low-stock record.
04
Protect campaigns
AtlasCampaigns receives explicit eligibility and buyability state. New product-linked execution fails closed while inventory is unsafe, without rewriting approvals or published history.
Current Beta features
- Executable WooCommerce, Shopify, and Magento / Adobe Commerce catalogue providers for eligible workspaces
- WooCommerce connectivity validation, encrypted read credentials, initial full sync, manual sync, and six-hour reconciliation
- Canonical product identity by connected store plus provider product ID
- Product, price, availability, inventory, categories, images, variants, and synchronization history
- WooCommerce low-stock threshold policy with open/observed/resolved inventory-event evidence
- Canonical AtlasSignals low-stock create/update/resolve lineage
- AtlasCampaigns eligibility and buyability projection with database and X publishing guards
- Tenant-scoped audit evidence for connection, credentials, sync, threshold, event, eligibility, and buyability transitions
- Intentional loading, empty, error, correction, refresh, and retry states in the authenticated workflow
Honest Beta limitations
- AtlasCommerce is a Beta product, not general availability or a production service-level commitment.
- The first hardened stock-to-signal-to-campaign workflow is WooCommerce. Shopify and Magento provider parity for this exact workflow remains open.
- Live PostgreSQL migration execution, real merchant-store transition/recovery, large-catalogue load, concurrency, and outage recovery remain production gates.
- Inventory policy is product-level. Location safety stock, reservations, bundle/component availability, and provider-specific salability are not complete.
- No autonomous campaign approval, copy change, budget change, publishing, replenishment order, or demand forecast occurs.
- Public access requires an eligible organization entitlement and deployment configuration.
Known deferred items
Provider parity for low-stock inventory events and campaign buyability beyond WooCommerce
Advanced feeds, complete channel/location mastering, orders, customers, fulfillment, checkout, and remote write-back
Forecasting, reorder recommendations, safety-stock optimization, reservations, bundles, and warehouse allocation
Additional campaign publishers and provider-side cancellation of an already-processing external call
Formal accessibility, browser E2E, load, security, backup/restore, retention, incident, and operational runbook evidence
Pricing and access
ADATLAS-074 creates no separate plan, subscription, price, checkout, licence, usage, or billing object. Beta access is enabled through existing organization entitlements; no public standalone price is represented as available.
Governance model
Owners and admins connect stores, synchronize manually, and change the WooCommerce threshold. Entitled members can inspect non-secret catalogue, workflow, event, signal, campaign, and audit evidence.
Set up the first inventory-aware workflow.
Review required WooCommerce permissions, connect the store, run the first catalogue sync, configure the low-stock threshold, and verify AtlasSignals, AtlasCampaigns, and audit evidence.