The inventory platform you can talk to.

• 01

  Asks before it acts.

  Every write — stock, orders, purchasing — comes back as a confirmation card showing exactly what will change. Nothing happens until you approve.

• 02

  Drives the screen you’re on.

  "Show only confirmed orders" filters the grid. "Take me to purchasing" just goes.

• 03

  Speaks your language.

  Push-to-talk and spoken replies — in English and Indian languages.

• 04

  Sees what you see.

  Photo of a product → identified, described, actioned. And it generates product images on request.

• 05

  Remembers what you approve.

  A per-business knowledge base: notes, files, even forwarded emails — everything enters through an approval queue, then it’s recallable in chat. Deep web research mode for when the answer isn’t in your data.

  Add-on
• 06

  Spends within budget.

  Per-business AI budgets with self-serve top-ups. You control the meter.

1. 01

   Single, variation & bundle SKUs

   Model standard products, parent/child variations and kits/bundles as first-class SKU types. → One catalog for everything you sell — no duplicate records, no double-counted stock.

2. 02

   Variation axes

   Declare up to five attributes — size, colour, finish — as a parent's variation dimensions; every child carries its combination, duplicates are rejected. → Variation grids stay clean at any scale.

3. 03

   Availability roll-up

   A bundle's available count is computed live from its components — the floor of what you can assemble, with the limiting component flagged; a parent shows the sum of its children. → Promise only what you can actually build and ship.

4. 04

   Typed custom attributes

   Text, number, select, multi-select, date and boolean fields with units, validation and defaults — org-wide or per category. → Capture the spec sheet that matters in your industry, then search and filter by it.

5. 05

   Bin-level stock

   Stock is tracked per SKU, per warehouse, per bin; bin-to-bin and cross-warehouse transfers; every movement lands in a ledger. → Know where every unit physically is — and prove it.

6. 06

   FIFO costing & valuation

   Every goods receipt opens a cost layer; outflows draw oldest-first; valuation totals stock value per SKU and warehouse. → A defensible stock value, and margins based on what inventory actually cost.

7. 07

   Image library

   Upload once, reuse across SKUs — reference-counted so shared artwork never breaks; the assistant can also generate product images on request. → Product imagery without duplicate uploads.

8. 08

   The products grid

   Search over every column and custom attribute, an AND/OR filter builder, saved views (personal or shared), per-user column layouts, bulk actions, and ⌘K everywhere. → Each person works their own slice of the catalog — and shares it as a URL.

9. 09

   CSV import & export

   Products, suppliers, inventory, customers and orders — with per-row error reporting that never aborts the rest of the file. → Leave the spreadsheet without losing your history.

10. 10

    Product activity log

    Every change to a product — who, what, when, from the UI or from the assistant. → Accountability that survives staff turnover.

11. 11

    Safety stock & dashboard

    Safety levels per item; the dashboard opens on what needs attention. → The morning check takes a minute, not a meeting.

12. REPLENISHMENT
13. 12

    Suppliers & purchase orders

    Growth plan

    Vendor records with a preferred supplier per product; purchase orders run draft → submitted → confirmed → received. → Buying has a paper trail.

14. 13

    Receiving posts everything

    Growth plan

    A goods receipt adds stock at the bin and opens its FIFO cost layer at the PO's cost — one step. → Nothing re-keyed between purchasing and stock.

15. 14

    Low-stock alerts & reorder drafting

    Enterprise plan

    Background workers watch safety levels and draft reorder emails for your review. → Replenishment starts itself; you stay in charge of the send.

Everything above is a sentence away — "how many gift sets can we assemble?" is a question, not a report request.

1. 01

   A guarded lifecycle

   Draft → confirmed → picking → packed → shipped → fulfilled, every transition validated; cancelling releases reservations. → A pipeline the whole team can trust at a glance.

2. 02

   Confirm = allocation

   Confirming reserves available stock. If there's a shortfall, the order goes backordered holding what it could reserve — and "reserve remaining" retries as stock lands. → Overselling becomes structurally impossible, not a policy.

3. 03

   Pricing engine

   Per-line and order-level discounts (amount or percent), tax with per-line exemptions, per-order currency, live totals as you build. → The quote, the order and the invoice agree.

4. 04

   Partial shipments

   Ship in parts; each shipment gets its own record; shipping decrements stock and draws FIFO layers. → Ship what's ready now — the order tracks the rest.

5. 05

   COGS & margin per order

   Realized cost rolls onto the order at shipment, next to the revenue it earned. → Profit per order, not per quarter.

6. 06

   Customers with channel identity

   Customer records deduplicate by source + external id. → Import from marketplaces without duplicate customers.

7. 07

   Three-mode order import

   Draft (no stock touched) · confirmed (reserves live stock) · historical (record only, zero stock movement) — with auto order numbers and duplicate detection. → Bring years of history in without corrupting today's stock.

8. 08

   Draft-guarded editing

   Orders are editable exactly while it's safe (draft), with lifecycle timestamps throughout. → Fix mistakes without breaking the audit trail.

9. 09

   The make-to-order bridge

   Enterprise plan

   Confirm an order for something you manufacture and a work order is raised automatically; when the build lands, the order completes its own reservation. → Sell what you haven't built yet — safely.

"Show only confirmed orders" filters this screen — and a stock adjustment still comes back as a card to approve.

1. 01

   Versioned recipes (BOMs)

   A finished good plus component lines with quantity and scrap %; publishing makes a version active, effective-dated; new versions supersede without touching history, on a visible version timeline. → Change the recipe on Monday without corrupting last month's costs.

2. 02

   Multi-level explode

   Preview total component demand for any build quantity — sub-assemblies roll up, scrap included. → Know true material demand before you commit to a job.

3. 03

   Work orders from the sale — or by hand

   Confirming a sales-order line for a manufactured good raises a work order automatically, carrying a frozen snapshot of the exploded recipe; manual work orders for everything else. → The floor starts from the sale — nothing re-keyed.

4. 04

   Due dates & priorities

   Every job carries a due date and a priority. → Sequence the floor by what actually matters this week.

5. 05

   Make-or-buy, per component

   The work order shows on-hand availability versus shortfall for every component, across warehouses. → The build-vs-buy call is one glance, per job.

6. 06

   Release starts procurement

   Releasing a job reserves available components; the remaining shortfall becomes suggested purchase orders grouped by supplier — one click raises them in Purchasing. → No mid-build stockout surprises; buying starts itself.

7. 07

   Workflow templates

   Ordered WORK and GATE stages with rework targets; map templates to finished goods, to categories, or set a default — resolved and snapshotted onto the job at release. → Every product family gets its own process, and in-flight jobs never shift under your feet.

8. 08

   The job board

   A kanban of live jobs by stage. WORK cards advance; GATE cards pass or fail — a fail loops the job back to its rework target and counts it; supervisors can override. → Quality control sits in the flow, and rework is measured instead of hidden.

9. 09

   Record build — one atomic step

   Enter actual components consumed and quantity produced: components are drawn at FIFO cost, the finished good enters stock as a new cost layer at the rolled-up unit cost, and the job completes — one transaction. → A true production cost per unit, computed rather than estimated.

10. 10

    Partial builds

    Produce in tranches against one work order. → Ship what's finished while the rest is still on the bench.

11. 11

    Un-build

    Reverse a recorded build; stock and cost entries back out cleanly. → Mistakes are correctable — with the audit trail intact.

12. 12

    Dispatch closes the loop

    When the build lands, the originating order completes its reservation automatically and ships through the normal flow; the sales order gains a manufacturing panel — job status, current stage, unit cost. → Sales watches production without walking to the floor.

13. 13

    Your industry's language

    Terminology packs with per-term overrides — jobs, batches, repairs, commissions — plus starter workflow templates by industry. → The app reads like it was built for your shop, because the labels are yours.

14. 14

    Custom fields on the work itself

    Typed fields on orders, on work orders by job type, and on stages. → Capture intake details, measurements and checklists exactly where they belong.

15. 15

    Stage power-ups

    Send a job back to any earlier stage with a reason; per-stage fields; structured assignees; instructions on the stage itself. → The board bends to how work actually moves — including backwards.

16. 16

    A thread on every job

    Stage-aware discussion on each job with @mentions; the assistant reads the job's context, documents decisions, and acts on approval. → Decisions live with the job — not in a chat app nobody searches.

"Explode the recipe for the oak stool" or "record the build for WO-0042" — the assistant runs this floor too, always behind a confirm.

1. 01

   Multiple stores

   Connect each Shopify store with its own credentials, refreshed automatically. → One catalog behind many storefronts.

2. 02

   Per-store field mapping

   A business-wide default map plus per-store overrides — standard and custom fields, with a preview of exactly what will be sent. → Each store gets precisely the data it should.

3. 03

   Per-product store targets

   Choose, product by product, which stores carry it — from the product editor or in bulk from the grid. → Segment your channels without maintaining separate catalogs.

4. 04

   Label-driven publish & remove

   Tag a product and it publishes to the store; untag and it's removed. A background reconciler drives the change and tracks per-listing status, the last error, and one-click retry. → Publishing is an intent you set, not a script you babysit.

5. 05

   Store attribution on orders

   Every order records which store it came from. → Channel performance is visible right in the orders list.

Ask "which products aren't published to the retail store yet?" — the grid answers before a meeting could be scheduled.

• Roles and read-only accounts
• Two-factor auth
• Group threads with the assistantAdd-on
• Presence
• A full activity log on every product
• Low-stock alerts and AI-drafted reorder emailsEnterprise plan
• Works on your phone

All plans include a fair-use AI allowance — top up anytime, self-serve. Add-on modules (knowledge base, deep web search, group threads) available on any plan on request.