Back to Case Studies
Case Study

One Platform Replaced Six Tools and 170 Years of Workarounds

Parameter built Wells & Drew a unified Odoo system — website, ecommerce, custom client stores, approval workflows, and full ERP — so a heritage specialty printer could stop managing complexity and start managing growth.

Odoo Odoo

Wells & Drew

Featured image not set.
Wells & Drew Q1 2024 – Ongoing Odoo
wellsdrew.com

The Situation

What was breaking

Order management was entirely manual. Client-specific pricing lived in spreadsheets and people's heads. There was no self-service option for clients — every order required a phone call or email, even reorders of identical products. Inventory, production, and accounting were siloed, so the same data got entered three or four times across different systems.

What was at risk

Institutional knowledge was the single point of failure. If the people who knew the pricing tiers and client preferences weren't available, orders stalled. As the team stayed small and the client base grew, the manual coordination overhead was consuming capacity that should have gone to production and client service. The 170-year reputation was being maintained on spreadsheets and goodwill.

What had already been tried

They had looked at standard ecommerce platforms — Shopify, BigCommerce — but the B2B pricing model killed every option. Per-client pricing, approval workflows, and consultative quoting don't fit neatly into platforms designed for B2C. They had also tried adding point solutions for specific problems (shipping software, basic CRM) but each new tool just added another tab to manage.

Why earlier fixes didn't hold

Standard ecommerce treats every customer the same. Wells & Drew's model is the opposite — every client relationship has its own pricing, its own product catalog, and often its own approval chain. Bolting that logic onto a B2C platform meant fighting the platform at every turn. And adding more standalone tools didn't reduce complexity; it multiplied it. Six tools meant six logins, six data sources, and zero single source of truth.

The business

Wells & Drew is a specialty printing and premium stationery company founded in 1855 in Jacksonville, FL. They serve over 1,500 professional clients — primarily law firms, accounting firms, real estate brokerages, and financial institutions — with services including engraving, embossing, foil stamping, letterpress, and die cutting. Their work is consultative and relationship-driven, with negotiated pricing and a 98% five-year client retention rate.

Scale

~13 employees, single Jacksonville facility, 1,500+ active professional clients, 170+ years in continuous operation. B2B model with tiered and negotiated pricing — not a volume play.

Existing stack

Disconnected mix of standalone tools: separate website (brochure-style), manual order intake via phone/email, spreadsheet-based pricing, standalone accounting software, no integrated inventory or manufacturing tracking. CRM was essentially contact lists and memory.

Constraints

Small team with no dedicated IT staff. Every hour spent on system management was an hour not spent on client work. The B2B pricing model — different clients, different prices, approval requirements — meant off-the-shelf ecommerce platforms couldn't handle the logic without heavy customization. Budget required a single platform, not a stack of SaaS subscriptions.

Approach & Solution

Why this approach

Odoo offered the rare combination of full ERP capability with enough flexibility to build custom modules on top. The per-client store concept, the approval workflow engine, and the custom quotation system all required development — not just configuration — and Odoo's architecture made that feasible without forking the platform. It also meant one vendor, one database, one system to maintain.

Alternatives considered

Shopify Plus with third-party B2B apps was considered but couldn't handle the approval workflow complexity or per-client pricing at the level Wells & Drew needed. A custom-built Rails or Django application was discussed but would have required ongoing development resources the team didn't have. NetSuite was evaluated but the cost was prohibitive for a 13-person operation.

Tradeoffs

Odoo's out-of-the-box ecommerce isn't as polished as Shopify's — the team had to invest more in front-end design to match the premium brand. Custom module development also meant a longer initial build timeline compared to configuring an existing platform. The tradeoff was worth it: the system actually fits how the business works, rather than forcing the business to fit the software.

Constraints

No dedicated IT staff meant the system had to be manageable by the existing team after handoff. Budget was real — this is a profitable but lean operation, not a VC-funded startup. The build had to be comprehensive enough to replace everything but modular enough to phase in without shutting down operations.

Core ERP & Data Migration
What was done

Stood up Odoo 17.0 with Sales, CRM, Inventory, Purchasing, Manufacturing, and Accounting modules. Migrated client data, pricing tiers, and product catalog from the existing patchwork of spreadsheets and legacy systems.

Why it mattered

Nothing else could be built until the foundational data was clean and centralized. You can't build custom stores on top of bad data.

What it replaced

Standalone accounting software, spreadsheet-based client/pricing records, manual inventory tracking

Custom Client Stores & Approval Workflows
What was done

Developed the WD User Stores module — per-client storefronts with individual product catalogs, negotiated pricing, and configurable approval chains. Built the Wells & Drew Quotation module for consultative pricing on custom jobs.

Why it mattered

This is the core of Wells & Drew's business model. Without per-client pricing and approval workflows, the ecommerce layer would have been useless for their actual clients.

What it replaced

Phone/email order intake, manual pricing lookups, verbal approval chains

Ecommerce & Web-to-Print
What was done

Built the public-facing website and ecommerce layer on Odoo. Integrated PitchPrint for web-to-print customization — clients can preview and customize stationery designs before ordering.

Why it mattered

The website needed to serve two audiences: new prospects seeing the brand for the first time and existing clients logging in to reorder. PitchPrint bridged the gap between 'browsing' and 'specifying a print job.'

What it replaced

Static brochure website with no ordering capability

Shipping & Fulfillment Integration
What was done

Integrated Shipstation Odoo Shipping Connector with multi-carrier support (UPS, DHL, FedEx). Shipping labels generate automatically from confirmed orders.

Why it mattered

Manual shipping label creation was eating 20+ minutes per order for a team that ships hundreds of orders weekly. Automation here had an outsized impact on daily capacity.

What it replaced

Manual carrier website visits for label creation, copy-paste address entry

Accounting Localization & Go-Live
What was done

Configured US-localized accounting (NACHA payments, 1099 reporting), connected bank feeds, and ran parallel operations for 6 weeks before full cutover.

Why it mattered

Accounting migration is where implementations go to die. Running parallel ensured the numbers matched before anyone flipped the switch.

What it replaced

Standalone accounting software disconnected from sales and inventory

Execution

Odoo 17.0 (Community + Enterprise) WD User Stores (custom module) Wells & Drew Quotation (custom module) Shipstation Odoo Shipping Connector PitchPrint (web-to-print) Odoo CRM Odoo Inventory Odoo Manufacturing Odoo Accounting (US localization) Odoo Purchasing Odoo Project Management Odoo Timesheets Odoo Email Marketing Odoo Live Chat
Technical decisions

Odoo 17.0 was chosen over 16.0 for its improved web framework and better ecommerce performance. Custom modules were built as proper Odoo add-ons (not monkey patches) so they survive upgrades. The WD User Stores module uses Odoo's access control framework rather than reimplementing permissions — less code, fewer bugs. Product BOMs were structured to reflect actual manufacturing steps, not just finished goods, which means inventory depletion tracks reality.

Turning points

The moment that changed the project trajectory was realizing the approval workflow couldn't be bolted onto standard Odoo ecommerce. It needed its own module. That decision added three weeks to the timeline but eliminated what would have been months of workaround maintenance. The second turning point was PitchPrint integration — initially scoped as a phase 2 feature, but pulled forward when early client testing showed that seeing a preview before ordering dramatically reduced revision requests.

Unexpected issues

Product data migration was messier than expected. Pricing tiers had accumulated exceptions and one-off deals over decades, some of which contradicted each other. Cleaning that data took longer than building the quotation module itself. The Shipstation connector also required custom handling for Wells & Drew's packaging logic — standard carrier rate shopping doesn't account for the fact that embossed stationery can't be folded, which changes box dimensions and shipping costs.

Wells & Drew has been in the specialty printing business since 1855. That’s not a typo. They were making engraved stationery before the lightbulb existed. Their client list reads like the yellow pages of professional services — law firms, accounting firms, real estate brokerages, financial institutions — and their 98% five-year retention rate tells you everything about how seriously they take the relationship. This is not commodity printing. Every order involves negotiated pricing, custom specifications, and often a conversation.

The problem wasn’t that Wells & Drew lacked technology. It was that they had too much of it, none of it connected. Orders came in through one system, inventory lived in another, accounting was somewhere else, and the website was essentially a brochure with a phone number. For a company managing 150,000+ professional clients with tiered pricing and approval workflows, this meant a staggering amount of manual coordination. Steven Houser, the company’s president, knew the operation was held together by institutional knowledge and spreadsheets — and that neither of those scales.

Parameter’s approach wasn’t to digitize the existing process. It was to rethink which processes actually needed to exist. The core build centered on Odoo 17.0 with several custom modules: WD User Stores (per-client storefronts with built-in approval chains), a custom quotation system for consultative pricing, and tailored product attributes and bills of materials that reflect how specialty printing actually works. Shipstation integration gave them multi-carrier shipping without leaving Odoo, and PitchPrint brought web-to-print customization directly into the ordering flow. On top of that, the full ERP suite — CRM, inventory, manufacturing, purchasing, accounting, project management, timesheets — replaced the patchwork of disconnected tools.

The trickiest part was the client store architecture. Wells & Drew’s B2B model means different clients see different products at different prices, and many organizations require internal approval before an order ships. Building that logic into Odoo meant custom module development, not configuration. The quotation system had similar complexity — pricing isn’t a lookup table when you’re quoting foil stamping on 120lb cotton stock with a custom die. Parameter built the system to handle that nuance without flattening it into something generic.

The result is a single platform that runs the business end to end. Orders flow from the client-facing store through approval, into production, out through shipping, and into accounting — without anyone re-keying data or toggling between tabs. For a 13-person operation, that’s not a nice-to-have. It’s the difference between spending the day on work and spending the day on workflow.

Results

24 Custom Client Stores Deployed Per-client storefronts with individual pricing tiers and approval workflows
68% Order Processing Time Reduction From intake to production — eliminated re-keying and manual handoffs
1 replaced 6 Tools Consolidated Website, ecommerce, CRM, inventory, accounting, and shipping unified in Odoo
41% Client Self-Service Order Rate Clients placing orders directly through their custom stores without sales rep involvement
94% Shipping Label Automation Labels generated automatically via Shipstation — manual entry only for non-standard shipments
Operational improvements

The most significant change is that orders now flow from client-facing store through production to shipping without anyone re-entering data. Client self-service handles routine reorders, freeing the sales team for consultative work. Inventory updates in real time as manufacturing consumes materials, so purchasing decisions are based on actual numbers instead of estimates. Accounting closes faster because transactions originate in the same system — no reconciliation across platforms.

Business impact

Wells & Drew can now onboard new clients with their own store in hours, not weeks. The sales team spends time on high-value consultative work instead of processing routine reorders. Manufacturing has visibility into incoming orders before they hit the floor. The company is operationally positioned to grow the client base without proportionally growing the team — which, for a 13-person operation, is the whole point.

Parameter gave us a system that keeps that personal touch while letting our clients help themselves when they want to. That's not something we thought was possible.

Blake Houser, President, Wells & Drew

Takeaways

Who this applies to

B2B manufacturers and specialty producers with client-specific pricing, approval workflows, and consultative sales processes. Particularly relevant for companies that have outgrown spreadsheets and point solutions but aren't large enough to justify enterprise ERP pricing. If your clients need their own storefront — not just a login — this pattern applies.

Patterns observed

The biggest efficiency gains came not from any single module but from eliminating data re-entry between systems. When inventory, sales, manufacturing, and accounting share a database, a whole category of daily work just disappears. The second pattern: clients adopted self-service faster than expected when the interface actually reflected their specific relationship (their products, their prices, their approval rules). Generic portals get ignored. Personalized stores get used.

When to consider this

When your B2B operation has outgrown phone-and-email ordering but your pricing model is too complex for standard ecommerce. When you're spending more time managing tools than managing the business. When your team is small enough that every hour of manual process has a visible cost. When your clients need to feel like they have their own storefront, not a generic shopping cart.

Odoo

Full platform implementation — ERP, ecommerce, custom module development, third-party integrations, and ongoing management. This was a ground-up build, not a migration from another Odoo instance.

Next Step

Want this kind of clarity on your own stack?

If your site, store, or business system is carrying silent risk, we can map the problem, choose the right approach, and turn it into something steadier.