Velvet Arcs
Talk to us
Commerce operations technology practice

Modern operations technology for growing commerce businesses.

We start with inventory: best sellers that run out, slow stock that piles up, counts that don’t match, stock that arrives but can’t be sold. We make your systems agree, define inventory the way your operation actually works, and put decision logic on top. The internal tools your ops team never had, built inside the systems you already run.

verified_user Two senior operators from Amazon and AWS who built the internal tools operators use every day. Not another inventory platform.

your inventory control layer
Example · decisions with evidence
S Your store A Amazon W Warehouse / 3PL P Inventory planner YOUR inventory control layer built for you, inside your tools Reorder refill 40ml now 3,200 units · sellable by Nov 30 Move 600 to Amazon by Nov 3 900 held back for wholesale PO 2291 is nine days late 5 SKUs at risk · supplier chased
Where we start · inventory

Out of your best sellers. Overstocked on the rest. Not just a forecasting problem.

Inventory stopped being one number in one system a while ago. The warehouse knows what’s physically there. Amazon knows what Amazon can sell. Your store knows what customers ordered. The planner predicts what’s next. Somebody still has to make those systems agree and turn them into decisions. In most growing brands, that somebody has a spreadsheet. Three problems, in owners’ words:

01

What should we reorder, and where should it go?

Why it happens

Best sellers run out while slow stock piles up. You pay for a planner, but the real reorder happens in a spreadsheet, on the lead time the supplier promised rather than the one you get. And how many units go to Amazon versus the warehouse is a business decision no forecast makes for you.

What we look at

A year of purchase orders against when each one actually became sellable. The promotions and channel splits the planner never heard about. Stock-out days per best seller, and what each cost.

What a fix looks like

A lead time that corrects itself from your receipts. A reorder list that already knows about next month’s promotion. An allocation rule written down and applied the same way every week.

02

The stock arrived. Why can’t we sell it?

Why it happens

Between “delivered” and “available to sell” sit receiving, counting, putaway, a sync and a channel update. At your warehouse, then again inside Amazon. Units sit for days, sometimes weeks, while you pay for them and lose the sale.

What we look at

Each inbound shipment, state by state: landed, counted, seen by the warehouse system, sellable on your store and Amazon. And where the days went.

What a fix looks like

A check that flags any shipment stuck too long in one state, who owns that state, and what moves it on.

03

Which stock number is right?

Why it happens

Your store, Amazon, the warehouse and the planner each measure something different: owned, on hand, reserved, in transit, available to promise. Some differences are legitimate. Nobody can say which, so nobody trusts any of the numbers.

What we look at

The same products across every system on the same morning, each difference explained: reservations, stock in transit, returns not yet restocked, a bundle mapped wrong, a damaged unit nobody recorded.

What a fix looks like

One trusted number per product, every morning. Legitimate differences explained. A short exception list of only the unexplained ones, each with an owner.

Good planners, order systems and warehouse tools already exist, and most brands we talk to own one. What’s missing is the layer that fits them to how your operation runs: stock numbers you can run the business on, reorder and allocation decisions made explicit, and a shorter gap between stock arriving and becoming money. Decisions reach your team with the evidence attached. Less checking by hand; the judgement stays with your people. Once inventory is in hand, the same method extends to the 3PL invoice, returns and marketplace payouts.

You shouldn’t need an in-house engineering team to fix an expensive operations problem.

AI changed what a small, experienced team can build. AI alone isn’t the advantage. The discipline around it is: operating judgment, structured diagnosis, proven economics, scoped access, safe implementation.

  1. person_check

    01 · Experience

    Senior operators

    We have run inventory, fulfillment and marketplace operations at scale. We know which problems matter.

  2. troubleshoot

    02 · Diagnose

    Structured diagnosis

    One expensive problem, traced to its root cause in your real data. Same method every time.

  3. monitoring

    03 · Prove

    Proven economics

    What the problem costs, quantified before anything is built. If the case isn’t there, we say so.

  4. lock

    04 · Access

    Scoped access

    Only the data and permissions the work needs. Read-only by default. You stay in control.

  5. verified

    05 · Build safely

    Safe implementation

    Test, validate, then automate. Inside the tools you run, with changes your team can see and reverse.

The internal tools large operators take for granted. No engineering team to hire. One costly problem at a time.

See how an engagement runs arrow_forward

Work directly with senior operators.

We spent years building marketplace, fulfillment and supply-chain systems at Amazon scale. We read what your data means operationally, not just how to connect two APIs. And we do the work ourselves.

AY

Ankita Yadav

Business diagnosis & client outcomes

A decade in product and growth across Amazon, AWS and venture-backed startups, most recently Principal Product Manager at Symbl.ai. She pins down the workflow, the economics and the outcome that matters, and keeps the technical work anchored to it.

AG

Aikansh Garg

Technical diagnosis & build

15+ years in operations and engineering leadership, including a decade building marketplace, fulfillment and supply-chain systems at Amazon, most recently as a Director of Engineering leading a 40-person org. He diagnoses what your data really means and builds the fix.

“And if you don’t need us to build anything, we’ll tell you.”

What we do

Diagnose. Quantify. Fix. Maintain.

radar

Find what’s costing you

A fixed-fee diagnostic. Three weeks, one costly inventory problem, your own data. We trace real cases across your systems, estimate the cost from evidence, and name every cause: a setting, a process, a vendor, or something genuinely missing.

Learn more arrow_forward
hub

Fix what’s worth fixing

Configure what you already own. Connect the systems you run. Recommend a proven tool where one fits (no referral fees). Build only the piece that’s missing, inside the tools you already use.

Learn more arrow_forward
published_with_changes

Keep it running

Optional, after a build. We watch the checks, handle what they raise, and re-tune the rules as your suppliers, channels and tools change. Everything we build stays yours.

Learn more arrow_forward
Who we help

Built for businesses that outgrew their spreadsheets.

Brands that sell on their own site, on marketplaces and through wholesale, with a warehouse partner and a team spending too many hours keeping the numbers honest. Too big for spreadsheets, too small for an engineering team. The pain tracks complexity, not revenue: products × suppliers × channels × lead times × commitments.

shopping_bag

Your own store

Shopify and other platforms

storefront

Amazon & marketplaces

FBA, AWD, FBM; wholesale too

inventory_2

3PL / Warehouse

ShipBob, your own WMS, a partner’s portal

calculate

Inventory planner & ERP

Inventory Planner, Cogsy, Prediko, Cin7, NetSuite, QuickBooks

Tell us where inventory keeps going wrong.

Thirty minutes with both founders. We’ll say whether a diagnostic is worth it. If it isn’t us, we’ll say so.

Book a 30-minute fit conversation