Business systems, connected cleanly.
P2 Business Solutions builds practical integrations, ERP workflows, automation tools, and reporting systems for companies that need their data to move correctly the first time.
- Odoo
- A2000
- NetSuite
- Cin7
- Finale
- Elastic B2B
- Shopify
- SPS Commerce (EDI)
- Azure Data Factory
- AWS Lambda
Three specialties, one philosophy: it has to actually work on Monday.
We're a small team handling operations and IT for businesses too big for spreadsheets and too small for a CIO. The three lines below are how we think about scope — but real projects bend across all three, because real businesses don't separate ERP from integrations from the people running them.
ERP migrations & implementations.
Odoo, A2000, NetSuite, Cin7, Finale. Discovery, data migration, configuration, integrations, training, cutover, hypercare. We do the 70% of the work that isn’t "clicking around in the system."
How we run an ERP project →B2B and channel rollouts that connect to your reality.
Elastic, Shopify B2B, marketplaces. Catalog, pricing, orders, customers, ATS — synced from whatever system of record you have, however many you have.
How we run B2B integrations →The plumbing nobody else wants to touch.
EDI (SPS Commerce 850/810/856), Shopify, channel sync, shipping and payment integrations, ADF and AWS Lambda pipelines, and the reporting layer that ties it all together.
How we work →Odoo migrations that go live and stay live.
Odoo is genuinely good — and a great Odoo implementation is the work that happens around the system: scoped well, sequenced well, with data migration treated as the real work it is. Here's how we set you up to thrive on it.
(yes, even the ones with 20 years of crusty data.)
An ERP project is mostly the work that doesn't show up in the demo.
Most Odoo quotes cover configuration. The rest — discovery, data cleanup, EDI mapping, channel integrations, UAT, training, hypercare — is the work that turns a system into an operation. We've already done it, on systems that look a lot like yours.
Configuration only. Assumes you have someone internal to map processes, clean data, build integrations, and own the cutover.
Discovery, data migration, EDI, channel integrations, UAT, training, go-live, hypercare. The work that decides whether the project succeeds.
Seven phases. Real hours. A clear runway to go-live.
Hours below are estimates from a recent mid-market apparel migration. Manufacturing implementations look similar — different complexity in BOMs and routings instead of EDI and channels.
Discovery & Process Design
Map current operations end-to-end. Identify what to replicate, what to fix, what to retire. Output: a scoped SOW you can hold us to.
Data Migration
Customers, products, variants, BOMs, pricelists, inventory, history. Cleaned, validated, mapped. Imports rehearsed before cutover.
Configuration
Sales, purchasing, inventory, accounting, pricing, manufacturing, multi-warehouse. Set up to match how you actually operate.
Integrations
EDI (SPS Commerce 850/810/856), Shopify, B2B platforms, shipping carriers, payment gateways, MES if applicable. Built, monitored, documented.
Testing & UAT
Real scenarios with your team and your data. Confidence in every flow before it touches a customer.
Training & Change Management
Role-based training, written SOPs, recorded sessions. Your team using the system confidently before go-live.
Go-Live & Hypercare
On-site or on-call through cutover and the first weeks of operation. We stick around until the system is genuinely running on its own.
Your B2B platform is only as good as what's behind it.
Elastic is a great B2B storefront — but it doesn't run your business. Your ERP does. Whether your system of record is Odoo, A2000, Cin7, Finale, or something else, we move the right data to Elastic, on the right cadence, in the right shape, so your storefront actually reflects what you can sell.
Multiple source systems? We design a clean integration layer that keeps each feed reliable and auditable.
Modern ERP, fully integrated. Native API access.
Apparel-focused legacy ERP. We've built deep integration patterns.
Inventory + ERP for product-driven brands. SaaS API.
Inventory ops platform. REST API, multi-channel data.
What we ship for Elastic clients
Catalog feeds
Products, variants, attributes, images, pricelists. Built once, updated automatically. Lens material normalization, customer-specific pricing, regional logic — handled.
Order sync
Orders flow into your ERP with the right warehouse, terms, and ship-via mapped per customer. Fulfillment, tracking, and invoices flow back.
Customer onboarding
Account creation, pricing tier assignment, region-specific custom fields. New B2B customers using the storefront within hours, not weeks.
ATS & inventory
Real-time available-to-sell exposed to buyers — across multi-warehouse inventory and pre-allocations. No more overselling on the B2B side.
Decades of operational scars, distilled into systems that just work.
Apparel, manufacturing, and wholesale aren't sectors we picked up last year. We've been deep in the data models, EDI specs, BOM hierarchies, variant matrices, channel reconciliation, and order routing for these businesses for years. It means we walk in knowing the questions to ask — and a lot of the answers.
Apparel
DTC, wholesale, and B2B brands navigating channels, retailers, and inventory complexity.
- EDI 850 / 810 / 856 — SPS Commerce, drop-ship vs DC routing, retailer-specific mappings
- Variant matrices — style / color / size with proper data models
- MAP enforcement — order-line tracking, retailer behavior alerts
- ATS — pre-allocations, reservations, multi-warehouse routing
- Channel orchestration — Shopify, B2B, wholesale, marketplaces
Manufacturing
Make-to-stock, make-to-order, or both. Odoo's manufacturing module is a real strength — when configured right.
- BOM hierarchies — phantom, kit, and multi-level structures
- Work orders & routings — by-product handling, scrap, rework
- MRP — demand-driven planning, reorder rules, kanban
- Lot / serial tracking — with full traceability across operations
- Quality control — inline inspections, holds, COA generation
Wholesale & B2B
Wholesalers, distributors, and B2B sellers connecting digital storefronts to legacy systems.
- Multi-tier pricing — customer-specific pricelists, contract pricing
- B2B platform integration — Elastic, custom Shopify B2B, marketplaces
- Customer-specific catalogs — assortments, restrictions, branded portals
- Drop-ship vs DC — per-customer rules, cost-to-serve aware routing
- Pricelist engineering — quantity breaks, promotional, region-specific
Proof, not promises.
A few representative projects. Names available under NDA on request — but the scope, scale, and outcomes are real.
Apparel wholesaler · Elastic + Odoo
Catalog, pricing, and order sync between Elastic B2B and Odoo. Customer onboarding flow, region-specific custom fields, real-time ATS exposure to buyers.
Eyewear brand · Elastic + A2000
Bridged a legacy A2000 ERP to a modern B2B storefront. Custom catalog feeds, order and fulfillment sync, MAP-aware retailer pricing, no ERP replacement required.
From discovery call to running on its own.
We don't sell open-ended retainers, and we don't bill hourly. Every project runs on a fixed-fee SOW with a defined timeline, defined deliverables, and a defined go-live date — so you know exactly what you're paying for and what you're getting.
Discovery
2 weeks · paidTwo-week paid engagement. Process map of current operations, gap analysis against the target system, scoped proposal with fixed pricing.
Plan
2 weeksFixed-fee SOW signed. Integration architecture, data migration plan, project schedule, named owners on both sides.
Build
8–14 weeksConfiguration, data migration, and integration work in parallel sprints. Weekly status, weekly demos, weekly decisions. Predictable rhythm all the way through.
Validate
2–3 weeksUAT with your team on your data, against the scenarios that actually run your business. Sign-off before any cutover happens.
Cutover
1 wk + 4 wks hypercareGo-live with hands-on support. Four weeks of hypercare during which we own everything that comes up. Then a clean handoff.
A few opinions, openly held.
We don't pretend to be neutral about how this work should go. Here's what shapes every project we run.
Fixed-fee SOWs, always.
Hourly billing makes both sides squirm. Fixed scope, fixed price, defined deliverables — easier for everyone, including future-us.
Spreadsheets aren’t an ERP.
We say this with love. Some of the best businesses we know run on heroic spreadsheets. We’re here when those become the bottleneck.
Your team using it is the only metric.
A perfectly configured system nobody touches is a failure. A slightly imperfect system everyone uses confidently is a win.
ERP and integrations aren’t separable.
Real businesses don’t have separate departments for “the system” and “the connections.” Neither do our SOWs.
Boring Mondays are the goal.
Especially the first Monday after go-live. If we did our job right, the system fades into the background and people get on with their week.
If a process is hard to explain, fix it first.
We’ve never met a tangled process that got better when migrated as-is. The discovery phase exists for good reason.
Already working with us?
Sign in to the client portal for project documents, integration health dashboards, and support tickets — everything tied to your engagement, in one place. Subscription required for ongoing access after go-live.
Outgrowing your current ERP, your B2B platform, or both?
30-minute discovery call. We'll listen, ask hard questions, and tell you honestly whether we're the right fit. No deck, no pitch, no hard sell — promise.
Will Thompson — based in Summerville, SC.
I've spent years inside ERP migrations and integration projects across apparel, manufacturing, and wholesale operations. P2 is intentionally small: you work directly with the person designing, building, and supporting your system. The goal is simple — clear scope, practical execution, and a team that feels in control after go-live.