InPost Lockers and Microsoft Dynamics Business Central
Integration Agency & Consultants
At Cogent2, our AI-powered integration delivery is guided by operators who have managed these systems. We connect InPost Lockers with Microsoft Dynamics Business Central to give the ERP a reliable, real-time feed of shipping and returns data from the parcel network. This provides a clear picture of stock movements, reducing costly fulfilment errors.
Consulting
We connect your InPost Lockers and Microsoft Dynamics Business Central with Smart Lockers and ERP systems, ensuring your technology ecosystem works efficiently. Our consulting services are valuable because our system audit uncovers integration gaps and inefficiencies between InPost Lockers, Microsoft Dynamics Business Central, Smart Lockers, and ERP platforms. This enables our consultants and your team to take decisive action, helping your tech environment run smoothly and efficiently, so you can deliver a great experience to your customers.
Solution Design
Design for InPost and Microsoft Dynamics Business Central focuses on making the ERP the authoritative source for the order life cycle. We prioritise the flow of locker metadata directly into Business Central Sales Orders to ensure shipping labels are generated with correct routing. A key design decision involves the handling of returns. While outbound shipping is often triggered on a defined schedule to facilitate warehouse speed, we typically sync return and uncollected parcel data in a way that ensures financial reconciliation matches physical stock counts before inventory is adjusted. This trade-off ensures reporting accuracy but may require finance to accept a slight lag in intra-day return visibility. This model allows warehouse ops to work from Business Central as their primary interface while finance completes reconciliations with confidence that locker movements match the records.
Managing data flow through the order journey
The integration between InPost Lockers and Microsoft Dynamics Business Central ensures that locker selection data is preserved from the customer order through to final fulfilment. The Sales Order in Business Central typically serves as the source of truth for the order life cycle, capturing metadata such as the locker ID to ensure warehouse teams have the correct routing information for shipping labels.
Data flow follows a defined trigger based on your operating model: - Order Processing: Orders containing InPost metadata are created in Business Central, where locker details are mapped to headers or address fields. - Warehouse Workflow: When a shipment is prepared, the integration requests a shipping label from InPost and posts the tracking number back to the Business Central record. - Status Updates: Fulfilment and collection statuses flow back into the ERP, providing customer service teams with visibility into delivery progress. - Returns Handling: Return events at InPost lockers are used to initiate return records in Business Central, ensuring inventory levels and financial documents remain accurate.
iPaaS
Leveraging IPaaS with SO 27001 and SOC 2 compliance and above ensures secure, efficient integration of InPost Lockers and Microsoft Dynamics Business Central with ERP and Smart Lockers. IPaaS simplifies connecting InPost Lockers, Microsoft Dynamics Business Central, ERP, and Smart Lockers, reducing risk and complexity. Security accreditations guarantee data protection, while automation and centralised management improve reliability and scalability for ERP and Smart Lockers integrations.
Exposing exceptions before they impact customers
Visibility in an integration between InPost Lockers and Business Central goes beyond simple connection monitoring. Problems typically surface as data drift, where a locker selection is captured in the storefront but fails to map correctly to a shipping agent code within Business Central. Without proactive monitoring, these issues stay hidden until a shipment is delayed or a tracking number fails to sync back to the Sales Order.
We focus on identifying these exceptions early in the fulfilment process. This includes monitoring for label generation failures and ensuring that locker collection notifications are triggered by the correct status update in the ERP. By surfacing failures at the record level, your team can resolve mapping errors or API timeouts before they impact the warehouse dispatch queue. This approach ensures that the finance and operations teams have a consistent view of every locker-delivered order, from initial capture to final collection.
Operational manuals for warehouse and finance teams
Handover ensures that your finance, operations, and customer service teams own the day-to-day running of the InPost and Business Central integration. We provide an operational operating model that moves away from technical jargon. Your warehouse team learns to manage shipping label exceptions, while finance is trained on how to reconcile locker-based returns against Credit Memos. We define what to check on a regular basis, such as sync error logs, and who owns each exception type. This documentation is written for the people running the business, serving as a practical guide for resolving data mismatches or uncollected parcel alerts. Training is anchored in your specific configuration, ensuring teams know exactly where locker data lives in Business Central and how it impacts stock availability.
Maintaining data integrity after go-live
Ongoing support focuses on maintaining the integrity of the data flow between InPost and Business Central. We monitor for sync exceptions, such as failed label generations or tracking numbers that do not post back to the Sales Order, which can stall customer notifications. Our team provides operational ownership, ensuring that API changes or locker network updates do not disrupt your warehouse workflow. When issues arise, we prioritise resolving the root cause in the integration layer rather than relying on manual data patches in the ERP. This approach ensures that your inventory levels and financial reconciliations remain accurate without constant intervention from your internal teams. Monitoring typically includes tracking the life cycle of locker returns to prevent stock discrepancies.
Common failures
Mismatched inventory from unrecorded returns
Operational impact: A customer returns an item via an InPost locker, but this event is not synced back to Business Central. This results in physical stock being returned to the warehouse without a corresponding update to system inventory levels, causing stock discrepancies. The finance team is then unable to accurately process Credit Memos and reconcile SKUs, leading to manual stock counts and adjustments.
Prevention / Action: The integration process must treat InPost return notifications as triggers for creating a Sales Credit Memo or Return Order in Business Central. This record should remain open until the warehouse team physically scans the returned item, confirming its condition. Only this final scan should trigger the inventory-level adjustment in Business Central, ensuring the system record reflects physical reality.
Assignment of oversized parcels to lockers
Operational impact: Product dimension data is missing or incorrect in Business Central, allowing customers to select InPost delivery for orders that exceed locker size limits. Warehouse teams pack these orders only to find they cannot generate a valid InPost label, forcing a manual hold. This requires the customer service team to contact the customer for an alternative address, delaying fulfilment and creating a poor experience.
Prevention / Action: Business Central must be the source of truth for all SKU-level dimension and weight data. Before displaying InPost as a shipping option, the integration should validate the cart's total volumetric size against InPost's parcel limits. This requires disciplined master data management and integration logic that queries item records before committing to a fulfilment method.
Missing locker ID on sales orders
Operational impact: The customer's chosen InPost locker ID fails to transfer correctly with the order data into Business Central. This creates Sales Orders with an 'InPost' shipping instruction but no destination, bringing the fulfilment process to a halt. The warehouse team cannot create a shipping label, forcing them to flag the order for manual intervention by the customer service or operations team.
Prevention / Action: The integration's field mapping must make the locker ID a mandatory field for any Sales Order using an InPost delivery service. Implement a validation layer that holds any order missing this data in a separate queue for exception handling. This prevents incomplete orders from entering the main fulfilment workflow in Business Central and allows for proactive resolution.
API rate limiting during peak order volume
Operational impact: During a flash sale or peak trading period, a high volume of dispatch requests overwhelms the InPost or Business Central APIs, triggering rate limits. This stops shipping labels from being generated, creating a fulfilment bottleneck where packed orders cannot be dispatched. The backlog can take hours for the warehouse team to clear, resulting in missed service-level agreements and negative customer feedback.
Prevention / Action: Design the integration to use a queuing system for generating shipping labels, rather than making a direct API call for every single order in real-time. Process the queue at a controlled, steady rate that respects the published API limits of both systems. This approach provides resilience and ensures predictable throughput, even during unpredictable spikes in order volume.
Frequently asked questions
How does the integration handle customer returns sent back through an InPost locker?
When a customer scans a return at an InPost locker, the integration can automatically create the corresponding return authorisation and credit documents in Microsoft Dynamics Business Central. This ensures that the stock level for the returned Item record is accurately updated once it's processed. Without this, returned inventory is not visible in your ERP, leading to inaccurate stock counts and missed sales opportunities.
What happens if a customer tries to ship an item that is too large or heavy for an InPost locker?
This can cause significant fulfilment delays and require manual intervention from your customer service team. A properly configured integration uses the weight and dimension data from the Item record in Microsoft Dynamics Business Central to dynamically hide InPost as a shipping option during checkout for any non-compliant SKUs. This prevents an impossible fulfilment request from ever becoming a Sales Order.
How does this integration help our finance team with reconciling InPost shipping costs?
The integration is designed to capture shipping fees from InPost Lockers and post them as costs against the corresponding Sales Order in Microsoft Dynamics Business Central. This can be configured to happen as journal entries are created for financial reconciliation. This process avoids hours of manual work allocating shipping costs at month-end and gives you an accurate view of order profitability.
When we ship an order via InPost, how quickly is the stock level updated in Business Central?
The integration updates Microsoft Dynamics Business Central as soon as the shipment is confirmed in the InPost system, triggering the creation of an Item Fulfilment. This reduces the available quantity for that SKU, providing timely inventory data across your business. This is critical for preventing overselling of a product that has already been dispatched but not yet recorded in the ERP.