A leading European manufacturer of premium outdoor products for the home sought to capture a share of the lucrative U.S. consumer market. Their go-to-market strategy hinged on securing placement in national big-box retailers, being a fast path to widespread brand recognition and sales volume.
Problem
Since the company was new to the U.S. market, they started with a small, lean team. They quickly found success with their first large retailer. With success came a challenge: how could they process hundreds of manual orders a week while simultaneously implementing the chain’s required EDI transmission of information?
MI’s Solution
MI assisted the company by immediately taking on the manual data entry, reviewing all new vendor information from the customer, and working with a third-party EDI solutions partner to get the company in full compliance and ready to take on more customers. Over time, we assisted with the transition to a full ERP with more robust EDI connections and further automation of the order-to-cash workflow.
Deep Dive
First Things First – What is EDI?
Electronic Data Interchange (EDI) is at its core, a direct line from one company’s system to another’s. Instead of printing purchase orders, faxing invoices, or forwarding email attachments—all of which demand extra human touchpoints—EDI moves those same documents computer‑to‑computer in a universally accepted digital format.
That single shift rewires the entire order‑to‑cash cycle. Purchase orders (850s), invoices (810s), and advance‑ship notices (856s) post straight into their prescribed data fields, where downstream processes—picking, packing, billing—trigger automatically. Processing cycles shorten, data‑entry mistakes all but disappear, and overhead drops; most firms report transaction costs falling by 35 percent or more and processing times improving by roughly 61 percent once full EDI integration is established2.
For MI’s client, the stakes went beyond internal efficiency. Manually keying hundreds of orders each week was time‑consuming and error‑prone, but the larger issue was external compliance: their flagship big‑box customer required EDI. Without a functioning feed, future orders would stop. Implementing EDI, then, was not optional—it was the price of admission for staying on the shelf and deepening the relationship.
A Huge Opportunity
Big-box retailers run on precision. The size of the supplier is irrelevant—if you want shelf space, you play by their rulebook and meet every technical checkpoint. The company understood the stakes: getting onto those shelves can take years, yet a perfectly timed, innovative product gave them a rare fast‑track. The first purchase orders were a trial not only of sell‑through potential but of operational muscle—could a lean U.S. subsidiary hit shipping windows, meet fill rates, and transmit flawless documents on schedule? Failure would have slammed that door shut.
Inside the subsidiary, the initial three hires were all more sales‑leaning in their roles. When the retailer’s trial orders arrived—more than four hundred PDF purchase orders—the company asked Management inSites to step in. MI’s immediate task was tactical: key every order into QuickBooks Online (QBO) so product could leave the 3PL warehouse within the required shipping window. At the same time, we flagged the obvious risk: manual entry at this volume was unsustainable.
Therefore, MI’s next move was a deep dive into the retailer’s 200‑page vendor manual and the supplemental EDI implementation guide. In an ideal world, every data segment, qualifier, and shipping‑label requirement should be mapped against the company’s internal systems. But that level of integration requires a much more robust software solution, which the company was not ready for. The retailer did offer a simple solution for smaller companies: Sterling Web Forms acted as a go-between. Using Sterling, the retailer would push each 850 directly into the company’s Sterling inbox. This automated part of the workflow—that of the retailer. From there the workflow remained painfully manual for the company. The team downloaded a PDF for every order, and re‑entered those details as an invoice in QBO. Next, that invoice had to be rekeyed back into Sterling and finally transmitted to the retailer’s gateway.
To automate the process as much as QBO would allow, MI brought in SPS Commerce, a third‑party EDI provider able to integrate more deeply. SPS imported the 850 data, generated the matching invoice inside QBO, and then pushed the completed 810 back through its own network to the retailer. Its Fulfillment platform mirrored Web Forms but added “auto‑sourcing” options that cut double entry to a minimum while additional connections were made. Step by step, the ad‑hoc paperwork queue transformed into a controlled, traceable, and more automated order‑to‑cash flow—exactly what the retailer’s compliance team required and what the company needed to scale with confidence.
Acting as an Internal Company Specialist
During this process, MI stepped in as the company’s in‑house EDI steward, bridging five moving parts at once: the retailer’s B2B‑onboarding team, SPS Commerce, QuickBooks Online, a fast‑growing group of order processors on the office floor, and multiple 3PL warehouses. Our consultant ran meetings and carried out tests with SPS Commerce to ensure the data input and output from QBO went to the right fields, met any specific requirements the retailer had for the company, and matched the data the company needed to record in its systems for its own purposes.
Sometimes, this included asking SPS Commerce for special mapping for data the retailer’s purchase orders didn’t supply—so the invoices generated in QBO would feed later processes automatically. For example, certain stores for the retailer were assigned to one sales rep, others to another. We had a rule built that read the ship‑to state on each PO, inserted the correct rep code into a new QBO field based on location, and turned month‑end commission reports from a manual chore into a one‑click query. Making that happen took deep knowledge of QBO, a clear brief to SPS, and a full view of the client’s procedures beyond basic order processing.
Inventory complexity added another layer. MI created a second custom field in QBO for SPS to map that looked at which 3PL warehouse should ship each order based on ship to address and product code. In parallel, we proposed the next layer of automation: linking SPS Commerce directly to each warehouse. That would reduce communication between the order staff and the warehouse (emails with packing lists and further instructions) and ensure the advance ship notice (EDI 856) would fire automatically as soon as the load left the warehouse. However, this was put on hold due to the limitations of the company’s selected 3PLs’ internal systems.
Furthermore, by serving as a technical link, MI’s consultant was able to distill the complicated discussions about systems integrations into detailed process-driven procedures for the daily office staff to follow. Illustrated manuals walked office staff through the full order‑to‑cash cycle: how to recognize a clean EDI feed, where to check if a document rejects, how to use Fulfillment correctly, and whom to notify when an automation stalls. This documentation allowed order processors to keep shipments moving even while MI tested new maps or chased down edge‑case errors.
As each new trading partner—whether a brick‑and‑mortar chain or an e‑commerce marketplace—came aboard, MI repeated the same EDI onboarding cycle. While every partner required the core EDI documents, some added extras such as the Purchase Order Acknowledgement (855) or Remittance Advice (820), and all of them wanted the data in a slightly different way. At the same time, the company’s operation itself kept evolving: product lines expanded, packaging units changed, shipping shifted from single‑store drop‑shipments to full truckloads into regional distribution centers, new sales reps joined, and 3PL relationships changed. Each of these moves demanded continuous coordination with the retailer’s EDI‑onboarding teams and SPS Commerce, along with prompt revisions to the step‑by‑step process guides that MI maintained for the office staff.
Throughout these tactical wins, MI kept an eye on system fit, auditing every system each trading partner used—looking for points where smarter automation, tighter integrations, or workflow tweaks could squeeze more speed and accuracy out of the entire order‑to‑cash chain. That ground‑level assessment surfaced a bigger insight: QuickBooks Online had reached its limits.
Outgrowing QBO
QuickBooks Online is a solid launchpad, but it was never intended for the large transaction volume, or the inventory complexity the company now faced. At this point, the company needed to track inventory in multiple 3PL locations, Amazon’s FBA warehouses, and ocean freight in transit from the parent company in Europe, as well as the kits the U.S. warehouses were building for specific U.S. customers. Add the upcoming shift to domestic manufacturing and the limits of QBO became untenable: the business needed a true ERP.
As a solution, the company sought to replicate its highly customized European SAP software for the U.S. market. However, the European template was built for distributor sales, not direct-to-retail fulfillment the U.S. subsidiary was focusing on. Success therefore hinged on two non-negotiables. First, SAP consultants in the home country needed to fully grasp the U.S. subsidiary’s workflows in detail. Second, and most importantly, the transition from QBO to SAP had to happen with minimal disruption. As a seasonal business, timing was everything and the company couldn’t afford to lose the momentum it had earned with its key retail customers.
Implementing SAP
Again, MI acted as the critical bridge between teams as the company’s de facto QBO, EDI, SPS Commerce, and order process expert. We worked shoulder-to-shoulder with the European SAP consulting firm, walking them through the U.S. order-flow in detail—how EDI data was coming in, where it was stored, what was still manual, which segments mattered for each retail partner, what packaging units differed by customer, and more. The consultants were primarily liaising with the parent company’s European team, but to build a platform that actually worked in the United States, they had to understand the U.S. business as a whole, particularly how order processing worked within the U.S. subsidiary and the clock-tight shipping commitments it was up against.
That meant every ounce of prior EDI work had to be rebuilt. New SAP implementation specialists at SPS Commerce needed a crash course on the company’s customer‑specific mapping, and how SPS Fulfillment and QBO had been working together previously. Meanwhile, the company’s SAP consultants required a deep dive into each document type—who was responsible for what, and how the data had to flow once U.S. manufacturing came online. The system had to satisfy today’s retail scorecards and tomorrow’s in‑house production runs.
The transition was successful, but it was labor-intensive. It involved many early morning calls with the parent company that evolved from strategic planning to troubleshooting. MI was there to translate both language and technical nuance so that every stakeholder grasped the requirements set forth by U.S. trading partners. While the SAP consultants in Europe were responsible for bulk data loads and outbound test transmissions, MI’s role was to interrogate every transaction that came back, flag mismatches, and provide feedback. When it came time for the SAP launch, MI was onsite and ready to step in to offer additional support if needed. As the company continued to grow in size, MI was eventually able to help train one of the company’s new direct hires to assume MI’s role as the in-house specialist, ensuring the company could continue to onboard new trading partners successfully through SPS Commerce and its SAP system.
Key Learnings
Landing a big‑box account is only the first hurdle; keeping it means delivering quality product on time and hitting every EDI mile‑marker, every time. This company met that challenge by handing the heavy lifting to MI. We took the manual order crush off their plate, connected QBO to SPS Commerce for automation, and turned what could have been a bottleneck into a growth engine.
The results followed quickly: fewer keystrokes, faster cycle times, and data that matched the retailer’s spec on the first pass—freeing the team to pursue new customers instead of fixing old errors. When volume outgrew QBO, MI assisted in the move to SAP, extending the same automation principles to a platform built for scale. In short, the company didn’t just keep pace with big‑box demands; it built the infrastructure to exceed them.