Preset Bridge Ecommerce Setup

Choose the right setup

Preset Bridge accepts orders from Shopify, WooCommerce and any platform that can send signed JSON directly or through a small adapter.

Store	Order intake	Cortex Cloud username	Store completion
Shopify	Native Order payment webhook	Cart or order attribute	Custom app or callback receiver required
WooCommerce	Preset Bridge plugin	Checkout field supplied by the plugin	Automatic through the plugin
Other platforms	Generic signed webhook or adapter	Field supplied by the store	Signed callback handled by the adapter

Native and compatible are different. Shopify has native inbound order verification. WooCommerce has a packaged two-way plugin. Other platforms use the documented generic webhook contract until a dedicated connector is available.

Setup shared by every store

Save and validate the Cortex Cloud credentials for the account that owns the assets.
Create an active API token for the store.
Open Integrations → Store integrations and add the appropriate provider.
Set the username field key. ndsp_username is the recommended default.
Add one item mapping for every preset or capture sold by the store.
Configure the store or adapter to send paid orders to the integration webhook URL.
Run a real test order before making products public.

Map products to Cortex Cloud assets

Each mapping connects a store identifier to one preset or capture. SKU matching is usually the clearest choice because it works across product and theme changes.

Match type	Use it for	Example
`sku`	A stable product or variation SKU	`STORM-LEAD-V2`
`productId`	The platform product ID	`7891234567890`
`variantId`	A platform variant ID	`43210987654321`
`title`	A case-insensitive title match	`Storm Drive Lead Preset`

Example mapping

{
  "matchType": "sku",
  "externalRef": "STORM-LEAD-V2",
  "resourceType": "preset",
  "resourceId": "abc123-preset-id"
}

Orders in, delivery results out

The inbound integration accepts and verifies an order, then queues the mapped assets for delivery. An outbound webhook subscription can report each delivery state to the store or its adapter.

The store sends a paid order with a stable order ID, Cortex Cloud username and product identifiers.
Preset Bridge verifies the signature, rejects duplicates and queues the matched assets.
Preset Bridge follows the customer, waits for a follow-back when required, then shares the assets.
A delivery.completed callback tells the store that fulfilment succeeded.
If the order is invalid, the merchant stops retries and sends a delivery.invalidated callback.

See Webhooks for request signatures, response codes and the outbound event payload.

Delivery states

Status	Meaning
`queued`	The order was accepted and is waiting to be processed.
`running`	Preset Bridge is working on the delivery.
`retry_scheduled`	Preset Bridge will try again, including while waiting for a follow-back.
`action_required`	The merchant must correct the username, credentials, credits or mapping.
`completed`	All mapped assets were shared successfully.
`failed_permanent`	The delivery cannot continue without a new order or configuration change.
`invalidated`	The merchant stopped the delivery and recorded why the order should not be fulfilled.
`ignored`	The order status was not accepted by the integration.
`duplicate`	The same webhook event was already accepted.

Go-live checklist

The store collects a required Cortex Cloud username for every eligible order.
Every sellable SKU or product ID has one correct mapping.
A paid test order appears once in Preset Bridge.
The test customer receives the correct assets.
The store or adapter receives delivery.completed when it depends on a callback.
Store staff know where to find and retry deliveries that need attention.
The Preset Bridge credit balance can cover live orders.

Email contact@presetbridge.com if you need help connecting a platform not covered by a dedicated guide. Include the platform name and its webhook documentation, but never send passwords or secrets by email.

Ecommerce setup