From Spreadsheets to an ERP: What Digitizing a Manufacturer’s Operations Really Took

Between October 2020 and August 2025 I was Director of Marketing and Technology at Pravada, a Fort Myers manufacturer. In that time the company moved its operations from spreadsheets to shopVOX, a cloud shop-management ERP, integrated it with Shopify, standardized labeling on Zebra printers and GS1 barcodes, and got pricing models and margin dashboards. The same period built an in-house printing operation that my resume describes as "driving multi-million-dollar cost savings over five years," and I will leave that number at the resume's wording, because that is as precise as I can be in public.

The outcome that matters for anyone reading this with their own spreadsheet open: it worked, and almost none of the hard parts were technical.

Context

A manufacturer running on spreadsheets is not disorganized. It is organized in a way that only works while the people who built the spreadsheets are in the room. Quotes live in one file, jobs in another, inventory in a third, and the relationships between them live in someone's head. That holds up to a certain order volume and number of channels, and then it does not.

Pravada crossed that line as its channels multiplied. The private-label site, PravadaPrivateLabel.com, was rebuilt on Shopify with a custom Liquid, section-based theme. The wholesale storefront, PravadaBeautyLabs.com, did $10,000 in its first month and passed $1 million in its first year, which is its own story in the Shopify wholesale case study. Orders from two storefronts landing in spreadsheets that did not know about each other was the problem the ERP had to solve. The storefronts were in better shape than the operations behind them.

Approach

Why a job-shop ERP instead of a manufacturing ERP?

The first decision is category, not vendor. A manufacturer that does custom and private-label work behaves more like a print shop than a factory: every job is quoted, proofed, produced, and shipped, and the quote is where the margin is won or lost. shopVOX positions itself for exactly that. Its site is organized around sign shops, print shops, apparel shops, installation shops, and custom manufacturing, and its integrations page promises "sales, design, production, customer support, and accounting under one roof."

The 2026 field, from the vendors' own pricing pages accessed 2026-09-22:

Product	Built for	Pricing (official, September 2026)	Shopify
shopVOX Express	Quote-to-job shops	$109/mo plus $29 per user (one included); QuickBooks Online, Sage, Xero; no onboarding fee	No native connector; Zapier (shopVOX's own how-to uses it)
shopVOX PRO	Same, plus CRM, custom workflows, API, purchase orders	$249/mo plus $49 per user (one included); onboarding from $499	Same, plus API access
Katana Cloud Inventory	Small makers who need MRP and stock across locations	Free up to 30 SKUs; Core from $299/mo, unlimited users; paid add-ons for traceability, manufacturing, warehouse	Native, bidirectional
Fishbowl	Inventory-first, QuickBooks-centric	Essentials $229/mo (2 users) to Scale $729/mo (10); Advanced Manufacturing from $675/mo; implementation extra	Native plugin on Advanced
Odoo	Modular open-core ERP	One App Free; Standard $24.90 per user/mo yearly; Custom $49 adds Studio and the external API	App-store connector

Third-party listings for shopVOX still show older flat prices of $99 and $199. They are stale. Read the vendor page.

Order of operations

The sequence I recommend, because each step depends on the one before it:

1. Customers and products first. Nothing else works until the customer list is clean and every product has one canonical record.
2. Quoting and pricing second. This is where the spreadsheet habit is strongest, because the quoting spreadsheet is usually the owner's. Rebuild the logic in the ERP's pricing tools and run both in parallel until they agree.
3. Jobs and production third. Once quotes convert to jobs inside the system, the shop floor has a reason to look at a screen.
4. Labels fourth. Standardize every unit and carton label before volume makes retrofitting painful.
5. Reporting last, but designed first. Know which dashboards you want before step one, so the data to feed them is captured from day one.

How does shopVOX connect to Shopify?

Shopify was where online orders originated, so the ERP had to see them. As of September 2026, shopVOX lists no native Shopify connector. The documented route is Zapier: shopVOX's own how-to on sending Shopify orders into shopVOX sales orders runs through it, and the open API on PRO is the other option. The objects worth syncing are the ones Katana and Fishbowl list for their native connectors: products and SKUs, orders into sales orders, inventory levels back out, and fulfillment and tracking back to the store. The connector decides how much manual matching remains, and manual matching is where the spreadsheet sneaks back in.

GS1 barcodes and Zebra labels

Standardized labeling means two things: a barcode any retailer's scanner accepts, and a label that prints the same way on every printer in the building.

The barcode side runs through GS1 US. As of September 2026, its published pricing is:

GS1 US product	Initial fee	Annual renewal
Single GTIN	$30	$0
Company Prefix, 10 items	$250	$50
Company Prefix, 100 items	$750	$150
Company Prefix, 1,000 items	$2,500	$500

A single GTIN is fine for a handful of products. A manufacturer needs a company prefix, because GS1 requires a new GTIN for every variation of size, color, style, or pack count, and a prefix also identifies cases, pallets, and locations. A private-label catalog with dozens of variants burns through a 10-item prefix in a week.

The label side runs on ZPL, Zebra's page-description language. Every label format opens with ^XA and closes with ^XZ; ^FO positions a field, ^FD supplies its data, ^BU prints a UPC-A barcode, and ^PQ sets the quantity. A minimal product label for a 4-inch printer at 203 dpi looks like this:

^XA
^PW812
^LL406
^FO40,30^A0N,36,36^FDSAMPLE PRODUCT 8 OZ^FS
^FO40,90^BUN,120,Y,N,Y^FD01234567890^FS
^FO40,260^A0N,28,28^FDLOT 260915^FS
^PQ1
^XZ

Once the label is a template with fields, the ERP fills the fields and any Zebra on the network prints it. ZebraDesigner 3 Essentials is free for Link-OS printers and covers the design work for most shops. On hardware, as of September 2026 the desktop ZD421 (4-inch, 203 or 300 dpi) covers unit and shelf labels, and the industrial ZT411 (up to 600 dpi and 14 inches per second) is what you buy when the desktop becomes the bottleneck.

Pricing models and margin dashboards

The pricing model is the spreadsheet with the strongest owner, so the pricing models and financial reporting I designed had to earn their place: unit economics, margin dashboards, and channel performance across private label and wholesale. Once jobs live in the ERP, it supplies the costs, and the dashboards turn them into a conversation about which channel is paying for the building.

The in-house print operation

Bringing printing in-house is the line on my resume with the biggest number attached, quoted above as written. What an ERP adds to a decision like that is measurability: once jobs, materials, and labor are in one system, in-house versus outsourced is a report instead of an argument.

Change management

Every spreadsheet belongs to someone, and replacing it feels to that person like being replaced. The approach I recommend is parallel running with a deadline: both systems live, the ERP treated as the record, discrepancies chased daily, and a published date when the spreadsheet became read-only. Train by role, not by feature: the person who quotes learns quoting, the person on the floor learns the job screen. The first month is the hard one, and it should be.

What changed

Area	Before	After
Operations record	Spreadsheets	shopVOX: one record per customer, product, quote, and job
Online orders	Storefront and operations separate	Shopify integrated with the ERP
Labels	Not standardized	Standardized on Zebra printers and GS1 GTINs
Pricing and reporting	Spreadsheets	Pricing models with unit economics, margin dashboards, and channel performance
Print	Purchased outside	In-house operation, "driving multi-million-dollar cost savings over five years" (resume wording)
Wholesale	No wholesale storefront	PravadaBeautyLabs.com: $10,000 in month one, $1 million-plus in year one

Two things did not change: the people and the products. The system made their judgment visible and repeatable. It did not supply it.

What I would do differently

• Start the labeling standard on day one. Retrofitting GTINs across a catalog with variants is tedious, and GS1 wants one per size, color, style, and pack count. Buy the company prefix before the first product record exists.
• Pick the Shopify integration route before choosing the ERP. Write down the sync objects and the connector first and let that constrain the vendor list.
• Set the spreadsheet shutoff date at kickoff. Parallel running without a deadline becomes permanent, and permanent parallel running is two systems, both wrong.
• Design the dashboards before the data model. If margin by channel is the report you want, channel has to be a required field on every job from day one.
• Budget onboarding. As of September 2026 shopVOX PRO onboarding packages start at $499. Cheap next to your own evenings.

Stack

• ERP: shopVOX. Express and PRO pricing as in the table above; QuickBooks Online, Sage, and Xero connect natively, and the API is PRO only.
• Storefronts: Shopify, with a custom Liquid, section-based theme; catalog scaled through metafields, variant logic, and faceted collections.
• Labels: Zebra thermal printers driven by ZPL templates; ZebraDesigner 3 Essentials for layout; a GS1 US company prefix for GTINs.
• CRM: HubSpot, Zoho, and Pipedrive, with pipeline automation and lead routing. The CRM playbook is what that taught me.
• Analytics: GA4 and Tag Manager, set up the way the GA4 guide describes, plus structured data and Core Web Vitals work.

If you quote every job and still live in spreadsheets, the consulting page describes how WBX Creative scopes this kind of project, and the technical services page covers integration and labeling. The career detail is on the bio page.