Channable

Sync product offer data from your warehouse to Channable. Keep stock levels, pricing, and product information up to date across all your connected marketplaces and advertising channels using the Channable REST API.

Prerequisites

• A Channable account with API access enabled
• A Channable API token generated from your account settings
• Your Channable Company ID and Project ID
• At least one project (connected shop or data feed) configured in Channable

Authentication

API Token

1. Sign in to your Channable account at app.channable.com
2. Hover over your account name in the top-right corner to open the dropdown menu
3. Note your Company ID displayed in the dropdown
4. Click Generate API Token (or navigate to account settings)
5. Copy the generated API token
6. Paste the token into the API Token field in Zeotap

Important: Generating a new API token revokes all previously issued tokens for your company. Store the token securely. Rate limits are enforced per company, so regenerating tokens does not reset rate limit counters.

Configuration

Target Settings

Supported Operations

Sync Modes

The Channable Offers API performs upsert operations by matching on the product id field. If an offer with the given ID exists, it is updated; otherwise the behavior depends on your Channable project configuration.

Audience Sync Modes

Channable does not support audience or list membership management. Use sync modes for product data synchronization.

Features

• Field Mapping: Yes
• Schema Introspection: No

Required Mapping Fields

Offers

Orders

Default Destination Fields

How It Works

1. Offer Sync: Zeotap sends product offer updates to the Channable Offers API in batches of up to 50 items per request. Each offer must include id, title, price, and stock fields. The API performs an upsert based on the product ID, updating existing offers or signaling new products to Channable.

2. Order Shipment Updates: For order syncs, Zeotap sends individual shipment update requests per order. Each row must contain an order_id field. Optional fields include tracking_code, transporter, return_tracking_code, and return_transporter.

3. Error Handling: Failed rows are reported with specific error messages from the Channable API. Transient errors (rate limits, server errors) are retried with exponential backoff. The API returns structured error responses with status and message fields.

4. Multi-Channel Distribution: Once offer data reaches Channable, it is automatically distributed to all connected marketplaces (Amazon, eBay, Bol.com, Zalando, etc.) and advertising channels based on your Channable project rules and feed configurations.

Rate Limits

Channable enforces rate limits on a per-company basis using a leaky bucket algorithm:

Zeotap automatically handles rate limiting with exponential backoff and respects the rate limit headers returned by the API.

Best Practices

• Use a dedicated project for each shop or marketplace connection to keep offer data organized
• Map all four required fields (id, title, price, stock) for offer syncs to avoid API validation errors
• Include GTIN/EAN when available to improve product matching on marketplaces
• Schedule syncs during business hours to ensure stock updates propagate to marketplaces before peak shopping periods
• Use discount_price for promotional pricing rather than modifying the base price field
• Monitor sync results for validation errors that may indicate mismatched product IDs

Troubleshooting

Authentication failed: invalid or revoked API token

Verify your API token is correct and has not been regenerated. Generating a new token in Channable automatically revokes all previous tokens. Copy the latest token from your account settings.

Project not found

Verify both the Company ID and Project ID are correct. The Company ID is visible in the account dropdown at app.channable.com. The Project ID can be found in the URL when viewing a project (e.g., app.channable.com/companies/12345/projects/67890).

Offer update rejected: missing required fields

The Channable Offers API requires id, title, price, and stock for each offer. Ensure all four fields are mapped in your field mapping configuration. The id field must match an existing product identifier in your Channable project.

Rate limit exceeded (429 errors)

Zeotap automatically retries rate-limited requests with exponential backoff. If you see persistent rate limit errors, reduce sync frequency or batch size. Rate limits are shared across all API tokens for your company, so check if other integrations are consuming capacity.

Shipment update failed: order not found

Verify the order_id value matches a valid Channable order. Orders may be in different statuses (not_shipped, shipped, cancelled). Only orders in not_shipped or pending_shipment status can receive shipment updates.

Offer data not appearing on marketplaces

After a successful sync to Channable, there may be a delay before data propagates to connected marketplaces. Channable batches updates and sends them to channels on a schedule (typically every 15 minutes). Check the Channable dashboard for feed processing status.

Connection timeout errors

Channable API requests have a 120-second timeout. If you experience timeouts, verify your network connectivity and check the Channable status page for any ongoing service disruptions. Large offer batches are automatically chunked into groups of 50 to stay within API limits.

Invalid price or stock values

Price must be a numeric value and stock must be a non-negative integer. Ensure your source data does not contain currency symbols, commas, or other non-numeric characters in these fields. Use a SQL transformation to clean the data before syncing.