commerce platforms.md
Commerce Platforms
Use this page to choose the right integration shape for a merchant platform.
Platform Strategy
Hexagon is built for merchants selling through AI shopping channels. The exact integration depends on where the merchant's product truth lives.
Common product truth sources include:
- Shopify
- WooCommerce
- Magento or Adobe Commerce
- VTEX
- BigCommerce
- custom ecommerce backends
- product information management systems
- ERP-backed catalogs
- flat product feeds
- marketplace catalogs
Shopify
Shopify merchants usually have clear catalog, price, variant, image, and inventory APIs. When current Hexagon docs or onboarding materials provide a Shopify path, use that path rather than inventing a custom feed.
For agent-written code, keep credentials server-side and avoid embedding Shopify tokens in frontend code.
WooCommerce
WooCommerce stores vary widely because plugin stacks differ. Confirm:
- product API availability
- variant representation
- authentication method
- inventory source
- checkout flow
- whether prices are modified by plugins, discounts, tax rules, or memberships
If there is no official Hexagon WooCommerce SDK in current docs, treat it as custom rollout.
Magento / Adobe Commerce
Magento implementations often have complex catalogs, configurable products, customer-group pricing, and extension-specific checkout behavior. Confirm:
- catalog API access
- price scope
- customer-group constraints
- inventory source
- index freshness
- store-view and locale behavior
Large Magento merchants usually belong in an enterprise or custom rollout conversation.
VTEX
VTEX stores often have strong catalog and marketplace patterns but custom checkout and regional requirements. Confirm:
- catalog source
- seller and marketplace model
- fulfillment and SLA rules
- payment and order routing constraints
- region-specific compliance requirements
BigCommerce
For BigCommerce, confirm product variants, modifiers, channel-specific storefront behavior, and checkout constraints. Use official Hexagon docs if current docs list a BigCommerce integration. Otherwise treat it as custom.
Custom Catalogs
For custom commerce backends, define a stable contract:
- product identity
- variant identity
- canonical URL
- image URL rules
- price and currency
- inventory or availability
- categories and attributes
- discontinued or hidden product handling
- update frequency
Do not let agents guess a product schema. Use the merchant's actual data model.
Marketplaces
Marketplace implementations need extra care because the seller of record, inventory owner, payment flow, and fulfillment responsibility may differ by product. Confirm those relationships before creating product or purchase-path docs.