Selected Work

Systems in production.

Below is a system running an importer's daily operation, followed by the shapes of build we do most often. Client names are withheld where they've asked for it — we'll walk through the live system on a screen share.

Case Study 01 · In Production

A specialty goods importer, Los Angeles

IN PRODUCTION

From five disconnected systems to one live hub

~2,900 SKUS · 5 SALES CHANNELS · IMPORTED PRODUCT · OWNER-OPERATED

A wholesale importer selling through Amazon, their own site, US dealers, international distributors, and trade shows. Inventory lived in their ERP. Distributor revenue lived in QuickBooks. Freight status lived in an inbox. Nobody could see the whole picture without a person spending most of a morning building it.

What we found

  • Purchasing decisions made from a report that was three days stale by the time it was read
  • Units already on the water not subtracted from reorder quantities — so the same SKU got ordered twice
  • International distributor revenue invisible in the ERP entirely
  • Container status reconstructed by searching email
  • 51 exclusive and limited-edition projects tracked in one spreadsheet, on one laptop, maintained by one person

What we built

  • Six connectors into one canonical schema — ERP, Amazon SP-API, Shopify, QuickBooks, Sheets, and a manual freight connector
  • Purchasing engine that nets inbound units and applies per-vendor lead times
  • Role-based seats: owner, purchasing, accounting, and custom projects
  • A two-stage projects model — resin PO to production PO to promised ship month — that the ERP could not represent
  • A WhatsApp agent that turns a chat message into a finished contract, in Hebrew
$250K+
Committed project value surfaced that had never been consolidated anywhere
6
Live data sources in one view, refreshed continuously
1 file
Client-specific configuration — the engines are shared, so the next build is faster
NAME WITHHELD BY AGREEMENT · LIVE WALKTHROUGH AVAILABLE ON A CALL
What We Build

The builds we do most often

Three company shapes we build for regularly, with the systems that solve them and what a project like that runs.

COMMON BUILD

Housewares importer, 4,000 SKUs

Sells on Amazon and to regional chains. Purchasing runs off a monthly export; by the time it's built, the fast movers are already short and the slow movers already reordered.

BUILD: Reorder Brain + Container Tracker
TIMELINE: 4 weeks · $5,500–$9,500
COMMON BUILD

Apparel wholesaler, 60 dealers

Orders arrive as emails, PDFs and photos of handwritten sheets. Two people spend most of Monday and Tuesday keying them in, and the errors surface at invoicing.

BUILD: Order Intake + Invoice Chaser
TIMELINE: 3 weeks · $4,000–$6,500
COMMON BUILD

Specialty food distributor

Landed cost hasn't been recomputed since freight moved. Several SKUs are being sold below true cost and nobody will notice until the year-end close.

BUILD: Margin Watchdog + accounting seat
TIMELINE: 3 weeks · $4,500–$7,000
Where To Start

Start with one workflow

We open every engagement by mapping how work actually moves through your operation, then picking the single workflow with the most time or money sitting in it. You get that written plan whether or not you build with us — including the parts you could implement yourself.

Start Here

See what this looks like on your operation

Fifteen minutes on how the work moves today, where it stalls, and what the first system would be.

Book a call hello@charidan.com · Los Angeles / Tel Aviv