Merchants

In SCAYLE, a merchant is the seller toward the end customer. Merchants influence assortment, prices, stocks, and fulfillment setup.

When you create a merchant, you define its name and reference key. You can also set a priority. After that, you can configure contacts, return addresses, countries, carriers, and warehouses.

How these pages differ

Use this page for concepts and setup decisions.

Use Merchant Allocation when you need the workflow for making a merchant sellable in a shop country.

Use Interact with Admin API in Multi-Merchant Setup when you need request examples for assortments, prices, or stocks in a multi-merchant setup.

Single-merchant vs. multi-merchant

Single-merchant setup

Use this when one merchant sells the catalog in a shop country.

If you omit merchantReferenceKey, SCAYLE uses the default merchant.

Warehouse assignment is simpler. SCAYLE can create the warehouse on first use and connect it to the default merchant.

Multi-merchant setup

Use this when several merchants can sell the same products.

In this setup, merchant allocation becomes part of the rollout. You need to connect warehouses, include the merchant in the shop country assortment, and provide merchant-specific prices or stocks where required.

Use merchantReferenceKey explicitly. This keeps price and stock ownership unambiguous.

Default merchant

The default merchant is the merchant created first.

SCAYLE uses it whenever merchant context is optional and no merchantReferenceKey is sent.

Priority

Priority matters when several merchants sell the same variant.

SCAYLE picks the merchant with the highest priority whose stock is available in at least one connected warehouse. If that merchant has no sellable stock, SCAYLE falls back to the next one.

The default priority is 0.

Carriers

A carrier delivers goods to customers.

After you configure carriers, you can assign them to merchants per country. This lets one merchant ship with different carriers in different markets.

Warehouses

Warehouses store sellable stock.

One merchant can use multiple warehouses. Multiple merchants can also share the same warehouse.

The warehouse flow depends on your setup:

• In a single-merchant setup, warehouse assignment is handled through the default merchant path.
• In a multi-merchant setup, you should treat warehouse allocation as an explicit setup step.

For the exact rollout sequence, see Merchant Allocation.

Product assortment

Assortment controls which products and variants are sellable in a shop country.

You can include or exclude merchants as part of the assortment. In multi-merchant setups, this is the step that makes a merchant’s catalog available in the shop.

Prices

Prices are stored on variant level.

You can define merchant-specific prices by sending merchantReferenceKey.

In multi-merchant setups, use merchantReferenceKey explicitly.

Stocks

Stocks describe how many units are available in a warehouse.

You can create merchant-specific stocks by sending merchantReferenceKey.

In multi-merchant setups, make sure warehouse allocation is complete before you send stock updates.