Set up CMRE

1. Put the code in the Code Vault 5 min

1. Unzip cmre.zip on your computer.
2. Open Code Vault › New repository. Name cmreCopy, choose Private, click Create repository.
3. On the new repository page click uploading an existing file.
4. Open the unzipped cmre folder, select everything inside it (the database, public, src and tests folders and the files beside them) and drag it onto the page. Click Commit changes.

Back to steps

2. Create the Data Vault 10 min

1. Open Data Vault › Projects → New project. Name cmreCopy, a region near your customers, and a strong database password saved in your password manager. Click Create new project and wait for it to finish.
2. Left menu → SQL Editor → New query.
3. In your Code Vault repository open database/migrations/0001_foundation.sql, click Copy raw file (the two-squares icon above the code), paste it into the SQL Editor and click Run. It should end with Success.
4. New query, same for 0002_growth_and_customers.sql. New query, same for 0003_views_and_setup.sql. Run the three in this order, each once.
5. Project Settings (gear) → Data API: copy the Project URL.
6. Project Settings → API Keys: copy the Publishable key (starts sb_publishable_) and create or reveal a Secret key (starts sb_secret_). Older projects may show only the legacy anon and service_role keys; those work too, in the same places.

Back to steps

3. Deploy on the Edge Runtime 10 min

1. Open Edge Runtime › Applications → Create.
2. Choose Import a repository. Connect the Code Vault when asked and allow access to cmre.
3. Select cmre. Leave the build command empty; the deploy command is Copy (the Edge Runtime runs it for you). Click Create and deploy.
4. Note the address shown, for example https://cmre.<your-subdomain>.. That is your app.
5. Recommended: Edge Runtime › Plans → the paid plan. The Tuesday KPI refresh makes more outside calls in one run than the free plan allows.

Back to steps

4. Add the settings and secrets 5 min

Edge Runtime → your cmre application → Settings → Variables and Secrets → Add. Add each row as type Secret.

The key is made in your browser with a secure random generator and never sent anywhere. Keep a copy in your password manager: if it is lost, the Commerce Hub access token has to be saved again.

1. Click Deploy (or Save and deploy).
2. Settings → Trigger events: confirm two cron triggers, */15 * * * * and 5 * * * *. They come from the code.

Back to steps

5. Point sign-in at your app 2 min

1. Data Vault → Authentication → URL Configuration.
2. Site URL = your app address from step 3.
3. Redirect URLs → Add URL: the same address followed by /**Copy. Save.
4. Optional: Authentication → Emails → custom SMTP, so sign-up emails come from your domain (the built-in sender is rate-limited).

Back to steps

6. Create your account and workspace 5 min

1. Open your app address → Create account. Confirm the email, then sign in.
2. Create a workspace named Arctic BarrierCopy with the template Winter retail 2026 (or Standard for another brand). You become its owner. The three launch checklists (31 items), six email flows, seven experiments, the collections, the advertised codes to audit, a basket at your price points, wholesale terms and the first content ideas for every channel are filled in.
3. You land on Launch. Each checklist item says which page or outside tool it happens in.
4. Settings → Team: invite the CMO, operator, merchandising lead and admin by email. They join when they sign up or sign in with that email.

Back to steps

7. Connect the Social Relay and every channel 15 min

In the Social Relay dashboard, then on Settings → Connections in CMRE.

1. Social Relay dashboard: create a profile for the brand with the store's time zone. Connect every network the brand uses to that profile. Start with the six CMRE turns on for this template: Pin board, Short-video, Photo, Community, Business listing and Professional (for corporate gifts). Connect others when you are ready to post there; they stay off in CMRE until you switch them on. The provider table names each network.
2. Turn on the Social Relay's Inbox add-on so the Social Scout can read comments and messages.
3. In CMRE: Load Social Relay profiles → choose it → Use this profile.
4. Type the store admin domain (Commerce Hub admin → Settings → Domains) → Connect store via Social Relay → approve in the tab that opens.
5. Sync accounts from Social Relay, then tick Verified for each brand handle after checking it on screen.
6. Load store blogs → choose the blog → Use this blog.
7. 6. Channel settings: check the six ticked Active channels; Load boards and pick the default Pin board board; choose Video visibility and Short-video audience; enter a Forum group or Community server channel id only if you post there. Click Save channel settings.

Back to steps

8. Connect the Commerce Hub store 10 min

CMRE reads orders, stock and customers. With your approval it writes tier tags, discounts, customer segments, marketing report entries, bundle products and VIP gift cards, and it can add a storefront event pixel. The Commerce Hub now issues this access through an app made in its Dev Dashboard; CMRE renews the access itself every day.

1. In CMRE, open Settings → Connections → 5. Connect the Commerce Hub store. Keep this tab open: it shows three values with Copy buttons (App URL, Allowed redirection URL, Access scopes).
2. Open the Commerce Hub Dev Dashboard and sign in with the store owner's account. Click Create app → Start from Dev Dashboard, name it CMRECopy and click Create.
3. In the app's version settings, paste the App URL and the Allowed redirection URL from CMRE, and paste the scopes into Scopes: read_orders,read_products,read_inventory,read_customers,write_customers,write_discounts,write_marketing_events,write_products,write_gift_cards,write_pixels,read_customer_eventsCopy. Click Release.
4. In the same version settings, under Compliance webhooks, paste this address for all three privacy topics (customer data request, customer erasure, shop erasure): https://cmre.io/api/commerce/webhooksCopy. CMRE checks each request's signature with your app's client secret before acting.
5. Install the app on your store. If the Dev Dashboard asks how to distribute it, choose Custom distribution, enter your store domain, and open the install link it gives you.
6. In the app's Settings, copy the Client ID and Client secret.
7. Back in CMRE: paste the store domain, Client ID and Client secret → Connect store.
   • If the store and the app are in the same organization, it connects at once.
   • Otherwise CMRE shows Approve on the store: click it, approve, and you return to CMRE connected.
8. Catalog & offers → Sync products from the store, star 4 to 6 hero products and enter unit costs.
9. Customers → Refresh from Commerce Hub. KPIs, tiers, buying plan, cross-sell, returns and the order-size report appear. It refreshes itself every Tuesday at 8 AM.

Back to steps

9. Turn on the revenue features 20 min

1. Settings → Workspace → Order size and reviews: confirm Free shipping from 35Copy, and paste your Review link (the page of your reviews app, starting https://). Save.
2. Install a reviews app from the Commerce Hub app store so product pages show reviews; then build the Review request flow in Commerce Mail (Catalog & offers → Email flows lists its tests).
3. Add a signup pop-up (Commerce Hub theme editor or Commerce Mail forms) offering the welcome code ABWELCOME10Copy, and consider retiring the public SP10 code once it runs.
4. Wholesale: tick Wholesale page on, check the minimum units, discount and terms, and Save. Copy the trade page link; trade buyers in Social leads get a Copy trade link button.
5. Catalog & offers → Products → Feed check: fix the listed products (hero products first) in the Commerce Hub product editor and sync again. Then, in the Commerce Hub admin, add the free search listings sales channel and the Pin board sales channel so your products appear in shopping results and on pins.
6. Settings → Workspace → Order size and reviews: confirm the standard and express cut-off dates with your carrier (template: 2026-12-15Copy and 2026-12-19Copy). In the Commerce Hub admin, turn on digital gift cards.
7. Catalog & offers → Order size: read the free-shipping recommendation, add the cart message, and save the first two bundle ideas. The owner or CMO approves them; build them in the store; mark them live.

Back to steps

10. Connect the CMRE Assistant 3 min

1. In the app: Settings → Agents & CMRE Assistant. Name the key, leave Allow drafts off for a read-only start, click Create key for CMRE Assistant. Copy what is shown; the key is displayed once.
2. Assistant workspace: Settings › Connectors → Add custom connector. Name CMRECopy, URL = the private connector URL. Treat that URL like a password. Help: custom connectors
3. Developer assistant or another Agent Bridge client: use the project config shown with the key (server /bridge with an Authorization: Bearer header).
4. Ask: "How did last week go and what is the one change?", "Is anything going out this week that will be blocked?", "Who in our comments is asking about wholesale?", "Draft a gift post for the beret".

Back to steps

11. Updating later

• Code changes: edit or upload files in the Code Vault repository. The Edge Runtime redeploys within a minute or two (application → Deployments).
• Database changes: new files in database/migrations are run once each in the SQL Editor, in number order.
• Logs: application → Observability shows API errors and scheduled job runs.
• Rotate a secret: change it under Variables and Secrets and deploy. A new ENCRYPTION_KEY means clicking Connect store again.
• After four weeks: open Numbers → Channels. Post more where it says Grow, switch off what says Pause, and turn on one new channel at a time.
• Coming from v2.2: v3.5 is a clean install (33 tables). Create a new Data Vault project and follow steps 2 to 10; keep v2 running until L1 passes. Re-enter unit costs, offers and creators by hand; tiers, KPIs, order size and quick wins rebuild from the Commerce Hub on the first refresh.

Back to steps

Provider table

CMRE uses CloudOneSoftware-native names everywhere. This is the only place the services behind those names are listed; the links in the steps above are filled in from this table.