Dispatch milestone: define the operational meaning
Start by describing dispatch milestone through an example from your operations.
Dispatch advice should originate from the milestone agreed with the customer. Picked, loaded and departed may be different warehouse stages. Define which one authorises the message and what is confirmed then, so an outbound communication does not describe a still-changeable plan as a completed physical dispatch.
Partial quantities: establish the actual scope
Reviewing partial quantities separates available functions from remaining work.
Link ordered lines to actual dispatched quantities while retaining references. Where one order produces several departures, the customer must distinguish them without losing the parent relationship. Check how the WMS identifies these dispatches and what identifiers the receiving system needs to recognise each event correctly.
Order reference: identify evidence of completion
For order reference, distinguish sending information from actually using it.
Partial supply, substitutions and picking differences need explicit rules. Do not populate actual dispatched quantity from the plan when the warehouse has not confirmed that outcome. Customers need what happened and enough context to interpret it, rather than apparently complete information generated by copying an earlier expectation.
The customer places the order. The warehouse executes it in the WMS.
A logistics order needs recognisable items, units, recipients and references. Define correction and completion of an already reported dispatch and what information the customer needs. A second departure is not necessarily a correction to the first. Link that distinction to the WMS operational model and the partner guideline so the receiving application can interpret the additional message correctly.
A new customer should not automatically mean rebuilding the integration
The WMS may retain a common interface while customers use different documents and rules. Review scope: EDI integration for logistics and warehouses.
An example to frame the decision
Illustrative scenario, not attributed to an actual customer. A logistics provider onboards a customer whose warehouse orders differ from the WMS format. Administration fills in mappings and sends confirmations separately.
Map master data, import WMS orders and generate responses from agreed operational events. Review scope: How an EDI integration is implemented.
Customer orders and warehouse confirmations should match
Useful WMS integration connects what was requested to what was executed. Review scope: EDI integration with your WMS.
Prepare references and master data
Match customer items, units and locations to warehouse references. Identify master data needed before the first exchange and agree the handling of unknown references.
Compare proposals using the same workflow
Give each provider the same incoming document, intended result and required response. Ask how it covers dispatch milestone, partial quantities and order reference. Compare partner adaptation, existing-software tasks and acceptance criteria. Identify the effect of adding documents or changing specifications. A lower price may cover fewer stages; a broader project may include functions you do not yet need. Compare useful scope before comparing price, so the decision reflects the workflow your team actually needs.
Prepare the first discussion
Identify software name and version, partner and available documentation. Collect complete and partial dispatch examples, extractable WMS information and the customer's required response for assessment. State when a confirmation may be corrected. This evidence supports purchasing an outbound information flow with a defined operational outcome instead of an unspecified promise to send warehouse updates.
Where Ediprism fits
Ediprism is EDI integration software between your business systems and third-party applications. Ediprism can connect confirmed warehouse information to responses required by a customer's system. Design should establish the milestone, fields and available interface. It should not imply product traceability or package-level data that the WMS and warehouse process do not actually record in the agreed scope.
Initial cost, continuity and later changes
Separate implementation, third-party services and maintenance. Separate warehouse-event extraction, document creation and customer delivery in the quote. Include WMS work where the milestone must be exposed. Automatic confirmation cannot safely depend on information that currently exists only as a person's screen check without an agreed means of making that result available to the connection.
Customer and warehouse need matching references
An order must correctly identify the customer, item, unit and destination used by the WMS. We assess code mapping and the information that needs to be prepared before accepting the exchange.
Confirm what has actually happened
Dispatch or receipt confirmation should come from an agreed operational milestone. Partial quantities, discrepancies and corrections need explicit treatment instead of assuming every message represents a complete operation.
Multiple customers with individual requirements
Each customer can have a different guideline. The proposal separates common warehouse rules from partner-specific adaptations and defines how new customers, specification changes and document-to-operation traceability are managed.
What we review before quoting
Identify existing software, the partner and its documentation, inbound and outbound flows and available interfaces. This enables agreement on test scenarios, exception ownership and readiness criteria. The proposal should reflect adaptations needed for the specific exchange.
Confirmations tied to work actually completed
Receipt or dispatch responses are defined from the appropriate WMS event. Partial quantities, discrepancies and corrections need agreement so the customer receives information reflecting the actual operation.
Inventory and orders are different flows
Orders, confirmations and stock communications have different purposes and frequencies. Scope identifies included flows, the authoritative system and how discrepancies between applications are resolved.
What we need to assess the connection
Software identity and version, available interface documentation and an anonymised example exchange. Permissions, test environments and responsibilities are reviewed with the vendor or developer. Connectivity is confirmed by scope; brand compatibility is not claimed without verification.
A first flow with standalone value
For a limited phase, define one document, one partner and one useful operational result. If the warehouse confirms by package while the customer expects line quantities, verify their relationship. Integration needs approved mappings and sufficient data. It should not infer package contents from the original ordered quantity where actual preparation can differ, even if that shortcut produces a complete-looking outbound document.
References that help investigate exceptions
Users reporting differences need to locate the corresponding message and operation. Support needs the specific dispatch as well as the order reference. Agree who reviews quantity disputes and what WMS evidence is available. Transmission identifiers help investigation, but operational staff need to find the physical movement behind the confirmation to explain the discrepancy to the customer.
Distinguish objectives from verified capabilities
A business need describes the result sought but does not prove the system has every required function. At cutover, review open orders awaiting outbound confirmation. Establish the route for each response and prevention of repeat reports. The new connection must respect operational history instead of treating every visible dispatch as newly completed simply because it is being read for the first time by the integration.
Decide the next step
Identify the unresolved question and information needed to answer it: perhaps an ERP interface, amendment meaning or customer response. Measure changed work using confirmation samples: data staff copy and differences they validate before responding. This assesses scope without an arbitrary savings claim and identifies controls that should remain because they depend on a warehouse owner's decision rather than merely moving information between two applications.
1. Identify the exchange
Capture the business need, partner specification and existing system. Confirm the result each document should produce and the data it requires.
2. Agree the solution and ownership
Define interfaces, mappings, validation and responses. Responsibilities across Ediprism, your team, software vendor and partner must be documented alongside prerequisites.
3. Test realistic scenarios
Agree inbound and outbound examples, amendments, retries and exceptions. Testing verifies final-system data and partner responses. Timing also depends on access and third parties.
4. Prepare go-live and continuity
Determine monitoring ownership, incident escalation and maintenance before operation. Version and specification changes need a review, testing and acceptance process.
A module in your existing software
A module may fit if it covers required documents, partners, versions and business rules. Ask what is included and what needs configuration or development. Check the effect of adding customers or changing specifications, since fit depends on scope and maintenance.
Custom integration development
This can fit when your team intends to build and maintain the workflow and understands the systems and partner requirements. Include interpretation, mapping, responses, tests and subsequent changes. The first transmission is not the whole project: identify incident ownership and documentation responsibilities.
An integration layer such as Ediprism
This is an option when you want to connect partner formats to existing systems while separating exchange adaptation from business logic. Assess Ediprism by message coverage, available interfaces and intended operational results. Scope should identify adaptations and ownership shared with your software vendor.
Compare offers on the same basis
Provide the same scenario to each provider: document, partner guideline, software and required result. Test complete and partial dispatches and a correction after initial confirmation. Check message counts, quantities and links to the external order. Correct transmission can still misrepresent operations if it duplicates a departure or reports the same shipped quantity twice under references the destination treats as separate events.
An exercise to evaluate the proposal before buying
Assessment scenario; not results from an actual customer.
Use an order with several lines and a dispatch covering only part of demand. Identify the warehouse milestone confirming departure and available information. Show links between supplied quantities, customer reference and specific dispatch. Do not populate advice from the full order when that is not the confirmed warehouse result.
Add another dispatch and a correction to the first. Check how the recipient distinguishes new supply from rectification without counting quantities twice. If the WMS identifies packages and the customer uses lines, verify the documented relationship and declare unavailable detail.
Request evidence connecting order, confirmed departures, emitted document and known recipient outcome. Include investigation and correction owners. This compares partial-dispatch handling against actual execution rather than treating advice created at order entry as equivalent to a message generated from confirmed warehouse activity.
Reference documentation
Partner and system specifications define the project. These references describe the framework, not Ediprism compatibility or certification.
Before you choose a provider
How do I apply this guide to my case?
Identify your software, partner and intended result. Assessment should review dispatch milestone, partial quantities, order reference using examples and available interface conditions.
How do I compare providers?
Provide both with the same document, system and intended result. Compare workflow coverage, interfaces, responses, implementation, support, changes and cost.
How much does integration cost?
Cost depends on partners, documents, interfaces, rules and tests. Separate implementation, adaptations, third-party costs and maintenance.