Integrations

Two ways the viewer plugs into your stack.

An ERP overlay reads live stock and price from your system of record (Odoo today) and shows the numbers on every part. An ecommerce embed posts add-to-cart events from the viewer up to your existing storefront — Shopify, WooCommerce or custom. The viewer never owns the cart; your checkout does.

Upload a STEP file View the embed snippet

Backed by Pogodan's integrations practice — see below.

CART empty Checkout →

● LIVE DEMO STEP → glTF · 2.1s

live · SO-ARM100 robot arm · demo.quidities.com

Track A · ERP

Live stock and price from your ERP.

The viewer's erp-client calls into your ERP for the SKUs on a BOM and overlays the numbers on each part card. Falls back to a static erp.json snapshot when the connection isn't reachable, so an unhealthy ERP doesn't break the viewer experience.

VIEWER

Quidities

· 3D + BOM overlay

· Live stock + price per SKU

· postMessage add-to-cart

←

JSON-RPC over HTTPS · read-only

YOUR ERP

Odoo 18 / Online

· product.template

list_price

qty_available

READ · LIVE

list_price, qty_available by SKU

WRITE · ROADMAP

sale.order writes scoped per-deployment

Where we are with Odoo specifically

Pogodan has Odoo integration experience and the JSON-RPC plumbing in the viewer works today. Quidities itself is a new build, so the Odoo-specific story is a scorecard, not a packaged-module pitch:

✓

Live stock & price overlay

JSON-RPC client reads list_price + qty_available by SKU from Odoo 18 / Odoo Online (the versions we've actually run against). The viewer shows live numbers on each part card, with a graceful fallback to a static erp.json when the connection is unreachable.
○

Packaged Odoo module

Wiring today is a small custom integration per deployment. A drop-in Odoo Apps module that bundles the QWeb template and the SKU mapping is scoped; until then, expect a short scoping conversation when you onboard.
○

Direct sale.order writes from the viewer

The host page handles cart writes today; the viewer just emits the add-to-cart event. If you need a deeper sync (draft-order create, audit trail), it's a paid scoping engagement.

✓ wired today · ○ scoped — if a scoped item is on your critical path, email [email protected] before you sign.

Other ERPs (SAP, NetSuite, MS Dynamics) follow the same overlay pattern — talk to us about scope.

Track B · Ecommerce

A web component and one event.

Drop the component on your product page. When a shopper picks a part, the viewer posts an event up to the host page; your storefront's existing add-to-cart maps SKU → variant and continues to your normal checkout. No Quidities-side cart, no second login, no theme rewrites.

Drop the component on your product page

<script src="https://q.dt/v1.js" async></script>

<quidities-viewer
  asset="rover-v8-engine"
  on-add-to-cart="window.addItem">
</quidities-viewer>

Wire the event to your existing add-to-cart

// window.addItem receives:
{
  sku:      "ROV-V8-1310",
  quantity: 1,
  part_n:   "05",
  asset:    "rover-v8-engine"
}
// You map sku → variant in your storefront.

Storefronts we plug into

ShopifypostMessage + theme snippet

WooCommercepostMessage + filter hook

BigCommercepostMessage + storefront API

Custom cartspostMessage + your handler

Built by Pogodan's integrations practice.

Quidities is the parts-catalog product; the integration work behind it sits inside Pogodan's broader integrations & automation engineering line. If your stack needs more than the ERP overlay + ecommerce embed above — orchestration, sync, scheduled imports, bespoke connectors — those are the same engineers and we can scope it as part of the onboarding.

Pogodan integrations & automation →

PICK A TRACK

Upload a STEP file. We'll send back an install snippet pre-mapped to your stack.

Upload a STEP file →