Fulfillment Nutra
Connect Custom API / Headless to private-label supplement fulfillment with APIs/webhooks, SKU mapping, paid-order validation, tracking and recovery — Shopify…
Direct answer
Custom API / Headless can connect to the Channel Hub when official or documented access, the source account or system, permissions and required data are available. Shopify is not required: the data contract, authentication, idempotency, order events and tracking feedback must be validated. Shopify is not a dependency: activation follows the real protocol and requires an end-to-end test without a real customer order.
Every order coming from Custom API / Headless keeps a stable external identifier and idempotency key. A replayed webhook or API call must never create a second order. This also protects retries after timeouts or network errors.
Order created, payment confirmed, preparation, shipment, cancellation and refund remain separate facts. The Custom API / Headless connection must translate those states without treating a commercial status change as automatic proof of a logistics event.
Fulfillment Nutra can receive orders from a documented channel without forcing Shopify in the middle. For Custom API / Headless, feasibility depends on the protocol actually available: API, webhook, IPN, export or secure automation. The source system can remain the owner of checkout and customer relationship.
Fulfillment must not be released from an ambiguous event. The Custom API / Headless connection defines which event or authority proves that the order is actually payable or paid and how pending, authorized, failed, cancelled or refunded states are handled.
A mature integration does not stop at order import. When Custom API / Headless supports it, tracking and useful statuses flow back to the channel. Invalid address, unknown SKU, unavailable inventory or carrier errors should create explicit states rather than silence.
API access, catalog visibility and channel authorization are three separate things. Custom API / Headless may apply its own rules while the product, label, claims and destination remain subject to market obligations.
Related guides
FAQ
The displayed status is “Assessment — direct API”. General feasibility does not prove that an account or production flow is active.
At minimum: order creation, confirmed payment, cancellation or refund, and tracking feedback according to available APIs.
Only when the account, API and inventory model support a tested flow. Real-time inventory is not promised before that proof.
Custom API / Headless applies its own rules to the seller, country, product, label and claims.
Every event keeps an external identifier and idempotency key; a retry returns the same logical result.
Create your workspace to review the catalog and confirm the products, markets and capabilities that are actually available.