Acumatica × Shopify, live in production

Plekify for Acumatica

Talk to us See it live

Keep Acumatica. Add Plekify.

Plekify is the Shopify commerce layer on top of Acumatica — one dashboard where stock, pricing, and orders meet. No rip-and-replace. No fabricated numbers.

ERP-in, storefront-out

Your Acumatica data doesn't get guessed at — it gets cached, then written.

Stock items, per-warehouse availability, price books, and customer price classes are pulled from Acumatica and cached first. From that cache, Plekify writes products, variants, inventory, collections, filters, and metaobjects to Shopify.

Fail-closed, always. No cache, no write. If Acumatica hasn't confirmed a number, Shopify never shows one. Your storefront can be stale for a minute — it is never wrong.

A customer hub your trade customers actually use

Trade accounts don't want a portal. They want their invoices.

Invoices — per-invoice PDF download, on demand
PODs — full delivery detail, matched to the order
Statements — full account breakdown
Cases — credits, returns, POD queries, pricing queries, general support, with notes and attachments

Every screen is read live from Acumatica through a cache, and every screen is scoped to that one customer. Buyers sign in through Shopify session tokens (ExchangeGrant, renewed as an offline token) — no separate password to lose.

Approvals done right

A trade application shouldn't sit in an inbox.

Live today: the approval queue and Shopify account provisioning. Approve an application and Plekify builds the Shopify company and location automatically. The workflow is re-entrant — if a step fails, it resumes from where it stopped, not from zero.

Binding that company to its Acumatica customer record, stamping the correct pricing tier, and wiring net-terms payment customisation are on the roadmap — proposed, not shipped. Until that ships, the system fails closed rather than guessing at a tier.

Orders land back in Acumatica

Write-back is built and verified by test. It turns on with your first account's go-live.

Shopify orders map to Acumatica sales orders. The push is idempotent — a row already verified in Acumatica refuses to be pushed twice. Every write is checked against the ERP after the fact, not assumed. Full audit trail at every step, before it ever touches a live account.

The dashboard

One place for staff to see what's actually happening, gated behind Microsoft Entra ID.

/overview · /inventory · /price-sync · /tiers · /sales · /loyalty · /approvals · /ops

On the storefront: Market Pulse, built from metaobjects and served through a public app-proxy feed — live signal, not a static banner.

Built for hard networks

Distributors don't run on fibre in a fresh office park. Warehouses, branch offices, and field connections drop out.

Plekify's connector is resilient by design — built to survive restrictive networks, not just fast ones. Cache-first reads mean the storefront keeps serving numbers even when the link to Acumatica is having a bad day.

In production today — and what's next

Live, in production, right now, for a South African industrial-safety and tyre distributor on Acumatica, delivered with an ERP implementation partner:

3,323-item catalogue synced from Acumatica; ~500 curated for launch
957 customers live in the hub — 513 wholesale, 444 fleet
5 branches, 8 price classes, 3,294 price rows, 3,536 stock levels, all cache-fed
19,179 sales lines analysed to build the pricing and tier logic

Roadmap — proposed, not shipped:

Binding the Acumatica customer record, tier stamping, and net-terms payment customisation on approval
Tier-pricing loop completion
Offline-first mobile app (React Native): catalogue opens with no signal, cached prices stamped with last-sync time, orders queue and send when back online
Checkout on terms walked end-to-end, tier discount auto-applied
Listings agent-readable via the platform's UCP manifest — roadmap