Sample requests stalled deals — CRM to ERP/WMS & carrier APIs for predictable fulfillment

Overview

A food technology supplier was losing momentum on deals because sample requests overwhelmed the lab and shipments slipped. Requests arrived through emails and spreadsheets, inventory checks were manual, and shipping labels were created off-system. Intelligex orchestrated sample fulfillment from within the customer relationship management (CRM) workflow, adding inventory checks, priority rules, and auto-generated shipping labels with status updates. The lab worked from a clear queue, samples shipped predictably, and both reps and clients received timely notifications, which reduced manual tracking and missed commitments.

Client Profile

• Industry: Food technology and ingredients
• Company size (range): Mid-market with regional sales and centralized R&D
• Stage: Established growth with expanding enterprise accounts
• Department owner: Sales & Business Development (Sales Operations)
• Other stakeholders: R&D Lab, Quality Assurance (QA), Regulatory, Logistics/Warehouse, Customer Success, Finance, IT/Security

The Challenge

Sample requests arrived in bursts during late-stage evaluations. Reps captured details in different formats, the lab triaged by inbox, and warehouse staff did their best to find stock or prepare pulls for custom blends. Inventory for sample sizes was inconsistent, and the team lacked a single view of available lots, allergen flags, or special handling needs. Shipping was handled last, with addresses and service levels retyped into carrier portals. When requests piled up, priority became subjective and promised dates were missed.

Sales could not pause new opportunities, and leadership did not want to replatform core systems. The CRM housed opportunity context, an Enterprise Resource Planning system (ERP) or Warehouse Management System (WMS) tracked stock, and the lab maintained formulation notes in its own system. The ask was to coordinate these pieces into a reliable sample pipeline: capture requests in a consistent way, check inventory and constraints up front, apply clear priority rules, generate shipping labels automatically, and keep everyone informed without adding more tools for the field to learn.

Why It Was Happening

Work was fragmented across teams and systems. Sales created requests without visibility into stock or lab capacity. The lab received incomplete information and spent time chasing clarifications. Warehouse staff worked from emails, which led to picking errors or delays when lots had special restrictions. Shipping details were manually rekeyed, which introduced mistakes and slowed final handoff.

There was also no governance for priority and compliance. High-value deals, expiring samples, and allergen-sensitive items all ended up in the same queue. Review for labeling, storage conditions, and documentation happened informally. Without an audit trail and a clear owner for each step, escalations landed late and relationships with buyers suffered when samples arrived off-schedule or with missing paperwork.

The Solution

We implemented a sample orchestration layer that lived inside the existing CRM and connected to inventory and shipping tools. Requests were captured through a guided intake, validated against stock and constraints, and routed into a lab and warehouse queue with explicit priority. Shipping labels and documents were generated automatically, and status updates flowed to reps and clients. Sensitive items triggered QA and Regulatory review before release. Nothing was ripped out: the CRM remained the front door, ERP/WMS remained the source for stock and lots, and carrier systems handled labels.

• CRM intake with standardized fields for product, lot preference, sample size, allergens, temperature needs, and promised date
• Inventory and lot availability checks in ERP/WMS, including substitute sample SKUs and reserved stock rules
• Priority engine that considered deal stage, account tier, promised date, lab workload, and regulatory flags
• Automated task creation for lab prep and warehouse pick/pack with role-based queues
• Shipping label generation through carrier APIs (for example, UPS Developer or FedEx) and packing slips with lot and storage notes
• Workflow logic in CRM using Salesforce Flow to coordinate steps, hold releases for review, and update statuses
• QA/Regulatory gates for allergen labeling, storage instructions, and documentation requirements, including traceability to product identifiers such as GS1 GTIN
• Customer and rep notifications with tracking links and expected delivery windows
• Exception queue for out-of-stock items, custom blends, or special handling, with human-in-the-loop approvals and alternatives
• Dashboards showing request volume, aging by priority, lab workload, and on-time performance

Implementation

• Discovery: Mapped the end-to-end sample journey from request to delivery; inventoried CRM fields, ERP/WMS stock data, lab prep steps, and carrier label processes; identified compliance checkpoints for allergens and special storage; collected the most common request patterns by segment.
• Design: Defined the standardized intake form and required data; modeled the priority rules and ownership at each stage; specified ERP/WMS queries for stock, lots, and substitutions; outlined QA/Regulatory gates and documentation; designed notifications and status models visible to Sales and customers.
• Build: Configured CRM flows, custom objects for sample requests, and queues for lab and warehouse tasks; built integrations to query inventory and reserve stock; implemented label generation via carrier APIs and attached documents back to the request; configured QA/Regulatory approval steps; added audit fields and reason codes for exceptions.
• Testing and QA: Ran pilots across representative product lines and handling types; validated inventory checks and substitutions; verified label formatting, packing slips, and tracking links; exercised QA gates for allergen and storage documentation; tuned priority rules to avoid thrash.
• Rollout: Launched observe-only mode where the workflow created tasks and recommendations while teams continued their manual process; after validation, enabled reservations, approvals, and label printing; phased in customer notifications by segment to build confidence.
• Training and hand-off: Delivered short guides for reps on request intake, for lab on prep tasks and approvals, and for warehouse on pick/pack and label handling; documented exception playbooks and escalation paths; assigned stewardship for priority rules and compliance content; established a human-in-the-loop review for custom blends and unusual handling.

Results

Sample shipments moved from ad hoc to predictable. Reps could see when a request would leave the building, and customers received tracking and storage notes without back-and-forth. Inventory issues surfaced early with suggestions for substitutions or partial shipments, which protected promised dates. The lab focused on prep rather than sorting the inbox, and the warehouse worked from clear pick lists with labels and documents preattached.

Missed commitments and manual follow-ups declined because the workflow enforced priority and compliance in sequence. QA and Regulatory approved sensitive items before packing, so shipments contained the right documents and labels. Finance and Customer Success gained better visibility into sample activity on late-stage deals, which made forecasting and customer communications more credible.

What Changed for the Team

• Before: Requests arrived by email with inconsistent details. After: A guided CRM intake captured required fields and validations up front.
• Before: Priority was decided in the inbox. After: Rules set clear order based on deal context, capacity, and compliance needs.
• Before: Inventory and lot checks were manual. After: ERP/WMS availability and substitutions were checked automatically during intake.
• Before: Labels were typed into carrier portals. After: Shipping labels and packing slips were generated from the request with tracking attached.
• Before: QA and Regulatory reviews were ad hoc. After: Gated approvals ensured allergen and storage documentation accompanied each shipment.
• Before: Reps chased status by chat. After: Status and tracking updated in CRM with customer notifications.

Key Takeaways

• Coordinate sample fulfillment in the tools teams already use; do not add a separate portal if CRM and ERP can be orchestrated.
• Standardized intake and inventory checks prevent downstream rework and missed dates.
• Priority rules must reflect deal stage, customer tier, and capacity, with an exception path for edge cases.
• Automated label generation reduces errors and shortens the last mile from pick to ship.
• QA and Regulatory review gates protect brand and customer safety while keeping the lab focused on prep.
• Traceability to product and lot identifiers improves audit readiness and accelerates troubleshooting.

FAQ

What tools did this integrate with?
We integrated the CRM for intake, status, and notifications; the ERP or Warehouse Management System for stock, lots, and substitutions; and carrier systems for shipping labels and tracking (for example, the UPS Developer APIs). Workflow coordination and approvals ran through CRM automation, such as Salesforce Flow, and dashboards used the existing business intelligence stack.

How did you handle quality control and governance?
Sensitive items triggered QA and Regulatory gates that blocked release until required labels and documents were attached. Priority rules and substitutions were versioned and owned by named stewards. Every request captured audit fields, including inputs, approvals, lot numbers, and shipment details. Allergen and storage instructions were printed on packing slips and stored with the request record.

How did you roll this out without disruption?
We started in observe-only mode where the workflow created tasks and recommendations while teams continued manually. After confirming accuracy and fit, we enabled stock reservations, approvals, and label generation. Existing systems remained; the orchestration layer made them work together with minimal behavior change for Sales and Operations.

How were cold-chain or special handling needs addressed?
The intake captured temperature and handling requirements. These flagged special packing checklists, documentation, and service levels for shipping. QA and Regulatory reviewed those requests before release, and the label workflow selected appropriate carriers and services based on handling needs.

What about traceability and lot tracking?
Each sample request stored product identifiers and lot numbers from ERP/WMS. Packing slips carried the same identifiers and storage notes. Using standardized product keys such as GS1 GTIN reduced ambiguity across systems, and lot-level data supported audits, customer questions, and any required follow-up.