Ecommerce adapter

autonnel does not have a built-in product catalog or order management system. It reads product data from an external platform and pushes completed orders back to it after payment is captured. You choose one ecommerce adapter per deployment.

Navigate to the setting

Go to Settings → Ecommerce. The tab shows the currently active provider and lets you enter or update credentials.

Configuration shape

The adapter configuration is stored under the ecommerce.config runtime setting. The value is a JSON object:

{
  "provider": "shopify",
  "credentials": { },
  "isActive": true
}

The credentials shape differs per provider (see below). isActive: false disables the adapter without deleting credentials.

Provider credentials

Shopify

{
  "provider": "shopify",
  "credentials": {
    "shopDomain": "mystore.myshopify.com",
    "accessToken": "shpat_xxxx"
  },
  "isActive": true
}

Field	Where to find it
shopDomain	Your .myshopify.com subdomain
accessToken	Shopify Admin → Settings → Apps → Develop apps → your app → Admin API access token

The adapter reads products and pushes orders to Shopify using the Admin API.

WooCommerce

{
  "provider": "woocommerce",
  "credentials": {
    "siteUrl": "https://yourstore.com",
    "consumerKey": "ck_xxxx",
    "consumerSecret": "cs_xxxx"
  },
  "isActive": true
}

Field	Where to find it
siteUrl	Your WordPress site root URL
consumerKey	WooCommerce → Settings → Advanced → REST API → Add key
consumerSecret	Generated alongside the consumer key

The adapter uses WooCommerce REST API v3. Authentication uses the consumer key and secret.

Picocart

Picocart is an open-source headless commerce platform that is API-compatible with Shopify.

{
  "provider": "picocart",
  "credentials": {
    "baseUrl": "https://your-picocart-instance.com",
    "apiKey": "your-picocart-api-key",
    "apiVersion": "2024-01"
  },
  "isActive": true
}

Test the connection

After entering credentials, click Test connection. This fetches one product from the configured provider to verify that the credentials work and the API is reachable. A successful test does not guarantee all product data will sync correctly, but it confirms basic connectivity and authentication.

What autonnel reads vs. writes

autonnel uses the ecommerce adapter for two things only:

• Read: product catalog (list products, get by ID, get variants, search)
• Write: push a completed order after payment is captured

Everything else — recall emails, shipping rate display, tax calculation, coupon validation, email templates — is handled entirely by autonnel using its own settings. The ecommerce platform’s tax engine, shipping rules, discount codes, and email notifications are not read or activated, even if you have them configured on the platform side.

Caveats

• Platform-only handles products and orders. All other commerce logic (recall, tax, shipping rate calculation, coupons, email templates) is autonnel-side and does not inherit from the platform’s settings. Shopify’s tax engine, for example, is not used by autonnel even if you have Shopify configured.
• Switching providers mid-operation breaks existing order references. Orders in PENDING or PAID state have an externalId pointing to the old platform. If you switch providers, those references become invalid and fulfillment sync will fail for those orders. Plan any provider switch at a natural break point (e.g., end of a business day with no open orders).
• autonnel pushes orders to the platform after payment is captured, not at checkout initiation. If the push fails, the order is saved in autonnel but may be missing from the platform. Check the order’s externalId field to confirm the push succeeded.

Related

• Picocart — open-source headless commerce compatible with Shopify APIs
• Quick start — initial ecommerce configuration during setup
• Settings → Coupons — managing coupon codes (autonnel-side, not platform-side)