How a Small Fabric Manufacturer Stopped Losing Inventory to a Pencil — and Took Back Control of Its Zapier Stack
A small fabric manufacturer lost inventory to handwritten label corrections. Connex fixed their Zapier stack, migrated ownership, and automated notifications — saving ~$17k/yr.
TABLE OF CONTENTS
TL;DR: A small custom-fabric manufacturer regained ownership of its Zapier automations, fixed a remainder-roll mislabeling problem that caused chronic inventory errors, and added customer notification flows — estimated to save ~$17k/yr in manual correction labor and reduce mispicking risk.
The Situation
A small manufacturing business that cuts and ships custom fabric rolls to trade customers had been using Zapier to connect its ERP system ( to connect its ERP system (DEAR Inventory) to warehouse and customer communication workflows. The automations had been set up by the ERP implementer — sensible at launch. But it left the business with a structural problem: the zaps lived in the implementer's Zapier account and pointed to spreadsheets in the implementer's Google Drive. The client had no visibility, no control, and no ability to change anything without going back through a third party.
The Problem (in Their Words)
The label issue was the trigger: when a picking slip went out for a cut roll, the ERP printed a label for the customer's portion — but nothing for the remainder that went back to stock. A 50-meter roll cut to 30 meters returned to the shelf with the original 50-meter label. A picker would scratch out the number and write the remainder in pencil.
"The picker must take a pencil and cross 50m roll and write 20m — huge human error."
Multiply that across a day's worth of orders and you have chronic inventory inaccuracy, mispicking risk, and a process that required every operator to remember the manual correction — and get the math right. Compounding this: customers were receiving no automated status updates. No order confirmation, no shipping notification, nothing until the product arrived.
What They'd Already Tried
The business had trusted the ERP implementer to build the automations — reasonable when the system went live. The zaps partially worked. But "mostly working, owned by someone else" turned out to be worse than starting fresh: the client couldn't troubleshoot, couldn't modify the flows, and couldn't operate independently. When the label-printing step failed (the ezeep Blue printer integration timed out), there was no internal person who could diagnose it.
What Was Built
A Connex consultant ran a structured audit and migration across four phases:
- Ownership transfer. Every zap pointing to the implementer's Google account was identified, rebuilt in the client's own Zapier account, with spreadsheets moved into the client's Google Drive. The client now owns the entire automation stack.
- Zap audit and repair. Each automation was documented — what it does, where it fails, what's missing. The label-printing step was debugged: a timing issue caused DEAR to fire the webhook before ezeep Blue was ready. Fixed with proper delay logic and error-path handling.
- Remainder-roll label. A new zap listens for DEAR picking slips and calculates the remainder quantity automatically (ordered amount minus cut quantity). It generates a second label with the correct remaining meters and sends it to the warehouse printer. No arithmetic, no pencil.
- Customer notification flows. Automated emails now fire at each order milestone: order received, order cut, order shipped (with tracking), delay and backorder alerts. DEAR triggers the zap; the zap formats and sends. No manual follow-up required.
The Results
Estimated impact, based on the client's described workflow and a blended $45/hr labor rate.
Label corrections: In a fabric warehouse handling dozens of cuts per day, a conservative estimate of 30 cuts/day x 2 minutes of manual correction = approximately 1 hour/day — roughly 5 hrs/week of manual labor removed, or ~$11,700/yr. More significant is the reduction in mispick risk: a handwritten correction that's wrong sends the wrong amount to a customer and the wrong remainder back to stock. That's a quality and fulfillment problem, not just a time problem.
Customer notifications: Fielding 10-15 order-status inquiries per week at 5-10 minutes each = 1-2 hrs/week saved, plus the customer experience improvement of proactive updates instead of radio silence.
Ownership: The automation stack is now the client's. A new step, a template change, a new product category — all doable without re-engaging a third party.
FAQ
Does DEAR Inventory have a native Zapier connector?
Yes — DEAR Inventory (now Cin7 Core) supports Zapier via webhooks and a published Zapier app *(verified July 2026)*. The tricky part isn't the connection; it's the conditional logic around which triggers fire for which order states, and coordinating timing with downstream hardware like ezeep Blue.
How long did migrating the existing zaps take?
The migration phase alone was estimated at 3-5 hours: identify each zap, rebuild it in the client's account, point it to client-owned sheets, verify it fires correctly. The label fix and notification flows added scope. A realistic total for a project like this is 8-15 hours, depending on how many zaps exist and how documented the original setup is.
What if our ERP vendor built our zaps?
This is more common than it sounds. ERP and CRM implementers often build automation during onboarding — in their own accounts, for convenience. Ask explicitly: "Are these zaps in our Zapier account or yours? Are the Google Sheets in our Drive?" If the answer is unclear, a one-time audit before you need to change anything is worth it.
Does this pattern work for other ERPs?
Yes. The pattern — audit, migrate ownership, fix edge-case logic, add notification flows — applies to any ERP with Zapier integration or webhook support. Cin7 Core, Unleashed, Katana, Fishbowl, and similar systems all expose order-state triggers that power notification and label workflows.
Audit Your Automation Stack
Ready to audit your automation stack and take back control? Book a call.
Related Posts
Building a custom code shop for automation agencies (a playbook)
Custom code solutions for automation agencies: a playbook to productize offers, run scoped delivery (QA + release), and scale beyond fragile Zaps.
JobPro to Sage: webhook sync blueprint (no public API)
JobPro Sage integration without a public API is doable. Use outbound webhooks and a middleware layer to sync customers, jobs, invoices, and job costs reliably.
