Blog Details

Wutt connects to Magento (Adobe Commerce), BigCommerce, PrestaShop, OpenCart, and Squarespace Commerce through a unified Commerce workspace, so a single agent inbox can serve any combination of stores. The connection logic is similar across platforms, but the auth flow and the field mapping differ. This guide gives you a per-platform cheat sheet and the code to keep catalogs in sync.

Step 1 — Pick a provider in Commerce

Go to Commerce → Providers → Add provider. Each provider has its own auth screen, but the same five outcomes are always wanted:

1. Successful connection test.
2. Products pulled and indexed.
3. Orders pulled for the last 90 days.
4. Webhook inbound for new orders and cart events.
5. Revenue attribution enabled.

Magento / Adobe Commerce

Create an Integration in Magento admin (System → Extensions → Integrations) with these ACL resources:

Catalog -> Products (Read/Write)
Sales -> Orders (Read)
Customers -> All Customers (Read)
Stores -> Currency (Read)

Paste the consumer key, consumer secret, access token, and access token secret into Wutt. For multi-store setups, include the store code field.

Run a one-time backfill:

php artisan commerce:sync magento --products --orders --days=180 --store=sa_en

BigCommerce

In BigCommerce, go to Advanced Settings → API Accounts → Create API Account and pick the Storefront API + REST API scopes:

Products: read-only
Orders: read-only
Customers: read-only
Store content: read-only

Copy the Client ID, Access Token, and Store Hash into Wutt. Wutt auto-detects the channel (e.g. bigcommerce://store-hash/v3) and runs the sync.

PrestaShop

PrestaShop uses the Webservice key. Enable it under Advanced Parameters → Webservice, generate a key with these permissions:

products       (GET)
categories     (GET)
orders         (GET, POST)
customers      (GET)
states         (GET)

Use the Wutt PrestaShop embed module for a one-click install from the Addons Marketplace, or paste the key into Wutt’s Commerce → PrestaShop screen manually.

php artisan commerce:sync prestashop --products --orders --days=90

OpenCart

OpenCart 3.x and 4.x are both supported. Generate an API user from System → Users → API with the IP whitelist set to the Wutt server’s outbound IP. Enable:

catalog/product      (read/write)
catalog/category     (read)
sale/order           (read)
sale/customer        (read)
setting/store        (read)

OpenCart 2.x stores can use the legacy JSON endpoint; enable the “Use legacy endpoint” checkbox in Wutt.

Squarespace Commerce

Squarespace uses OAuth. In Wutt, click Connect Squarespace — a popup walks you through granting the commerce.products.read, commerce.orders.read, and profile.read scopes. The access token is stored encrypted.

Note: Squarespace does not expose a public cart or checkout API, so Wutt syncs products and orders but generates checkout links rather than full in-chat checkouts for Squarespace.

Unified inbox across all five

Once connected, every order, customer, and product shows up in the Wutt Inbox right panel. The store name appears as a tag, so agents can filter:

store:magento      -> 9 active conversations
store:bigcommerce  -> 4 active conversations
store:prestashop   -> 3 active conversations
store:opencart     -> 1 active conversation
store:squarespace  -> 0 active conversations

One cron to rule them all

Schedule a single cron to keep every store in sync. Place this in routes/console.php:

Schedule::command('commerce:sync all --days=1')
    ->everyFiveMinutes()
    ->withoutOverlapping()
    ->onOneServer();

Common gotchas

• Magento: throttle the API. Wutt defaults to 20 req/min; raise it only if your host can handle the load.
• BigCommerce: if you have more than 50,000 SKUs, run the sync in background mode and watch the Activity tab.
• PrestaShop: enable Enable CGI mode in your PHP-FPM pool so the long sync requests do not time out.
• OpenCart: 2.x stores do not emit order updated webhooks — Wutt polls every 5 minutes instead.
• Squarespace: there is no native cart-recovery hook — schedule a daily export and trigger a template send from the list.

Revenue attribution across stores

Open Reports → Revenue attribution → Group by store to see which platform is producing which WhatsApp-driven sales. Most multi-store operators discover that one platform quietly drives 70% of WhatsApp revenue and deserves the most template work.