Selling across multiple platforms is no longer optional for growing brands. Sellufy turns catalog distribution into a managed, automated, and observable process. Product data flows from a single source of truth outward to every connected channel, driven by a background job queue.
Free to start · No implementation fees · No credit card required
Shopify
Native Integration
WooCommerce
Native Integration
Custom Storefront
API-First Channel
Custom Channel
Developer Configurable
Why a Queue
Publishing product data to external platforms involves network calls, API rate limits, data transformations, and error handling. Processing this synchronously in the foreground would block the interface and make large catalog operations impractical.
Jobs run entirely in the background. Users can navigate away, close the browser, or continue working in the catalog while a publish job processes.
Large catalog publishes involving hundreds or thousands of products do not freeze the interface or require the user to wait.
Publishing Queue
Every publish job tracked end to end
Sales channels connected from a single product catalog. Shopify, WooCommerce, Custom Storefronts, and any custom destination, all running from one source of truth.
5
Queue lifecycle steps from trigger to completion
0
Manual reformatting workflows between channels
One Catalog
Multi-channel publishing is not just a technical operation. It is a core business workflow that affects how fast products reach customers, how consistently brand and product information is presented across touchpoints, and how much time catalog teams spend on repetitive manual work.
Sellufy's publishing system is built to handle that workflow reliably at any scale. The queue ensures large operations run without blocking the team. The Jobs Dashboard ensures nothing is missed. AI field matching ensures the right data reaches the right field in every channel.
Queue Lifecycle
Every publish operation in Sellufy follows a consistent lifecycle from trigger to completion.
A user initiates a publish from the product editor, catalog view, or via API. The system validates the request and prepares the job payload.
A job record is created and added to the publishing queue. The job carries all required product data, target channel configuration, and field mappings.
The queue worker picks up the job and begins processing: transforming data, resolving asset URLs, applying field mappings, and sending the payload to the target channel API.
The target channel responds with a success or error. The worker captures the response and updates the job record accordingly.
The job is marked as completed or failed. Results are available in the Jobs Dashboard with a full status log, including any per-product errors or warnings.
Every job that passes through the publishing queue is tracked and surfaced in the Sellufy Jobs Dashboard. This gives teams full observability over the state of every publish operation without needing to check channel platforms directly.
Publishing Channels
Sellufy supports four publishing destinations, covering the most common ecommerce platforms and providing the flexibility to connect to any custom system a business operates.
Native Integration
A native, direct connection to the Shopify Admin API. Full product creation and update support including variant structures, option sets, and custom metafields. Incremental updates push only changed fields on subsequent publishes.
Native Integration
Connects to the WooCommerce REST API to push product data into WordPress-based stores. Handles the full product schema including custom attributes, product categories, tags, gallery images, and variation structures.
API-First Channel
An API-first publishing destination for teams running headless commerce architectures or proprietary storefront systems. Sellufy acts as the product data API layer, delivering clean, structured, and enriched product records on demand.
Developer Configurable
The most flexible publishing destination in Sellufy. Designed for developers and technical teams who need to route product data to any external system, whether an internal tool, marketplace connector, fulfillment platform, or ERP.
Every publishing channel has its own data schema. Shopify expects product data in one structure. WooCommerce expects it in another. A custom storefront or custom channel might have an entirely unique set of field names and data types.
Sellufy's AI engine analyzes both the source attribute definitions and the target channel field schema, then automatically suggests or applies the correct mapping between them.
Sellufy reads the attribute definitions from the PIM catalog, including attribute names, data types, descriptions, and any existing values. It simultaneously reads the target channel field schema.
The AI engine analyzes the semantic meaning of each attribute and each channel field, looking beyond exact name matches to understand intent. An attribute named "Material Composition" will correctly match to a channel field named "fabric_content" or "material_type".
Matched field pairs are applied to the channel configuration. Mappings are presented clearly so users can review, adjust, or override any suggestion before the first publish.
What AI Field Matching Handles
For developers who need to respond to publishing events in real time, Sellufy provides a custom webhook system. Webhooks allow external systems to receive event-driven notifications when key publishing actions occur, enabling downstream automation, custom integrations, and event-based workflows.
Specify the HTTPS endpoint that should receive the event payload. Any publicly accessible endpoint that accepts POST requests is supported.
Choose which events trigger the webhook: job created, job started, job completed, job failed, or all events.
Webhook payloads are delivered as JSON objects containing the event type, timestamp, job ID, channel, and a summary of affected product records.
Each webhook request includes an HMAC signature header so receiving systems can verify that the payload originated from Sellufy and has not been tampered with.
Capability Summary
A consolidated reference for all Multi-Channel Publishing capabilities in Sellufy.
| Capability | Details |
|---|---|
| | Jobs run in the background via a dedicated queue system |
| | Monitor status, progress, and errors for every publish job |
| | Native field mapping and full product sync including variants |
| | Full catalog sync with custom attribute support |
| | API-first channel for headless and proprietary frontends |
| | Developer-configurable output for any external destination |
| | Developer tool for receiving real-time job event payloads |
| | Automatic attribute-to-channel field mapping powered by AI |
| | Full manual control to adjust or override any AI mapping |
One catalog. Every channel. Running in the background. Sellufy's publishing system is built to handle your workflow reliably at any scale.
Free to start · No implementation fees · No credit card required