Integrations: Ecommerce & Accounting

The Integrations hub

Open Brand Settings → Integrations for a card view of every connection. The banner reads "Integrations connect Longboard to your stack." You'll see three cards:

• Shopify — status shows "Connected · N stores published", "Connected", or "Setup needed". Powers the public store locator, storefront events, and product-catalog sync. Click "Manage →" to open the Ecommerce tab.
• Acumatica — status shows "Connected", "Dry run", or "Not connected". Pulls depletion and inventory to tie tastings to sell-through. Click to open the Accounting tab.
• QuickBooks — "Coming soon" placeholder; not clickable.

Connect Shopify (Ecommerce)

Open Brand Settings → Ecommerce. Setup is intentionally one field — the app credentials live on the platform and you never touch them.

1. In Shop domain, enter your store (for example luba-libations-uat.myshopify.com). This is the only editable field; everything else is status and diagnostics.
2. Click "Connect Shopify". A popup opens showing "Preparing Shopify authorization" — keep it open.
3. In the Shopify window, approve Longboard Connect.
4. Back in Longboard, click "Save connection" to persist the shop domain and auto-publish setting. You'll see "Shopify UAT connection saved."

If your browser blocks the popup, the panel shows "Shopify authorization is ready" with an "Open Shopify authorization" link — click it to continue.

### "Connected" vs "linked" — and when to Reconnect

These are two different things, and both show on this screen:

• "Connected" (the badge) means the connection reached "Connected" state — the OAuth token is present and the events schema is verified.
• "linked" means the tenant is associated with a Shopify shop. If you see "No tenant-shop link yet," you still need to install Longboard Connect in Shopify and redeem a one-time link code before commercial publishing.

If the badge changes to "Reconnect needed," the store's authorization expired or the app was uninstalled. Click "Reconnect" to re-run the approval and resume publishing.

### Verify the schema

Use the bottom button row when a probe or publish isn't behaving:

1. Click "Test schema" to probe token and schema access. You'll get "Shopify schema probe passed" or "Shopify schema probe needs attention."
2. If it fails at the schema stage, click "Repair schema" (this creates the missing Longboard event/location fields), then click "Test schema" again.
3. Click "Validate sync" to confirm end-to-end readiness once the state is "Connected."

### Control live publishing

Under the "Publishing" section, the "Live publishing" control has three settings: Off, Auto, and Force on. Auto publishes once the store is verified ready; Force on is an operator override; Off blocks all live writes. The resolved status line tells you exactly what's happening (for example, "Publishing live — Auto, and the store is verified ready."). Turn on "Auto-publish booked events" to publish automatically when an event is booked or a store changes.

Note: storefront events serve live from the Longboard feed — there's no publish step for them. Only the store locator and product catalog involve Shopify writes.

### The public store locator

Two pieces are edited here (these are editable by any write role, not just Super Admin):

• Store locator pin — upload your own map marker (PNG, JPG, or WebP, up to 256 KB; a square 96–128 px image works best), pick an Anchor, then click "Save pin" or "Remove pin". Leave empty to use the default Longboard pin.
• Event image defaults — global and event-type fallback images for published events.

Which stores actually appear on the locator is set elsewhere: the per-location "Store locator" toggle under Retail → Locations. A store only publishes with that toggle on, a complete geocoded address, the store-locator entitlement, and a single live Shopify connection.

Connect the accounting service (Acumatica)

Open Brand Settings → Accounting. The header reads "Acumatica Operations." Secrets are stored write-only in Key Vault.

1. Fill the six Connect fields: Acumatica site URL, Tenant, Integration user, Password, Connected app client ID, and Connected app shared secret.
2. Open "Posting rules — how Longboard writes to Acumatica" and complete the required fields — at minimum Branch, plus Sales order customer (samples account) (shared mode) or Ambassador customer class (extend mode).
3. Set "Connection mode" to "Off — not connected", "Dry-run — validate, send nothing to Acumatica", or "Live — write to Acumatica."
4. Click "Save connection." You'll see "Acumatica connection saved."
5. Click "Test connection." The result reads "Connection test passed" or "Connection test needs attention."

### What it syncs

The connection can write three things to Acumatica, shown in the "What this connection can write" readiness list:

• "Vendor onboarding"
• "AP bill on report approval"
• "Sales order on material request"

Each row shows whether it's currently writing live, dry-run, or off. Capability is set by the platform, not per tenant — you pick the connection mode, but a write only goes live when the mode is Live and the platform has marked that write available.

### Dry-run vs Live

"Live" is not all-or-nothing. Read the per-write "currently…" line to see what's actually writing. Non-production environments cap every write to dry-run as a safety net, even when the mode is set to Live, and any write the platform hasn't marked ready stays in dry-run. Before you can select Live, required posting fields must be filled — if any are missing you'll see "Complete before going Live:" with the list, and the Live option stays disabled until you close the gaps.

To disconnect, click "Disconnect" and confirm "Disconnect the accounting connection?" This deletes the stored credentials but keeps your posting rules, so reconnecting only needs the credentials again.

Who can do this

• Admin / Owner (Super Admin): Full control — connect, reconnect, disconnect, test, repair, and save both Shopify and Acumatica.
• Admin (non-super): Can open the Ecommerce and Accounting tabs and edit the Store locator pin and Event image defaults, but every Connect / Reconnect / Disconnect / Test / Repair / Save action is Super Admin-only and will show a Super Admin-required message.
• Regional / Territory Managers and Viewers: No access. The entire Brand Settings workspace is Admin-only, so these tabs never appear for them.