Field Guide
Train the floor in one shift. No consultant, no two-week rollout.
Every Fenyx screen, written the way a supervisor actually trains: what it does, when to use it, and what good looks like. Hand this page to your trainers, open the demo next to it, and run the loop once. That's the whole onboarding.
Watch the 8-minute overview
The why behind the guide: tribal knowledge, the layer, the method, the pilot. AI-narrated overview.
Print the one-page summaryHow to use this guide
- Trainers: read one section, click its demo link, run the screen once. One screen per sitting — the whole floor is done in a shift.
- Supervisors: the 30-60-90 plan below is your rollout calendar. Day 1 is two people, not twenty.
- Buyers: read Trust Pack, Dollar Autopsy, and Settings. Those three answer every question a boss's boss asks.
Command Pulse
The screen you open before the shift starts.- What it does
- One read: accuracy against target, open exposure in dollars, dollars caught this week, counts waiting on an autopsy, hot racks, and the loop progress for the session. Shift handoff notes sit underneath.
- When to use it
- Start of shift, mid-shift check, and every handoff. If you read nothing else, read this.
- What good looks like
- You can say the accuracy number, the open exposure, and the worst rack out loud without opening a second tab.
Capture
The radio note becomes a rule the floor owns.- What it does
- Type, paste, or speak the note exactly the way you'd say it on the radio. Fenyx extracts the trigger, object, condition, required action, owner, backup, and the war story behind it — then you confirm the card before anything goes live.
- When to use it
- Any time tribal knowledge surfaces: a correction on the floor, a supplier quirk, a 'never do this on grave' moment.
- What good looks like
- A brand-new hire could read the rule card and know exactly what to do — and why it exists.
Counts
Every variance with a reason attached.- What it does
- The last 14 days of cycle counts with variance, status, and the living rule already attached. Paste a count and Fenyx routes it straight into the right autopsy. The detail view shows system on-hand vs counted, the linked rule, and the next move.
- When to use it
- As soon as counts post. Nothing gets written off before someone explains it.
- What good looks like
- No count sits unexplained. Each one has a status, a linked rule, and a next move.
Living Rules
Tribal knowledge, structured and enforceable.- What it does
- Every accuracy rule the floor lives by: trigger, object, owner, backup, exceptions in the last 30 days, and the note it came from. Search by rule, SKU, or location. Statuses: Active, Draft, Needs Review, Retired.
- When to use it
- After a capture, during onboarding, and before any audit — this is the binder, except it's never out of date.
- What good looks like
- Every active rule has an owner and a backup. No single point of knowledge anywhere.
Exceptions
What broke, which rule it broke, what to do.- What it does
- A four-column board: New → Investigating → Fixed in process → Closed with SOP. Each card names the rule it broke — or shows 'no rule yet', which is exactly where the next capture should come from.
- When to use it
- Daily triage. Work it left to right; move every card once a shift.
- What good looks like
- Nothing sits in New overnight, and every 'no rule yet' card gets captured before it's closed.
Accuracy Autopsy
Explain the miss before anyone touches the number.- What it does
- The facts, the movement timeline, and what the floor already knew. Then the cause board: confirm or kill each likely cause in order — slot drift, method, timing. Theft is last, never first. It ends with tonight's procedure and a coaching card.
- When to use it
- Any count with a variance the floor can still explain today. Work the CC-118 Valley Gas autopsy to see a finished one.
- What good looks like
- The shift leaves with a fail-if procedure they can run tonight — not a write-off.
Dollar Autopsy
The same miss, priced.- What it does
- Inventory dollars at an editable unit cost, chargeback and audit risk, and total open exposure — plus a 7-step walk through the miss in supervisor voice, naming bins and people. Edit assumptions, walk the rack, or write the SOP straight from here.
- When to use it
- When an exception has real dollars behind it and you need the number for the ops meeting or the client.
- What good looks like
- An exposure figure you can defend line by line — and every assumption stays editable by you, not locked in a black box.
Trust Pack
The one page a client can read without a translator.- What it does
- The client-safe weekly summary: accuracy against target, exceptions opened, closed with SOP, voided before a bad adjust, what was caught, what stays open, and which rules were added. First names only, no unit-cost tables, nothing hidden. Print or save as PDF.
- When to use it
- Weekly client cadence — and before any QBR or account review.
- What good looks like
- Open items stay visible. A client trusts the page because it never hides the bad news.
Accuracy Map
A floor plan a supervisor can read from the aisle.- What it does
- A flat schematic of the DC shaded by exception density: inbound, QC cages, bulk, pick modules, will-call, outbound. Click a zone for its recent notes, the active rules that govern it, and its locations.
- When to use it
- Deciding where the next count, huddle, or walk goes. Also the fastest way to show leadership where the bleeding is.
- What good looks like
- You can point at the worst zone in the building in under five seconds.
SOP Studio
Tribal note on the left, trainable procedure on the right.- What it does
- Turn active living rules into a real warehouse procedure: purpose, when this applies, steps on the floor, what good looks like, and what to do when it fails. Copy or print it, mark it trained, and close the linked exceptions once the floor has run it.
- When to use it
- After an autopsy confirms a cause, or the moment a rule activates. The SOP and the training happen the same day.
- What good looks like
- The procedure was written by the shift that found the miss — and trained before the next shift starts.
Ghost Hunt
System says it's here. It isn't. Find it.- What it does
- Point Fenyx at the empty bin. You get a verdict — ghost, miscount, unit-of-measure trap, cut-off timing, theft-or-shrink, or not enough evidence — with confidence, the three places the units probably are, and a procedure and handoff you can copy. Fenyx does not post adjustments; you decide in the WMS.
- When to use it
- A bin is empty on the floor but full in the system. Run the hunt before anyone adjusts anything.
- What good looks like
- A verdict with evidence behind it, and the final call made by a human in the system of record.
Team & Shifts
When a lead quits, the knowledge should stay.- What it does
- Who owns which accuracy rules, who backs them up, and the cross-training badges each person carries. Not an HRIS — a knowledge map.
- When to use it
- Coverage planning, onboarding, and the moment a lead gives notice.
- What good looks like
- Every rule owned and backed up. No rule lives in exactly one head.
Settings
Facility, target, and the one rule that never bends.- What it does
- Facility name, ERP note, accuracy target, and shifts. Dollar assumptions are edited here — they stay yours. The principle is locked in: Fenyx never auto-adjusts the system of record. Humans close the loop.
- When to use it
- Setup, and any time you review the dollar assumptions behind your exposure figures.
- What good looks like
- The assumptions are visible, editable, and nobody pretends they're accounting data — they're supervisor judgment, in one place.
The 30-60-90 rollout
The same pace that works for a SAP cutover works here, just faster: train trainers first, prove the loop on one real miss, then make the cadence boring.
Train the trainers
Pick two people, not twenty. Walk them through Command Pulse and Capture using a real note from last week. Activate the first living rule together. That's the whole day — the loop starts running immediately.
Capture everything, autopsy one
Every new tribal note gets captured — radio quotes welcome. Run the first full autopsy on a live variance and write the first SOP from it. Hand your team the procedure before the next shift.
Weekly cadence
The Trust Pack goes out weekly. The Accuracy Map drives count planning: the hottest zone counts first. Every exception moves a column at least once every 24 hours.
The loop is a habit
Capture → rule → exception → autopsy → SOP → close runs without prompting. Accuracy is reviewed in the ops meeting using Fenyx numbers, and the dollar assumptions get their first quarterly review.
Day-one shift-huddle script
Five minutes, spoken, no slides. Read it out loud at the first huddle — or hand it to the shift lead and let them make it theirs.
1.“Alright, two minutes before we break. This is Fenyx. It is not our WMS and it will never change a number in there — every adjustment is still made by one of us, in the system, like always.”
2.“Three things today. One: if you learn something on the floor — a supplier quirk, a slot that keeps getting messed with — you tell me or you type it into Capture. Sixty seconds. The note stays even when people move on.”
3.“Two: when a count comes back short, we do not write it off and we do not start hunting a thief. We walk it: did something drift to the wrong slot? Did a pack get broken wrong at receiving? Did the timing cut it off? The tool walks us through it — theft is the last thing we look at, not the first.”
4.“Three: when we fix something, it becomes a rule and an SOP, and we train it before the next shift. That's it. Anybody's count, anybody's note — it all lives in the same place now.”
5.“Questions? Good. Let's run the floor.”
Questions you will get
Does Fenyx post adjustments to our WMS?
No — never. Fenyx sits beside the system of record. A human closes the loop, in the WMS, every time.
Does it touch finance?
No. Every dollar figure in Fenyx is a supervisor-editable assumption in one auditable place. It prices process risk; it does not do accounting.
Does it replace our WMS or ERP?
No. It runs beside whatever you already run, and it never writes back to it.
Who sees client data in the Trust Pack?
The Trust Pack uses first names only, shows no unit-cost tables, and never hides open items. It is built to be forwarded.
What happens to the knowledge when a lead leaves?
It stays. Every rule has an owner and a backup, and the war story rides along with the rule.
What does it cost?
Pilot $399/site/month · Trust Pack $99/client/month. One prevented mis-ship or chargeback clears the pilot.
Is the demo real data?
The demo data is fictional (Westline DC — Inland Empire) and Fenyx is not affiliated with any past employer. The method is real.
Ready to put it on your floor?
Pilot $399/site/month · Trust Pack $99/client/month
One prevented mis-ship or chargeback clears the pilot.
Demo data is fictional (Westline DC — Inland Empire). Fenyx is not affiliated with any past employer. Dollar figures are supervisor-editable assumptions; Fenyx never touches finance and never posts adjustments to the system of record.