Break It First

Kits

Two-store inventory sync

Keeps two online stores on one inventory count, and flags the order that oversold.

Covers: two online stores and one master count. Oversold orders are listed for you, not cancelled.

Limit: Both stores are mock APIs. It has not run against a real store or sheet account.

What you get

  • This kit, set up on your data after a written brief.
  • Its test report: what we broke, what caught it and what got through.
  • A plain list of its limits, and a report or log after every run, so you can check the counts the next day.

What we need from you

  • A sample export, or access to a test copy of the tools it connects.
  • A written brief: what it should do and where you think it breaks.

Price: from $49, fixed quote in writing before any work.

Timing: the written quote states the delivery date.

Ask about this kit

or write to teambreakitfirst@gmail.com

The problem

You sell the same items in two online stores, and each store only sees its own count. When the last unit sells in both stores at nearly the same time, each store accepts its order because it still shows 1 left.

What we broke

  • We sold the last unit in both stores at nearly the same time. The sync kept the earlier order and listed the later one as oversold, to cancel or back-order.
  • We crashed the run after 3 orders were applied, then ran it again. Both stores and the master count equal one clean run.
  • After the run, we checked store A, store B and the master count against each other. They were equal, with 0 negative counts.
  • We planted 28 bugs in its code, one at a time. The tests caught 28 of 28.

Before / after runTwo-store inventory sync

Short video, no sound. The slides below show the same steps.
  1. Hook: 1 mug left, 2 stores sold it. Run 1 counts with the oversold line outlined. Mock stores, synthetic data.
  2. The race: store A and store B each see their own inventory count of 1, so both accept an order for the last mug.
  3. Run report lines: the later order, B 9001 mug-black, is listed as oversold, to cancel or back-order. Low inventory alert for MUG-BLK.
  4. Chart of run 1: orders per store, 4 lines accepted, 1 line oversold, 2 unmapped, 0 conflicts. The oversold row is outlined.
  5. Checks: store A equals store B equals master for 5 SKUs, negative inventory counts 0, 24 tests passed, 28 of 28 planted bugs caught.
  6. Limits: mock stores only; the sync lists oversold orders, it does not cancel them. Follow for one tested kit at a time.

What it does after the fix

It keeps store A, store B and one master count equal. When two orders race for the last unit, the earlier order stands. The later one goes on an oversold list for a person to cancel or back-order. After a crash, a rerun ends where one clean run would.

Limits

  • Both stores are mock APIs. It has not run against a real store or sheet account.
  • It lists oversold orders. It does not cancel them.
  • Our own demo kit, run on made-up data.

What happens after you write

  1. You write

    Email us or send a DM on X: what it does and where you think it breaks.

  2. We ask a few questions

    About your tools, your data and what counts as done.

  3. Fixed written quote

    The quote states the price and the delivery date.

  4. Work starts only after you say yes

    Nothing is built before you agree to the quote.

Want this on your data?

Ask about this kitSend a DM on X

or write to teambreakitfirst@gmail.com

Kits set up on your data from $49. A test run on your own automation from $45. Fixed quote in writing before any work.

This kit's logged test run

tests
24 passed -> OK
bugs
28 of 28 planted, caught
data
made-up, mock services
Our own demo kit, run on made-up data.