Change your store's settings

The Settings section of the Commerce tab holds how the store is set up: its details, what checkout asks of shoppers, returns and policies, when orders go to your providers and how often the store pays out. It also holds the publishable keys and sales channels your storefront uses. Each card saves on its own.

• You need the Admin or Owner role to change settings. Other members see each card's values, with a note that the page is read-only for them.
• Two parts of this section have pages of their own: the merchant profile in Take your store live, and the providers in Send orders to a fulfilment provider.

1. In the dashboard, open the organization, then Commerce, then Settings.
2. Change the fields on a card. The card's footer counts the changes to save.
3. Select Save changes on that card, or Discard to put its fields back.

An optional field you empty goes back to its default when you save.

Store name

Shoppers see it in the emails the store sends them.

Support email

The store's emails tell shoppers to write to this address.

Storefront address

Order links in the store's emails open on it, and PayPal sends shoppers back to it after they pay. It starts with https://.

Sites that may call the Store API

One site per line, up to 20, each a scheme and a host such as https://shop.example.com. With none listed, any site can call the Store API from a browser. With a list, only those sites can, and the card warns you when the storefront's own site is missing from it.

Default currency

Prices are in it wherever no region applies, since each region sells in its own currency. The import form starts on it.

Other currencies

Where no region applies, a storefront can ask for prices in these, and an import can price in them. Once you remove one, a storefront that asks for it where no region applies is refused. A region that sells in it keeps selling in it.

Default language and Other languages

Your storefront reads the languages from the Store API and starts in the default one. Each order keeps the language its cart was in. Other languages are tags such as en-GB or de, separated by commas.

Guest checkout

On by default: shoppers can order without an account. Turned off, they sign in first.

Terms of sale

With a page set, checkout asks shoppers to accept it, and each order records when they did.

Terms version

Up to 40 characters, recorded on each order with the acceptance. Change it when the terms change.

Privacy policy

Your storefront reads it from the Store API, to link to it.

Order links work for

How long the order link in the store's emails opens the order without signing in: from 1 to 3,650 days, and 90 days unless set.

High-value first order

A first order from an email address above this total is one risk signal. Two signals, or a high rating from the payment provider, hold the order until you release it in Orders. The default is 500.00 in the store's default currency, and the same number counts in every currency.

Return window

How long after delivery shoppers can ask for a return from your storefront, or after shipping when there is no delivery date: from 0 to 3,650 days, and 30 days unless set. 0 turns shopper requests off, and you can still open returns yourself.

Refund policy and Shipping policy

Up to 5,000 characters each. Coritan sends them with your evidence when a shopper disputes a payment.

Send orders to webhook providers on their own

On by default. A placed order goes to its provider after the wait below, or after the provider's own wait if that is longer. Turned off, you send each order from its page.

Wait before sending

The least time any provider waits after an order is placed, so a mistake can still be put right: up to 10,080 minutes, which is a week. Unset, there is no wait.

Pay out

Daily, Weekly or Monthly, and weekly unless set. Days start at midnight, weeks on Monday and months on the 1st, all in UTC. Payouts shows the minimum for each currency, and lets you ask for a payout sooner.

A storefront sends a publishable key with every Store API call. A key is safe in browser code, and a test key places test orders.

1. On the Publishable keys card, select New key….
2. Enter a Label of up to 100 characters. It is for you to tell keys apart, and storefronts never see it.
3. Choose the Mode. Test places test orders. Live takes real orders once the store is live, and until then the Store API refuses it.
4. Under Sells through, tick the sales channels the key sells through. With none ticked, it sells through the default channel, and follows the default if another channel becomes it.
5. Select Create key.

The dialog shows the key, the header to send it in (x-publishable-api-key) and the Store API address. Select Done. The key stays in the list, where Copy key copies it. Send the publishable key shows how a storefront uses it. The JavaScript SDK takes the key as publishableKey and sends it with every request.

1. On the Publishable keys card, select Revoke… on the key's row.
2. Type the key's label, then select Revoke key.

Storefronts that send the key stop working within 15 seconds, so create another key first if a storefront still uses it. The key stays in the list, marked Revoked.

A sales channel is where the store sells. A key sells through its channels, and a product is listed in the channels it is added to under Listing in Products. A store has at most 50 channels.

To add one:

1. On the Sales channels card, select New channel….
2. Enter a Name of up to 100 characters. Storefronts can read it from the Store API.
3. Optionally, enter a Description of up to 500 characters, for members only.
4. Under Sells from, tick the stock locations whose stock the channel sells. With none ticked, it sells the stock of every location that is turned on.
5. Select Create channel.

The menu on a channel's row holds the rest:

Edit channel…

Change the name, the description or where it sells from, then select Save channel.

Make default

Keys that name no channel sell through the default. When some do, the dashboard asks you to confirm, because their storefronts then show the new default's products. A channel that is turned off must be turned on first.

Turn off… and Turn on

Storefronts whose keys sell through a channel that is turned off show none of its products until it is turned on again. Its products and keys stay as they are.

Delete channel…

Type the channel's name, then select Delete channel. Its products leave it and its locations are unlinked. A key that sells only through it shows no products, and needs replacing with a new key.

The default channel cannot be turned off or deleted. Make another channel the default first.

Each card confirms what it saved, such as "Checkout settings saved.", and shows the new values. A new key or channel appears in its list at once.

The storefront's pages cannot call the Store API

Sites that may call the Store API lists sites, and the storefront's own site is not one of them. Add it, or empty the list.

The Store API refuses a live key with store_not_live

The store is still in test mode. Use a test key until staff take it live, as Take your store live explains.

Make default cannot be selected

The channel is turned off. Turn it on first.

Turn off… or Delete channel… cannot be selected

The channel is the default. Make another channel the default first.

A card says it could not save

The alert or the field gives the reason. Fix the value, then select Save changes again.

• Run your store from the Commerce tab
• Set up regions and shipping
• Build a checkout with the Store API
• Build a storefront with the JavaScript SDK

PATCH https://api.coritan.com/api/v1/orgs/{org_slug}/commerce/store changes the store's details, and takes these keys under settings: guest_checkout, terms_url, terms_version, privacy_url, order_access_days, risk_high_value, returns_window_days, refund_policy, shipping_policy, auto_dispatch, release_delay_minutes and payout_schedule. A setting sent as null goes back to its default. Change the store's settings and Create publishable keys and sales channels have the details.

curl -X PATCH "https://api.coritan.com/api/v1/orgs/acme/commerce/store" \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"settings": {"guest_checkout": false, "returns_window_days": 14}}'