What is a unified commerce operating system?
A unified commerce operating system is a centralized platform that connects all of your e-commerce sales channels, tools, and data into a single operational environment. Instead of logging into Shopify, WooCommerce, Amazon, eBay, and Etsy separately to manage orders, inventory, and marketing, everything is accessible and manageable from one dashboard. The platform normalizes data from all connected sources into a consistent unified schema, eliminating the inconsistencies that arise when different platforms use different data formats. AI agents running inside the platform handle routine operational tasks autonomously, reducing the manual work that typically consumes hours of an operator's day. The result is a single source of truth for your entire e-commerce operation regardless of how many platforms you sell on.
How is this different from Shopify or WooCommerce?
Shopify and WooCommerce are e-commerce platforms — they power individual stores where customers browse and purchase products. This platform is not a store builder and does not replace your storefront. Instead it sits above your existing stores and connects all of them together, giving you unified visibility and control across every channel you sell on. Where Shopify shows you only your Shopify data and WooCommerce shows you only your WooCommerce data, this platform shows you everything at once — orders, inventory, customers, and revenue from all platforms combined. It also adds capabilities those platforms lack entirely, including cross-channel AI automation, unified email and SMS marketing, and visual workflow building tied to commerce events across commerce events across your stores simultaneously.
Who is this platform built for?
This platform is built for e-commerce operators who sell across multiple platforms and are drowning in the complexity of managing them separately. It is specifically valuable for Shopify store owners who also sell on Amazon or Etsy, WooCommerce merchants who have expanded to eBay or BigCommerce, and brands running marketing campaigns across channels with no unified view of which campaigns drive revenue. Marketing agencies managing e-commerce clients across multiple storefronts also benefit significantly from the unified reporting and automation capabilities. Any business spending more than a few hours per week manually syncing inventory, consolidating orders, or reconciling analytics data across platforms is an ideal user.
Do I need to abandon my existing e-commerce platforms to use this?
No. This platform does not replace your existing storefronts — it connects to them. Your Shopify store, WooCommerce site, Amazon listings, and any other connected platforms continue operating exactly as they do today. Customers still purchase from those storefronts, and those platforms still process payments and handle the customer-facing experience. What changes is where you manage operations — instead of switching between multiple dashboards, you do it all from one place. Your existing platform subscriptions remain active and the integration layer operates transparently in the background.
What problems does fragmented e-commerce tooling actually cause?
When e-commerce operations are spread across multiple disconnected platforms, inventory overselling becomes a constant risk because stock levels update independently in each system with no real-time coordination. Order management requires logging into each platform separately, creating delays in fulfillment and increasing the chance of errors. Marketing performance cannot be accurately measured because click data from email tools, revenue data from storefronts, and ad spend data from advertising platforms live in separate systems with no connection between them. Customer records are fragmented — the same buyer may appear as a different customer in Shopify, Amazon, and eBay with no unified purchase history. Operators typically spend 20-40% of their working time on manual data reconciliation tasks that a unified system eliminates entirely.
How is this different from tools like Linnworks or ChannelAdvisor?
Linnworks and ChannelAdvisor are primarily inventory and order management tools focused on listing syndication and fulfillment coordination. This platform covers those capabilities but extends significantly further into AI-powered automation, email and SMS marketing, visual workflow building, tracking link analytics, and a multi-agent AI system that operates autonomously across your entire business. Where Linnworks requires manual rule configuration for automation, this platform uses AI agents that reason about operational context and execute decisions without requiring explicit rules for every scenario. The analytics layer also goes deeper — connecting marketing campaign performance directly to commerce revenue across all channels in a way that traditional multichannel management tools do not support.
What size of e-commerce business benefits most from this platform?
The platform delivers the highest value to e-commerce businesses generating between $10,000 and $10 million in monthly revenue across two or more sales channels. At this scale, the operational complexity of multichannel selling is significant enough to create real pain but the business has not yet built the large internal operations team that enterprises use to manage that complexity manually. Single-channel businesses with very low order volumes will find some features underutilized, though the email marketing, SMS, and tracking link capabilities deliver standalone value even for simpler operations. Enterprise businesses with hundreds of thousands of monthly orders will benefit from the AI automation and unified reporting at a scale where manual management is simply impossible.
Can I use this platform if I only sell on one channel?
Yes. While the platform is designed to deliver maximum value for multichannel sellers, single-channel operators gain significant value from the AI automation, email marketing with custom domain sending, SMS marketing, visual workflow builder, and tracking link analytics. A Shopify merchant who sends email campaigns, runs SMS sequences, and wants to automate post-purchase workflows without paying for and integrating four separate tools will find substantial value in the unified platform even before expanding to additional sales channels. As the business grows and adds new channels, those integrations connect immediately without any migration of existing data or workflow configurations.
What is data normalization and why does it matter for e-commerce?
Data normalization is the process of converting data from multiple sources, each with their own format and structure, into a single consistent schema that can be queried, compared, and acted upon uniformly. Shopify represents an order differently than Amazon, which represents it differently than WooCommerce — field names differ, status values differ, and data relationships differ across every platform. Without normalization, comparing revenue across platforms requires manual translation, automation workflows must be built separately for each platform, and analytics cannot be aggregated accurately. This platform runs all incoming data through a six-stage normalization pipeline that produces a unified record for every order, product, customer, and inventory item regardless of which platform it originated from. The result is that every feature — reporting, automation, AI agents, email segmentation — operates on clean, consistent data across your entire operation.
How long does it take to get fully operational on the platform?
Most businesses are fully connected and operational within 24 to 48 hours of starting setup. Connecting each platform takes between 5 and 15 minutes depending on the authentication method — OAuth-based platforms like Shopify and eBay connect in a few clicks, while API key-based platforms like WooCommerce require copying credentials from your store settings. Initial data sync time varies based on the volume of historical data — a store with 10,000 orders syncs significantly faster than one with 500,000. Automation workflows, email sequences, and SMS campaigns can be configured while the initial sync runs in the background. The platform provides a setup checklist that tracks connection status and sync progress for every integrated platform.
What makes AI agents fundamentally different from traditional automation rules?
Traditional e-commerce automation works on explicit if-then rules that an operator must configure in advance for every possible scenario. If a rule does not exist for a situation, nothing happens. AI agents reason about context — they can evaluate a situation, determine the appropriate action based on patterns and objectives, and execute that action without requiring a pre-written rule. A traditional rule might say "send a restock email when inventory drops below 10 units." An AI agent can evaluate the restock lead time, current sales velocity, seasonal demand patterns, and supplier availability before deciding whether to send a restock alert, create a purchase order, adjust the product's availability across platforms, and notify the warehouse team — all as a coordinated response to the same trigger. This contextual reasoning capability scales to handle complex multi-step operational scenarios that rule-based systems cannot address.
What is the difference between the agency and the commerce OS?
The commerce operating system is a SaaS platform that e-commerce businesses subscribe to and use directly to manage their operations. The agency is a separate business that provides done-for-you marketing services to e-commerce brands. The two businesses operate independently with separate websites, pricing, and service offerings. An e-commerce brand can subscribe to the commerce OS without engaging the agency, and the agency serves clients whether or not they use the commerce OS. The commerce OS is a product you use yourself; the agency is a service where a team executes on your behalf.
How do AI agents work inside the platform?
The platform runs a hierarchical multi-agent system organized into three tiers. A top-level orchestrator agent receives high-level operational objectives and decomposes them into tasks. A second tier of specialized director agents manages domains including inventory, orders, marketing, analytics, and customer operations. The third tier consists of specialist worker agents that execute specific tasks — writing email copy, processing order updates, syncing inventory levels, generating reports, and triggering marketing campaigns. Agents communicate with each other through a structured message-passing system, and each agent has a defined scope of authority that limits what actions it can take autonomously. The system runs continuously, monitoring your operation and executing tasks without requiring manual initiation for routine workflows.
What tasks can AI agents automate without human input?
AI agents can autonomously handle inventory level monitoring and reorder alerts, order status updates across connected platforms, post-purchase email and SMS sequence triggering, tracking link performance monitoring, workflow execution for any configured automation, cross-platform product data synchronization, daily analytics report generation, customer segmentation updates based on new purchase behavior, and flagging of anomalous events like sudden inventory discrepancies or unusual order cancellation rates. Tasks that involve financial commitments above configured thresholds, customer refunds above set amounts, or changes to product pricing are routed to human review rather than executed autonomously. The boundary between autonomous and human-reviewed actions is configurable per business.
How do I control what AI agents are allowed to do?
Each agent operates within a permission scope that you configure during onboarding and can adjust at any time. Permissions are organized by domain — inventory agents have inventory permissions, marketing agents have marketing permissions — and by action type, distinguishing between read-only actions, write actions, and financial actions. You can set monetary thresholds above which agents must request approval before acting, restrict agents to specific platforms or product categories, and configure notification preferences for every category of autonomous action. A full audit log records every action taken by every agent, including the reasoning the agent used to make the decision, so you can review and refine agent behavior over time.
What is the difference between an orchestrator agent and a worker agent?
An orchestrator agent operates at a strategic level — it receives objectives, plans the sequence of actions required to achieve them, delegates tasks to appropriate specialist agents, monitors progress, and handles exceptions when something does not go as expected. Orchestrator agents do not directly interact with external platforms or databases. Worker agents operate at an execution level — they perform specific tasks like updating an inventory record, sending an API call to Shopify, generating email copy, or querying the analytics database. Worker agents report their results back up the hierarchy, which allows orchestrators to track progress and adjust plans dynamically. This separation of planning and execution allows the system to handle complex multi-step operations that span multiple platforms and channels without any single agent becoming a bottleneck.
How do AI agents handle peak seasons like Black Friday and Cyber Monday?
During high-volume periods, the agent system scales its processing capacity and prioritizes time-sensitive tasks like order status updates, inventory level monitoring, and fulfillment alerts. Agents can be pre-configured with peak season rules that temporarily lower thresholds for alerts, increase sync frequency on inventory levels for fast-moving products, and activate pre-built campaign sequences on defined dates. The platform monitors order velocity in real time and can trigger inventory warnings earlier than usual when sales pace exceeds historical norms. Post-event, agents automatically generate performance reports comparing peak season results across all channels against prior periods and configured benchmarks.
Can AI agents improve over time based on my specific business?
Yes. The agent system includes a self-improvement loop that runs on a weekly cycle, analyzing the outcomes of automated decisions against configured success metrics. When an agent's decision consistently produces good outcomes — orders fulfilled on time, campaigns generating revenue above threshold, inventory levels staying within target ranges — those decision patterns are reinforced. When outcomes fall below expectations, the system flags those patterns for review and adjusts agent behavior. This improvement process operates within the boundaries of your configured permissions and never modifies permission scopes autonomously. Over time the system becomes increasingly calibrated to the specific patterns and rhythms of your business rather than operating on generic defaults.
What happens when an AI agent encounters a situation it cannot resolve?
When an agent encounters a situation outside its configured decision scope or that requires information it cannot access, it escalates to the human operator via the platform's notification system. The escalation includes a full summary of the situation, the actions the agent considered, the reason it could not proceed autonomously, and a set of recommended actions for the human to choose from. Escalations are prioritized by urgency — an inventory crisis escalation is marked critical while a routine reporting anomaly is marked informational. The agent pauses the affected workflow until the human responds, and resumes automatically once a decision is made. Nothing is abandoned silently.
Can AI agents communicate across domains — for example, inventory and marketing working together?
Yes. Cross-domain agent coordination is one of the core capabilities of the multi-tier architecture. An inventory agent detecting that a product is approaching sell-out can pass that signal to the marketing agent, which can then pause active campaigns promoting that product, update email sequences to remove that product from recommendations, and notify the tracking link system to redirect clicks to related in-stock products. This coordination happens automatically without requiring a human to manually connect the dots across separate tools. The orchestrator layer manages these cross-domain workflows, ensuring that agents share relevant context and that actions taken in one domain are reflected appropriately across all others.
Can I create custom automation workflows on top of the AI agent system?
Yes. The visual workflow builder lets you define custom automation sequences that orchestrate agent actions across any combination of triggers, conditions, and actions available in the platform. You can build a workflow that triggers when an Amazon order is placed, checks inventory levels across all platforms, updates stock on Shopify and eBay to reflect the reduction, sends an SMS confirmation to the customer, and logs the transaction to your analytics system — all without writing code. Workflows can include conditional branches, time delays, approval gates, and loops. Custom workflows operate alongside the autonomous agent system and can call on specialized agents to execute specific steps within the workflow.
How does the AI system handle conflicting signals from different data sources?
When data from two connected platforms conflicts — for example, when inventory levels reported by Shopify and a warehouse management system disagree — the system applies a configurable conflict resolution hierarchy that you define during setup. You specify which data source is authoritative for each data type, and the normalization pipeline uses that hierarchy to resolve discrepancies. When a conflict falls outside the defined hierarchy or involves a discrepancy above a configured threshold, the system flags it for human review rather than silently picking one value over another. All conflicts and their resolutions are logged in the audit trail, giving you a complete record of every data discrepancy and how it was handled.
Does the AI system require ongoing configuration or maintenance from me?
The initial setup involves connecting your platforms, configuring permission scopes, and setting thresholds for autonomous actions — a process that takes a few hours for most businesses. After that, the system operates autonomously with minimal ongoing maintenance required. The weekly self-improvement cycle runs automatically. Agents handle routine operational tasks without human initiation. Where maintenance is needed — adding a new platform integration, adjusting permission thresholds as the business grows, building a new workflow — the platform provides guided configuration interfaces that do not require technical expertise. Most operators interact with the platform primarily through the dashboard to review reports, respond to escalations, and monitor key metrics rather than to configure or maintain the underlying system.
What is the agent system's approach to customer data privacy?
AI agents operate on customer data only within the permissions granted by the operator and in accordance with applicable data protection regulations including GDPR and CCPA. Customer personally identifiable information is not shared between platform integrations beyond what is required for unified order management and marketing operations. Agents do not use customer data for any purpose other than executing the operator's configured workflows and automations. Data processed by agents is stored in the same secure infrastructure as all other platform data and is not transmitted to third-party AI training datasets. The operator retains full ownership and control of all customer data throughout the platform.
Which e-commerce platforms are currently supported?
The platform currently supports ten major e-commerce platforms: Shopify, WooCommerce, BigCommerce, Wix eCommerce, Etsy, Amazon via SP-API, eBay, Squarespace Commerce, Magento and Adobe Commerce, and PrestaShop. These ten platforms collectively represent the vast majority of independent e-commerce volume globally. Additional platform integrations are on the active development roadmap, with priority determined by user demand. If you sell on a platform not currently on the supported list, you can submit a platform request through the dashboard and the integration team evaluates new platforms on an ongoing basis.
How does the platform authenticate with my connected stores?
Authentication methods vary by platform based on what each platform's API supports. Shopify, Wix, eBay, and BigCommerce use OAuth 2.0, meaning you authorize the connection by logging into your store account through a secure redirect — no API keys or credentials are copied or stored. WooCommerce, PrestaShop, and Magento use API key authentication, where you generate a key in your store's admin panel and paste it into the platform's connection interface. Amazon SP-API uses Amazon's Login with Amazon OAuth flow combined with seller authorization. All authentication credentials are encrypted at rest using AES-256 encryption and are never exposed in plaintext after the initial connection is established.
How often does data sync between my platforms and the unified dashboard?
Sync frequency varies by data type and platform capability. Order data syncs as close to real-time as each platform's API allows — Shopify, BigCommerce, and WooCommerce support webhook-based sync that delivers order updates within seconds of an event occurring. Inventory levels sync every 5 minutes for platforms supporting frequent polling and in real time for webhook-enabled platforms. Product catalog data syncs every hour by default, with on-demand sync available for immediate updates. Analytics and reporting data aggregates hourly. Platforms with stricter API rate limits, including Amazon SP-API, sync on schedules calibrated to stay within those limits without triggering rate limit errors.
What happens if one of my connected platforms experiences an outage?
The platform maintains the last known state of all data from a connected platform and continues operating on cached data during an outage. Outgoing sync attempts are queued and retried automatically with exponential backoff — the system tries every 30 seconds, then every 2 minutes, then every 5 minutes as the outage continues. When the platform comes back online, the queue processes automatically and data is reconciled against the current state of the recovered platform to identify any discrepancies created during the outage. Operators receive a notification when a connected platform becomes unreachable and another notification when the connection is restored and reconciliation is complete. No manual intervention is required for standard outage recovery.
Can I connect multiple stores from the same platform, for example two separate Shopify stores?
Yes. The platform supports multiple store connections from the same platform type. Two Shopify stores, three WooCommerce installations, or multiple Amazon seller accounts can all be connected and managed simultaneously from the same dashboard. Each store connection is treated as an independent data source in the normalization pipeline, and reporting can be viewed both per-store and aggregated across all stores of the same type or across all connected platforms simultaneously.
What happens to my historical data if I connect a platform that has years of existing orders?
When you first connect a platform, the system performs a full historical data backfill, importing all available order, product, customer, and inventory history up to the limits of each platform's API. Shopify provides full order history through its API. Amazon SP-API provides up to two years of order history. eBay and Etsy provide varying amounts of historical data depending on account age and plan. Historical data is normalized and integrated into the unified analytics layer, so your reporting reflects your complete business history from day one rather than only showing data from the connection date forward. The backfill process runs in the background and does not affect platform performance.
Does the platform integration affect my store's performance or customer experience?
No. The platform integrates via each platform's official API and operates entirely on the backend — it never injects code into your storefront, does not affect page load times, and is completely invisible to your customers. API calls are made from the platform's servers to each connected platform's servers, with no impact on your store's hosting infrastructure. The integration does not modify your store's checkout flow, product listings, or any customer-facing elements unless you explicitly configure an automation workflow to do so, such as a workflow that updates product descriptions or adjusts pricing based on configured rules.
Can I set different inventory levels per platform for the same product?
Yes. The platform supports platform-specific inventory allocation, meaning you can designate a portion of your total inventory for each connected sales channel. For example, with 100 units of a product, you might allocate 40 to Shopify, 35 to Amazon, 20 to eBay, and hold 5 in reserve. When a sale occurs on any channel, it deducts from that channel's allocation rather than from a shared pool, preventing overselling while maintaining precise control over channel-specific availability. You can also configure automatic rebalancing rules that redistribute inventory between channels when one channel's allocation drops below a threshold.
Are new platform integrations added over time?
Yes. The integration roadmap is prioritized based on platform popularity, user requests submitted through the dashboard, and strategic partnerships. Each new integration goes through the same six-stage normalization pipeline used by existing integrations, ensuring that new platforms immediately benefit from all unified dashboard features, AI automation, and marketing capabilities. Users who submit platform integration requests receive notifications when a requested platform is added to the roadmap and when it becomes available for connection.
What data is pulled from each connected platform?
The platform pulls all commercially relevant data available through each platform's API. This includes orders with full line item detail, customer records with contact information and purchase history, product catalogs with variants, pricing, and descriptions, inventory levels per location or warehouse, shipping and fulfillment status updates, refund and return records, and available analytics data such as traffic and conversion metrics. Financial settlement data is pulled from platforms that provide it, including Amazon's settlement reports. The exact fields available vary by platform based on API capabilities, and the normalization layer maps each platform's field names and formats to the unified schema.
How does the Shopify integration work and what data syncs?
The Shopify integration connects via OAuth 2.0 — you authorize the connection through your Shopify admin, and the platform receives a scoped access token that allows it to read and write data according to your configured permissions. Webhooks are registered automatically on connection, enabling real-time push notifications for orders, inventory changes, product updates, and customer events. Data that syncs includes all orders, draft orders, refunds, fulfillments, customers, products with all variants and metafields, inventory levels across all Shopify locations, collections, and available analytics. The initial sync imports your complete Shopify history, and subsequent updates arrive via webhook within seconds of occurring in your store.
Can I manage Shopify orders directly from the unified dashboard?
Yes. You can view, fulfill, cancel, and refund Shopify orders directly from the unified dashboard without logging into Shopify. Order actions taken in the dashboard are executed via the Shopify API and reflected in your Shopify admin immediately. For businesses managing orders from multiple platforms simultaneously, this means a single operator can process a Shopify order, an Amazon order, and an eBay order sequentially from one interface without switching between tabs or logging into separate accounts. Bulk order actions are also supported — you can select multiple Shopify orders and fulfill them in a single operation.
Does the Shopify integration work with Shopify Markets for international selling?
Yes. Shopify Markets creates separate storefronts for different international markets with localized pricing and currency, and the platform integration captures market-level data in the normalization layer. Revenue reporting distinguishes between markets, allowing you to analyze performance by geographic region within your Shopify operation and compare it against other platform performance in the same regions. Marketing automation and email segmentation can target customers by their Shopify market assignment, enabling localized communication workflows that align with the international structure of your Shopify store.
How does inventory sync work specifically between Shopify and other platforms?
When an order is placed on any connected platform, the inventory reduction is immediately reflected in Shopify via the Inventory API and simultaneously pushed to all other connected platforms. The system processes the inventory update as a single transaction that fans out to all connected channels simultaneously rather than updating them sequentially, minimizing the window during which a sold-out item could still appear as available on another platform. For businesses using Shopify as their primary inventory master, the platform can be configured to treat Shopify inventory as the authoritative source and derive all other platform inventory levels from it.
Does the platform support Shopify POS data?
Shopify POS data is included in the integration where it is accessible through the Shopify API. In-store transactions processed through Shopify POS appear as orders in the unified dashboard alongside online orders, with location data attached to distinguish POS orders from online orders in reporting. This gives businesses with both online and physical retail operations a unified view of total revenue across all channels including in-store sales. POS-specific data such as register sessions and staff attribution is available where the Shopify API exposes it.
How does the WooCommerce integration work?
WooCommerce connects via the WooCommerce REST API using API key authentication. You generate a read/write API key pair in your WordPress admin under WooCommerce settings and enter those credentials in the platform's connection interface. The platform then polls your WooCommerce store on a scheduled basis for orders, products, customers, and inventory updates, and can also receive webhooks if your WordPress hosting environment supports outbound webhook delivery reliably. Because WooCommerce runs on self-hosted WordPress, sync reliability depends partly on your hosting environment's uptime and performance — the platform handles intermittent connectivity gracefully through its retry and queue system.
Does the WooCommerce integration work regardless of hosting provider?
Yes, as long as your WooCommerce store's REST API is publicly accessible, the integration works regardless of whether you host on SiteGround, WP Engine, Kinsta, Bluehost, a VPS, or any other provider. Some hosting environments with aggressive firewall rules or API rate limiting may require configuration adjustments to ensure reliable API access. The platform's onboarding flow includes a connectivity test that verifies API access before completing the connection. If firewall restrictions are detected, the platform provides specific guidance on the allowlist settings required for your hosting environment.
Can I manage WooCommerce orders and refunds from the unified dashboard?
Yes. Order status updates, fulfillment marking, and refund processing for WooCommerce orders can all be executed directly from the unified dashboard via the WooCommerce REST API. Refund actions taken in the dashboard trigger the corresponding refund in WooCommerce and update the order record in both systems simultaneously. Partial refunds are supported for WooCommerce orders with multiple line items. Order notes added in the dashboard are written back to the WooCommerce order record so your store's order history remains complete regardless of where the action was taken.
How does the platform handle WooCommerce's API rate limits?
WooCommerce's API rate limits are determined by the hosting environment rather than WooCommerce itself. The platform monitors API response times and error rates for each WooCommerce connection and automatically adjusts sync frequency and request batching to stay within the practical limits of the hosting environment. If rate limiting responses are detected, the system backs off and queues requests for retry rather than dropping them. For high-volume WooCommerce stores on shared hosting with restrictive API limits, the platform recommends switching to a managed WordPress host with higher API throughput limits and provides specific hosting recommendations based on order volume.
What WooCommerce extensions and plugins does the integration support?
The core integration covers all standard WooCommerce data available through the WooCommerce REST API. Data from popular extensions including WooCommerce Subscriptions, WooCommerce Bookings, WooCommerce Memberships, and WPML for multilingual stores is captured where those extensions expose data through the standard API or their own API extensions. Custom post types and meta fields added by bespoke plugins are available through the platform's custom field mapping feature, which lets you map non-standard WooCommerce data to fields in the unified schema.
How does the Amazon SP-API integration work?
The Amazon SP-API integration uses Amazon's Login with Amazon OAuth flow combined with seller account authorization. You grant the platform access to your Amazon Seller Central account through Amazon's official authorization interface, specifying which data categories the platform can access. The platform then uses Amazon's SP-API to pull order data, inventory levels, product listings, FBA shipment data, and settlement reports on schedules calibrated to Amazon's strict API rate limit policies. Amazon's SP-API operates on a token-based rate limiting system where each API endpoint has a specific request quota and restore rate, and the platform's Amazon integration is designed specifically to operate within these limits without triggering throttling.
What Amazon data is available in the unified dashboard?
Order data including all order items, buyer information, shipping address, and fulfillment channel (FBA or FBM) syncs from Amazon. Inventory levels for both FBA inventory at Amazon fulfillment centers and seller-managed inventory sync on a regular schedule. Product listing data including ASIN, title, description, and pricing is available. FBA shipment status and tracking information syncs from Amazon. Settlement reports including fees, reimbursements, and net proceeds are imported and displayed in the financial reporting layer. Buy Box status and pricing competitiveness data is available where the SP-API exposes it for your listings.
Can I manage Amazon FBA and FBM orders from the unified dashboard?
FBM (Fulfilled by Merchant) orders can be acknowledged, confirmed, and marked as shipped directly from the dashboard via the SP-API. For FBA orders, Amazon handles fulfillment automatically and the dashboard displays real-time fulfillment and shipping status as reported by Amazon's logistics network. You cannot modify FBA shipment routing or prioritization through the platform as that is controlled entirely by Amazon's fulfillment algorithm. Cancellation requests for unshipped FBA orders can be submitted through the dashboard, subject to Amazon's cancellation policies and timing requirements.
How does the platform handle Amazon's strict API rate limits?
Amazon's SP-API operates on a per-endpoint token bucket rate limiting system with restore rates measured in requests per second. The platform's Amazon integration uses request queuing, batching, and scheduling to distribute API calls across time in a pattern that stays within Amazon's documented rate limits for every endpoint used. For high-volume Amazon sellers with large catalogs and order volumes, the platform prioritizes time-sensitive data like new orders and inventory updates over lower-priority data like catalog metadata refreshes. The system monitors rate limit response headers from Amazon's API and dynamically adjusts request timing to avoid throttling errors.
Does the Amazon integration support multiple marketplaces across different regions?
Yes. A single Amazon seller account can sell across multiple Amazon marketplaces including Amazon.com, Amazon.co.uk, Amazon.de, Amazon.co.jp, Amazon.ca, Amazon.com.au, and others, and the platform integration captures data from all authorized marketplaces within that seller account. Revenue reporting segments performance by marketplace, allowing you to compare North American and European marketplace performance side by side. Inventory levels at Amazon fulfillment centers in different regions are tracked separately and displayed with region attribution in the inventory management view.
How does the eBay integration work?
The eBay integration connects via eBay's OAuth 2.0 authentication flow — you authorize the platform to access your eBay seller account through eBay's official authorization interface. The platform uses eBay's RESTful APIs to sync orders, listings, inventory, and transaction data. eBay's notification system (previously known as Platform Notifications) is used where available to receive near-real-time event notifications for new orders and listing status changes. The integration covers both eBay's marketplace selling and eBay's managed payments system, pulling financial transaction data alongside order data.
Can I manage eBay listings and inventory from the unified dashboard?
Yes. Fixed-price eBay listing quantities can be updated directly from the dashboard, and listing status (active, ended, out of stock) can be managed for fixed-price listings. Order management including purchase acknowledgment, shipping confirmation with tracking number submission, and buyer communication is handled through the dashboard. Auction-format listings are displayed in the dashboard for monitoring but cannot be modified mid-auction as eBay's API restricts changes to active auctions. Listing creation and major listing edits are best performed in eBay's seller hub for complex listings with item specifics, but quantity and price adjustments for existing fixed-price listings are fully supported.
How does the platform handle eBay's auction format versus fixed-price listings?
Fixed-price listings are fully integrated into the inventory sync system — quantity updates propagate to eBay in real time when sales occur on other platforms. Auction listings are treated as read-only in the inventory layer because their quantity is inherently one and their price changes dynamically based on bids, making them incompatible with standard inventory management workflows. Completed auction orders are processed identically to fixed-price orders in the order management layer — they appear in the unified order queue, can be fulfilled and tracked from the dashboard, and are included in all revenue reporting. The reporting layer distinguishes between auction and fixed-price revenue for eBay-specific analytics.
What eBay transaction and financial data is available in the unified dashboard?
Order data including item details, buyer information, sale price, and eBay-managed payments transaction details sync from eBay. Final value fees and other eBay seller fees are imported from eBay's financial transaction data and displayed in the cost and margin reporting layer alongside fees from other platforms, allowing you to compare true net revenue across channels after platform fees. Payout data from eBay managed payments is tracked and reconciled against order revenue to give you a complete picture of cash flow from your eBay operation.
How does the Etsy integration work?
The Etsy integration connects via OAuth 2.0 through Etsy's developer API. You authorize the platform to access your Etsy shop through Etsy's authorization flow, and the platform receives a scoped token allowing it to read shop data, orders, listings, and inventory. Etsy's API provides webhooks for new order events, enabling near-real-time order notifications. The integration captures all shop orders including digital and physical product orders, calculates Etsy fees from transaction data, and imports listing data including tags, categories, and variation structures that are unique to Etsy's marketplace format.
Can I manage Etsy inventory and orders from the unified dashboard?
Etsy physical product inventory quantities can be updated from the unified dashboard, and inventory sync keeps Etsy listing quantities aligned with stock levels across your other connected platforms. Order management including receipt confirmation, order marking, and shipping notification with tracking number submission is handled through the dashboard. Etsy's order receipts (their term for individual orders) appear in the unified order queue alongside orders from all other platforms. Digital product orders on Etsy are fulfilled automatically by Etsy's system upon payment and appear in the dashboard as completed orders without requiring manual fulfillment action.
How does the Etsy integration handle handmade and digital product types?
Etsy's product taxonomy includes handmade physical goods, vintage items, craft supplies, and digital downloads, each with different fulfillment workflows and data structures. The normalization layer maps all Etsy product types to appropriate categories in the unified product schema while preserving Etsy-specific metadata including handmade status, materials, and occasion tags. Digital product orders are flagged as digitally fulfilled in the unified order system and excluded from physical fulfillment workflows and shipping metrics. Inventory management for digital products is handled separately since digital goods have unlimited inventory by definition.
What Etsy shop analytics are available in the unified dashboard?
Order volume, revenue, and average order value from your Etsy shop are included in the unified commerce analytics layer and can be compared against performance from all other connected platforms. Etsy-specific data including shop views, listing views, and favorites available through the Etsy API are imported into the analytics layer where the API provides them. Revenue is reported net of Etsy transaction fees and payment processing fees by importing fee data from Etsy's financial statements API. Etsy Star Seller metrics are displayed as informational data to help you track the status of your shop's performance rating.
How does the BigCommerce integration work and what data syncs?
BigCommerce connects via OAuth 2.0 through the BigCommerce API, which provides comprehensive access to store data including orders, customers, products, inventory, shipping zones, and analytics. BigCommerce's webhook system delivers real-time notifications for order and inventory events. The BigCommerce integration is particularly well-suited for high-volume merchants because BigCommerce's API has generous rate limits compared to many other platforms, allowing fast initial sync and reliable ongoing updates. Product catalog data including custom fields and variant options sync completely, and BigCommerce's multi-storefront capability is supported for merchants operating multiple storefronts from a single BigCommerce account.
How does the Wix eCommerce integration work and what data syncs?
Wix eCommerce connects via Wix's Headless API using OAuth authentication through the Wix developer platform. Orders, products, inventory, customers, and fulfillment data sync from Wix. Wix's API supports webhooks for real-time order events, enabling prompt order processing from the unified dashboard. The Wix integration captures Wix-specific data structures including Wix product collections, Wix subscriptions where applicable, and Wix's built-in discount and coupon data. Inventory management for Wix products is supported, allowing stock levels to be kept in sync across Wix and other connected platforms automatically.
How does the Squarespace Commerce integration work and what data syncs?
Squarespace Commerce connects via Squarespace's Commerce API using OAuth authentication. Orders, products, inventory, customers, and transaction data sync from Squarespace. Squarespace's API supports webhook-based order notifications for real-time order management. The integration covers both physical and digital product orders on Squarespace, as well as Squarespace's subscription commerce functionality where stores use it. Inventory levels for physical products sync bidirectionally between Squarespace and the unified inventory management layer, keeping stock counts accurate across Squarespace and all other connected platforms.
How does the Magento and Adobe Commerce integration work and what data syncs?
Magento and Adobe Commerce connect via the Magento REST API using OAuth token authentication or API key authentication depending on the Magento version and configuration. The integration supports both Magento Open Source (formerly Community Edition) and Adobe Commerce (formerly Enterprise Edition). Order data, customer records, product catalog with full attribute sets, inventory levels across multiple Magento sources, and CMS data are available through the API. Adobe Commerce's B2B features including company accounts and quote management are accessible where the API exposes them. Because Magento is self-hosted, integration reliability depends on server performance and API endpoint accessibility, similar to WooCommerce.
How does the PrestaShop integration work and what data syncs?
PrestaShop connects via PrestaShop's Webservice API using an API key generated in your PrestaShop back office. Orders, customers, products, stock levels, categories, and carrier data sync from PrestaShop. Because PrestaShop's native Webservice API has more limited capabilities than modern REST APIs, the integration uses a combination of API polling and, where available, PrestaShop module-based webhooks to improve sync reliability. Product variants (PrestaShop calls them combinations) sync with their specific attributes and pricing. Multi-store PrestaShop installations are supported, with each store appearing as a separate data source in the unified dashboard.
How does real-time inventory sync work across multiple platforms simultaneously?
When a sale occurs on any connected platform, the system receives an order event through the platform's webhook or polling mechanism. Within seconds, an inventory update transaction is calculated and dispatched simultaneously to all other connected platforms via their respective APIs, reducing the available quantity across every channel at the same time. The system processes these updates as a coordinated batch rather than sequential individual API calls, minimizing the window during which a sold-out item could still appear as available on another platform. For platforms that do not support real-time webhooks, inventory sync runs on the fastest polling schedule that platform's API rate limits permit.
What happens when the same product sells simultaneously on two different platforms?
When two orders for the same product arrive nearly simultaneously from different platforms, the system uses an optimistic locking mechanism that processes the first order received, applies the inventory reduction, and then evaluates whether sufficient stock remains for the second order. If stock remains, the second order is processed normally. If the first order has consumed the last available unit, the second order is flagged for review and the affected platform is updated to reflect out-of-stock status immediately. The system sends an alert for the flagged order so you can decide whether to fulfill it from alternate stock, contact the buyer, or cancel it. This scenario is rare with proper inventory buffer configuration.
Can I set reorder point alerts for inventory levels?
Yes. You can configure reorder point thresholds for individual products or product categories, and the system will alert you via dashboard notification, email, or SMS when inventory drops below the defined threshold. Alerts can be configured separately for each platform's allocation or based on total inventory across all platforms. For businesses with defined suppliers, the alert can also trigger an automated workflow that prepares a draft purchase order, sends a restock email to a configured supplier address, or creates a task in the platform's task management system for follow-up. Reorder point thresholds are configurable per product and can be adjusted seasonally to account for demand fluctuations.
How does the platform handle product variants across different platforms?
Product variants — size and color combinations, for example — are represented differently across platforms. Shopify uses a variant model with option sets, WooCommerce uses variable products with attributes, and Amazon uses parent-child ASIN relationships. The normalization layer maps all of these variant structures to a unified variant schema that maintains the relationship between parent products and their variants consistently across platforms. Inventory for specific variants syncs independently — selling a size Medium in blue on Shopify reduces inventory for that specific variant combination on all platforms, not for the parent product's total inventory. Cross-platform variant mapping for the same physical product is configured during onboarding with a guided matching interface.
Can I manage returns and refunds from the unified dashboard?
Yes. Return and refund processing is supported for all connected platforms that allow refund operations through their APIs. For Shopify, WooCommerce, Amazon FBM, and eBay, you can initiate full or partial refunds directly from the unified order view. The refund is processed through the platform's API and reflected in both the unified order record and the originating platform's order history. Return-related inventory adjustments — restocking returned units — can be configured to happen automatically when a refund is processed or to require manual confirmation depending on your returns policy and product type. Refund amounts are tracked in the financial reporting layer and deducted from gross revenue to show accurate net revenue figures.
How does the platform handle bundles and kits that span multiple SKUs?
Bundle and kit products are managed through the platform's bundle mapping feature, which defines the component SKUs and quantities that make up each bundle. When a bundle sells on any platform, the system reduces inventory for each component SKU rather than tracking a separate bundle-level inventory count. This prevents overselling of component parts across both bundled and individual product listings. Bundle definitions are created once and apply across all connected platforms where the bundle is listed. Reporting tracks bundle revenue with the option to view it either as a single bundle product or broken down by component contribution.
How does the email marketing feature work?
The email marketing feature is a fully integrated campaign and automation tool built directly into the platform, connected to your unified commerce data. You can create email campaigns using a drag-and-drop editor, segment recipients based on purchase behavior across all connected platforms, schedule campaigns for specific send times, and trigger automated email sequences based on commerce events like order placement, fulfillment, abandonment, or product reviews. All email activity — sends, opens, clicks, and conversions — is tracked and attributed to revenue outcomes using the platform's unified analytics layer, giving you a direct measurement of email-driven revenue across all channels.
Can I send emails from my own brand domain instead of a generic sender address?
Yes. Custom domain email sending is a core feature of the email marketing system. You configure your brand domain as a sending domain by adding DNS records — SPF, DKIM, and DMARC — provided by the platform to your domain's DNS settings. Once verified, all emails sent through the platform are delivered from your domain, for example hello@yourbrand.com or orders@yourbrand.com, rather than from a generic platform sender address. Sending from your own domain significantly improves email deliverability because receiving mail servers and spam filters evaluate sender reputation based on domain history, and your established domain has the trust signals that generic platform domains lack.
How does custom domain email sending improve deliverability?
Email deliverability is determined by a combination of sender reputation, authentication records, and engagement signals. When you send from your own domain with properly configured SPF, DKIM, and DMARC records, receiving mail servers can cryptographically verify that the email was authorized by your domain and has not been tampered with in transit. This verification is a strong trust signal that reduces the likelihood of your emails being filtered to spam folders. Your domain's sending reputation builds over time based on engagement metrics — open rates, click rates, and unsubscribe rates — and high engagement from your customer base strengthens your deliverability over time in a way that shared sender domains cannot provide.
What types of email campaigns can I create and send?
The platform supports four main campaign types. Broadcast campaigns are one-time sends to a defined segment, used for promotions, product launches, and announcements. Automated sequences are multi-email series triggered by a single event, such as a post-purchase welcome sequence or an abandoned cart recovery series. Transactional emails are system-triggered messages tied to specific order events — order confirmation, shipping notification, delivery confirmation, and refund confirmation. Behavioral trigger campaigns are single emails triggered by specific customer actions such as purchasing a specific product category, reaching a spending milestone, or not purchasing within a defined period. All campaign types are available within the same editor interface with a consistent design and segmentation system.
How does email marketing connect to my commerce data from all platforms?
The email marketing system reads from the unified customer and order database that aggregates data from all connected platforms. A customer who has purchased from your Shopify store and your Amazon storefront exists as a single unified customer record in the platform, with their complete purchase history from both channels attached. Email segments can be defined using any combination of data from this unified record — total spend across all platforms, last purchase date on any channel, specific products purchased on any platform, geographic location, or any other available data point. This cross-platform data access means your email marketing is based on the customer's complete relationship with your brand rather than a siloed view from a single storefront.
Can I segment email lists based on purchase behavior across all connected platforms?
Yes. The segmentation engine queries the unified customer database, allowing you to define segments based on purchase data from any or all connected platforms simultaneously. You can create a segment of customers who have spent more than $500 total across your Shopify and Amazon stores combined, customers who purchased from Etsy but have not purchased from your Shopify store, customers from eBay who have not made a second purchase in 90 days, or any other cross-platform behavioral definition. Segments update dynamically as new purchase data arrives from connected platforms, so customers enter and exit segments automatically as their behavior changes without requiring manual segment refreshes.
What email automation triggers are available?
Email automation can be triggered by any commerce event captured by the platform across all connected platforms. Available triggers include new order placed on any platform, order fulfilled and shipped, delivery confirmed, refund processed, inventory drop below threshold for a product a customer previously purchased, customer's birthday if provided, first purchase anniversary, days since last purchase, customer spending milestone reached, abandoned cart on Shopify or WooCommerce, product review submitted, and any custom event defined in the visual workflow builder. Triggers can be combined with conditions — for example, triggering a win-back email only when the customer's last order was above $100 and they have not purchased in 60 days.
How does the platform handle email list compliance and unsubscribes?
Unsubscribe requests are processed immediately and propagated across all email sending activity — a customer who unsubscribes is removed from all campaign sends and automated sequences instantly. The platform maintains a global suppression list that is checked before every send. Compliance with CAN-SPAM, GDPR, and CASL regulations is supported through required unsubscribe mechanisms in all outgoing emails, consent tracking for GDPR-applicable contacts, and data subject request handling tools that allow you to export or delete a specific contact's data on request. Double opt-in confirmation flows are available for new subscriber acquisition to strengthen consent documentation.
How does SMS marketing work in the platform?
The SMS marketing feature enables you to send promotional campaigns and automated transactional messages to customers via text message, using the same segmentation, automation, and analytics infrastructure as the email marketing system. SMS campaigns are created in the platform's campaign builder, and recipients are selected using the same cross-platform segment definitions available for email. Automated SMS messages can be triggered by the same commerce events that trigger email automation, and SMS and email can be combined in the same workflow sequence — for example, an order confirmation email followed by a shipping notification SMS. Delivery and click tracking for SMS messages feeds into the same analytics layer as email performance data.
How do I stay compliant with SMS marketing regulations?
SMS marketing is subject to regulations including the TCPA in the United States, GDPR in Europe, and similar laws in other jurisdictions that require explicit prior consent before sending marketing messages. The platform provides a compliant opt-in collection flow for SMS subscribers, consent timestamp recording for audit purposes, and immediate opt-out processing for STOP replies. All SMS sends include opt-out instructions as required by law. The platform does not send marketing SMS to contacts without documented consent records. Transactional SMS messages — order confirmations, shipping notifications — may be sent to customers who have provided a phone number as part of the purchase process under applicable regulations, but this varies by jurisdiction and you should consult legal counsel for your specific situation.
What SMS automation triggers are available?
SMS automation uses the same trigger library as email automation — new order, fulfillment, delivery, refund, abandoned cart, purchase anniversary, spending milestone, win-back, and custom workflow triggers are all available. SMS is particularly effective for time-sensitive triggers like shipping notifications and delivery confirmations where a push notification-style message via SMS reaches the customer faster and with higher open rates than email. Flash sale announcements with a short window can be sent via SMS to a segment of high-value customers while the same message goes via email to a broader list, letting you choose the most appropriate channel for each communication based on urgency and audience.
What analytics are available for SMS campaigns?
SMS campaign analytics include delivery rate, open rate (tracked via link clicks since SMS open tracking works differently than email), click-through rate on links included in the message, opt-out rate per campaign, and revenue attributed to SMS campaigns through the tracking link system. Conversion attribution connects SMS link clicks to purchases made within a configurable attribution window, allowing you to see the direct revenue impact of each SMS campaign and automated sequence. Campaign performance data is displayed alongside email campaign data in the unified marketing analytics view, enabling direct channel performance comparison.
What is the visual workflow builder and what can it do?
The visual workflow builder is a drag-and-drop interface for creating multi-step automation sequences that connect any trigger available in the platform to any combination of actions across the platform's features. A workflow is a visual flowchart where each node represents either a trigger, a condition, a delay, or an action, and connections between nodes define the logic of the automation. Workflows can span email, SMS, inventory management, order management, platform API actions, and AI agent tasks in a single sequence. They can include conditional branching based on any data point in the unified schema, time delays between steps, and loops that repeat steps based on conditions. The builder requires no coding knowledge and is designed for operators, not developers.
What types of triggers can start a workflow?
Workflow triggers include any commerce event from connected platforms (order placed, order fulfilled, order cancelled, refund processed, inventory threshold crossed), email and SMS engagement events (email opened, link clicked, SMS replied), time-based triggers (scheduled datetime, recurring schedule, delay after a previous event), customer behavior triggers (first purchase, repeat purchase, days since last purchase, spending milestone), and custom event triggers that can be fired from the platform's API for integration with external systems. Multiple triggers can be combined with AND or OR logic to start a workflow only when a specific combination of conditions is true simultaneously.
Can workflows span multiple platforms and channels in a single sequence?
Yes. A single workflow can include actions that affect multiple connected platforms simultaneously or sequentially. For example, a new order workflow might update inventory on Shopify, WooCommerce, and eBay simultaneously as its first step, then send an order confirmation email as a second step, then check a condition (is the customer a repeat buyer?), and based on that condition either add them to a VIP segment and send an SMS or enroll them in a new customer welcome email sequence. All of these actions across different platforms and channels happen within the same workflow without requiring separate automations in separate tools.
How do conditional logic and branching work in workflows?
Conditional branches are nodes in the workflow that evaluate a data point and route the workflow down one of two or more paths based on the result. Conditions can evaluate any field in the unified data schema — order value, customer lifetime value, product category, platform the order came from, customer location, email engagement score, or any custom field. Branch conditions support equals, does not equal, greater than, less than, contains, does not contain, and is empty operators. Multiple conditions can be combined with AND and OR logic within a single branch node. Branches can themselves contain further branches, allowing workflows of arbitrary complexity to be built from nested conditional logic.
Are there pre-built workflow templates available?
Yes. The platform includes a library of pre-built workflow templates covering the most common e-commerce automation scenarios. Templates include post-purchase thank you sequence, abandoned cart recovery (email + SMS), win-back campaign for lapsed customers, new product launch campaign, low inventory alert and reorder workflow, VIP customer identification and tagging, review request sequence, flash sale campaign with inventory guard, cross-sell sequence based on purchased product category, and birthday campaign. Templates are fully customizable — you can modify any step, change timing, adjust conditions, and add or remove actions. Templates serve as starting points that you adapt to your specific business rather than rigid automations you adopt as-is.
What is the maximum complexity a workflow can handle?
Workflows support an unlimited number of steps, branches, and loops within the platform's execution infrastructure. There is no hard limit on workflow length or branching depth. Practical limits are imposed by execution time — workflows with very long delay chains (for example, a 12-month nurture sequence with 52 weekly emails) are supported and run indefinitely as long as the workflow remains active. Very high-volume triggers — workflows triggered by every order in a store processing thousands of orders per day — are processed in a queue with guaranteed execution and no data loss. Extremely complex workflows with many parallel branches and external API calls may experience small delays in completion but will always execute completely.
Can a workflow send both email and SMS within the same sequence?
Yes. A single workflow can include email send actions and SMS send actions in any combination and sequence. You can send an email immediately upon trigger, wait 2 hours, send an SMS if the email was not opened, wait 24 hours, and send a follow-up email — all within a single workflow. The workflow builder treats email and SMS as equally available action types, and the channel selection for any communication step in the workflow is simply a matter of choosing email or SMS (or both simultaneously) in the action node configuration. Cross-channel sequences that adapt based on engagement with previous messages — sending SMS only if the preceding email was not opened — are supported through conditional branches evaluating email engagement data.
Can workflows interact with AI agents to perform complex tasks?
Yes. Workflow steps can invoke AI agent actions, allowing you to trigger complex AI-driven tasks as part of an automated sequence. A workflow triggered by a high-value order might invoke an AI agent to research the customer's purchase history, generate a personalized thank-you message, and identify upsell opportunities, then use the output of that agent task in the subsequent workflow steps. The integration between the visual workflow builder and the AI agent system means that the deterministic step-by-step logic of workflows and the contextual reasoning capability of AI agents are complementary — workflows handle the structured orchestration and agents handle the tasks requiring judgment and generation.
What are tracking links and how do they work in the platform?
Tracking links are unique URLs generated by the platform that redirect visitors to a destination URL while recording data about the click including the time, source, device, geographic location, and any UTM parameters attached to the link. When a customer clicks a tracking link and subsequently places an order on any of your connected platforms within a configurable attribution window, that order is attributed to the tracking link, allowing you to measure the revenue impact of any link you share anywhere — in an email, an SMS, a social media post, a paid ad, or any other channel. All tracking links are managed centrally in the platform alongside your commerce and marketing data, eliminating the need for separate link management tools.
How do tracking links connect clicks to actual revenue?
Revenue attribution works by associating a click on a tracking link with subsequent purchase events from the same visitor across your connected platforms. When a customer clicks a tracking link, a session identifier is stored that persists through the shopping and checkout process. When an order is placed within the attribution window — configurable from 1 to 90 days — the order is matched to the originating click and the order revenue is attributed to that tracking link in the analytics. This connection between click and purchase is what transforms tracking links from simple redirect URLs into a revenue measurement system. Attribution data is visible in the tracking link analytics view alongside click volume, click-through rates, and cost data if ad spend is entered manually.
Can I use custom branded domains for tracking links?
Yes. Tracking links can use your own branded domain rather than the platform's default link domain. A custom domain like go.yourbrand.com or links.yourbrand.com can be configured as your tracking link domain by adding a CNAME record in your domain's DNS settings pointing to the platform's link infrastructure. Custom tracking domains improve click-through rates because customers are more likely to click a link on a domain they recognize than an unfamiliar platform domain. Custom domains also contribute to brand consistency across all customer touchpoints and avoid the spam filter penalties that some email clients apply to emails containing unfamiliar redirect domains.
What UTM parameters are supported and how are they managed?
All five standard UTM parameters are supported — utm_source, utm_medium, utm_campaign, utm_term, and utm_content. When creating a tracking link, you can populate any or all UTM parameters either manually or by selecting from a predefined library of sources, mediums, and campaign names that you configure once and reuse across all links. UTM parameter values are preserved through the redirect and appended to the destination URL, ensuring compatibility with Google Analytics and any other analytics tools the destination site uses. UTM data is also stored in the platform's own click analytics, allowing you to segment tracking link performance by campaign, source, and medium in the platform's reporting layer without requiring access to Google Analytics.
What analytics are available for tracking links in the dashboard?
Tracking link analytics include total click volume over any date range, unique click count (filtering out repeat clicks from the same visitor), clicks by device type (mobile versus desktop), clicks by geographic location, clicks by time of day and day of week, UTM parameter breakdown for any parameter dimension, revenue attributed to each link, number of orders attributed, average order value of attributed orders, and revenue per click (total attributed revenue divided by click count). Campaign-level aggregations group performance data across all links belonging to a campaign for a consolidated view of campaign ROI. All tracking link analytics data is available for export in CSV format.
What analytics are available in the unified commerce dashboard?
The unified analytics layer aggregates data from all connected platforms into a single reporting environment. Available reports include total revenue across all platforms with platform-by-platform breakdown, order volume and average order value by platform and time period, gross margin analysis incorporating platform fees and shipping costs where available, customer acquisition and retention metrics including new versus repeat customer ratios, best-selling products across all platforms combined, inventory turnover rates per product and category, marketing channel attribution showing which campaigns and channels drive revenue, email campaign performance, SMS campaign performance, and tracking link attribution analytics. All reports can be filtered by date range, platform, product category, geographic region, and customer segment.
Can I see combined revenue across all platforms in a single report?
Yes. The unified revenue report is one of the core features of the analytics layer, displaying total gross revenue, net revenue after fees, order count, and average order value for all connected platforms in a single view. Revenue is normalized to a single currency using configurable exchange rates for businesses selling across different regional marketplaces with different base currencies. The report supports both absolute revenue figures and trend views showing growth or decline over comparable periods. You can toggle between combined-all-platforms view and a side-by-side platform comparison view within the same report without navigating to a different interface.
How does the platform attribute sales to specific marketing campaigns?
Revenue attribution connects orders to the marketing campaigns that influenced them using tracking link click data and configurable attribution models. When a customer clicks a link from an email campaign, an SMS campaign, or any tracking link and places an order within the attribution window, that order's revenue is assigned to the campaign that generated the click. The platform supports last-click attribution by default, where the most recent campaign interaction before purchase receives full credit, and also supports first-click attribution and linear attribution models that distribute credit across all campaign touchpoints before a purchase. Attribution data is displayed in the marketing performance reports alongside campaign cost data for ROI calculation.
How far back does historical analytics data go?
Historical analytics data is available from the date of the initial historical backfill when you connected each platform. For platforms with full API history access like Shopify and WooCommerce, this means your complete store history is available in the analytics layer from day one. For platforms with limited historical API access like Amazon (two years) and eBay (90 days by default), historical data is available back to the limit of what the API provides at connection time. Going forward from the connection date, all data is captured continuously without expiry. The analytics system does not delete historical data, and date range selectors in the reporting layer can reach back to the earliest available date for each platform.
Can I build custom reports and dashboards?
Yes. The platform includes a custom report builder that allows you to select any metrics and dimensions available in the unified data schema and combine them into custom report views. You can create a report showing revenue from Shopify and Amazon combined filtered to a specific product category over the last 30 days, or a report showing email click rate by customer segment with attributed revenue attached, or any other combination of the available data points. Custom reports can be saved, named, and added to a custom dashboard that you configure as your default home view. Saved reports can be scheduled to run automatically and deliver results via email on a daily, weekly, or monthly basis.
Where is my data stored and how is it secured?
All platform data is stored in infrastructure running on Cloudflare's global network, with data encrypted at rest using AES-256 encryption and in transit using TLS 1.3. Database access is restricted to platform services through network-level access controls, and no data is stored on shared infrastructure with other tenants in the same physical location without encryption isolation. Authentication credentials for connected platforms are encrypted with a separate key management system and are never stored in plaintext. The platform undergoes regular security reviews and penetration testing, and any identified vulnerabilities are remediated on a defined SLA based on severity. All data processing occurs within the jurisdictions specified in the platform's data processing agreement.
Is the platform GDPR compliant and how does it handle data subject requests?
The platform is designed to support GDPR compliance for businesses operating in or selling to customers in the European Union. Data processing activities are documented in a data processing agreement available to all subscribers. Customer personal data is processed only for the purposes defined in the service agreement and is not used for any other purpose including advertising or AI model training. Data subject request handling tools are built into the platform — you can search for a specific customer record, export all data associated with that customer in a portable format, and permanently delete all data associated with that customer in response to erasure requests. These tools are accessible directly in the platform's settings without requiring developer assistance or support tickets.
Does the platform sell or share my data with third parties?
No. Your business data, customer data, order data, and any other data that flows through the platform is used exclusively to provide the service to you. It is not sold to third parties, not shared with advertisers, not used to train external AI models, and not disclosed to any party except as required by law or as necessary to provide the service using contracted infrastructure providers who are bound by data processing agreements. The platform's business model is subscription revenue from you as the operator — there is no advertising model, no data brokerage, and no revenue stream that depends on monetizing your data.
What happens to my data if I cancel my subscription?
Upon cancellation, your account enters a 30-day data retention period during which you can export all your data in standard formats. The platform provides a full data export tool that generates CSV files for orders, customers, products, analytics, and all other data categories. After the 30-day period, all your data is permanently deleted from the platform's infrastructure in accordance with the data deletion policy. Platform authentication credentials for connected stores are revoked immediately upon cancellation, disconnecting the platform from your stores. You can reconnect the platform if you resubscribe within the 30-day window and your historical data will still be available for export.