Integrations
The Integrations page is the one place a store sees every outside system it could connect:
wholesale and marketplace channels, Amazon’s Prime checkout, a Shopify stock link, and — for
the stores they were built for — a brand’s own ERP. In the admin it sits under Channels & apps,
beneath Apps, at /settings/integrations.
What the page shows
Section titled “What the page shows”The page has two lists:
| Section | What is in it |
|---|---|
| Connected | Integrations this store has already set up, each with a Connected badge. Shown only when there is at least one. |
| Available integrations | “Integrations that fit this store’s product line and region. Open one to connect it.” |
Open an entry to reach its own screen. Once an integration is connected it also appears in the sidebar under Channels & apps or in the Settings map; until then, this page is the only way in. That is deliberate: a store is not shown a sales channel it has not chosen in every menu it opens.
Why some channels are missing
Section titled “Why some channels are missing”Which integrations a store is offered is the platform’s answer, not a fixed list. A channel built for another market, or a connector built for one brand, is not listed at all on a store it does not fit — it does not appear grayed out.
Two more rules narrow the list:
- Selling channels need CIQRA Commerce. Faire, Temu, Buy with Prime, Shopify stock sync and CavaliERP are Commerce screens. A store on a CIQRA Sites plan reaches the Integrations page itself but is not offered these, because each would open on “Not in your plan”.
- When the check fails, everything is listed. If the admin cannot read which integrations fit this store, the page says “We couldn’t check which integrations fit this store, so every integration is listed.” It errs towards showing you too much rather than hiding a screen you use.
If the available list is empty, the page says “No other integration fits this store right now.”
Who can open it
Section titled “Who can open it”The Integrations page and every integration screen need the settings.manage permission. A team member without it cannot open them.
The integrations, one line each
Section titled “The integrations, one line each”Each has its own article where there is more than one decision to make.
| Integration | What its screen says it does | Article |
|---|---|---|
| Faire wholesale | “Sell wholesale on Faire. Orders placed on Faire take their units out of this store’s stock, and this store’s stock is sent to Faire so retailers only order what you have.” | Faire wholesale |
| Temu | “Sell chosen products on Temu as a US local seller.” | Temu |
| Buy with Prime | “Let shoppers check out with their Amazon Prime account. Amazon takes the payment and ships from its own warehouses; every Prime order lands in this store’s order list.” | Buy with Prime |
| Shopify | “Keeps your Shopify store’s stock equal to this store’s sellable stock” — a stock link, not an import. | Shopify stock sync |
| CavaliERP | “Your ERP link: stock both ways, orders sent to the ERP, the catalog pulled from it, with health checks and run reports.” | Below |
CavaliERP — a connector built for one brand
Section titled “CavaliERP — a connector built for one brand”CavaliERP is a brand’s own ERP. The platform lists it only on the store it applies to, so most
stores will never see it. Its screen lives at /settings/integrations/cavalierp. If it is on your
store, this is what the screen is made of, in its own terms:
- Connection — “The ERP’s API address and the two secrets the ERP team gives you.” The two secrets are the HMAC signing secret and the Webhook Bearer token. Both are write-only: “they are stored encrypted and never shown again.” The ERP API address is restricted: “Only https addresses on app.devcloud.com.tr are accepted.”
- Addresses for the ERP team — the stock webhook, stock snapshot and catalog trigger addresses to hand to the ERP team. They point at your store’s own domain, so a store without a connected domain is told to connect one first.
- Switches — Stock from the ERP, Orders to the ERP, Nightly alignment, Catalog sync, Prices from the ERP and Dry-run. The screen’s rule: “Everything starts off, with dry-run on. Turning something on that writes is confirmed first.”
- Health, Run reports (with Align now and Pull catalog) and Activity — what moved each way, including a Not delivered list you can send again.
🔴 Read the confirmations before you turn a switch on. They are specific: “The ERP’s stock balances will overwrite this store’s stock. Make sure the old site no longer writes stock.” and, for prices, “A catalog pull with price=force will overwrite this store’s prices, including campaign prices.” Dry-run is the switch that makes the others real: while it is on, the screen reports everything and writes nothing.
SETCRM — an app, not an integration
Section titled “SETCRM — an app, not an integration”SETCRM is not on the Integrations page. It is an app: it is installed from Apps, and only
after that does its settings page exist, at /settings/apps/setcrm. A store that has not installed
it gets a page-not-found at that address.
The Apps shelf describes it as: “Sends your form submissions to your SETCRM account and fills your forms’ dealer and fair-staff lists from it.” Its settings page has four parts:
- Connection — which parts of the account are configured. Tokens are never displayed, “only whether each one is present.”
- CRM account — the addresses, tokens and field names the app uses to reach SETCRM, with Save account and Test connection. “The test only reads from your CRM — nothing is created there.”
- Send form submissions to SETCRM — the switch that starts sending. It cannot be turned on until the web-service address, the web-service token and the customer API address are all stored, and the screen asks you to test the saved account first.
- Sent forms — each submission queued for SETCRM, with its status and a Send again action.
🔴 Turning the switch on sends personal data to another system. The confirmation says so in full: “From now on, each new form submission — including the visitor’s name, e-mail address and phone number — will be sent to your SETCRM account. Earlier submissions are not sent.” Check that your privacy notice covers that transfer before you confirm.
What this page does not say
Section titled “What this page does not say”- It does not list every channel the platform knows about. Only those with an admin screen are linked; a channel whose screen is missing is left off rather than linked to an empty page.
- It does not walk through CavaliERP or SETCRM field by field. Both are connectors set up together with the vendor’s own team, who supply the values the forms ask for.