We work with mid-market manufacturers every day. Steel buildings, contract bedding, food production, chemicals, pharma. Different industries, different operations, different challenges. But one problem shows up almost everywhere. Dynamics 365 is live. Inventory is tracked. Production is visible. Finance is closing on time. And then we walk to the shipping floor and someone is typing order details into UPS WorldShip by hand. The data is already in D365. The customer’s account number, the service type, the delivery preferences. All of it sitting in the system. None of it reaching the floor automatically. We kept seeing this. Across implementations, across industries, across team sizes. So we built something to fix it. This blog explains the gap, what it does to your operation, and how closing it changes the way your shipping floor runs. Where the Gap Comes From D365 Finance and Operations doesn’t have a native, out-of-the-box integration with UPS WorldShip or FedEx ShipManager that works the way manufacturers need it to. The connection that existed in older versions of Dynamics AX relied on an ODBC setup that no longer holds up in the modern D365 cloud environment. The result: your sales order lives in D365. Your packing slip is posted in D365. But when the order reaches the shipping floor, none of that data flows automatically to the carrier system. Someone bridges the gap manually, every order, every day. For a company shipping 20 orders a day that’s manageable. For a company shipping 50, 100, or 200 orders a day it becomes one of the biggest operational drains nobody is measuring. What It Does to Your Throughput Throughput is the metric most operations leaders focus on for production. How many units through the line per shift. Where are we bottlenecked. The same question applies to shipping and the answer is almost always the manual entry step. A shipping team processing 60 orders a day at 8 minutes of manual entry per order is spending 480 minutes on data transfer before they’ve done anything else. That’s not slack time. That’s your shipping floor’s entire productive capacity absorbed by a task the system should be handling automatically. What gets cut to make room? Address verification before the truck leaves. Exception handling. Proactive communication when something is running behind. The work that actually requires human judgment gets compressed into whatever time is left after the data entry is done. When data flows automatically from D365 to WorldShip, that capacity comes back. Not as cost savings on paper. As real time your team can redirect to work that matters. The Data Your Shipping Floor Needs But Can’t Access Here’s specifically what lives in D365 that your shipping team needs every day but currently can’t access automatically. Customer UPS account numbers. Some customers ship on your account. Some on a corporate UPS account. Some on a branch-level collect account that differs by location. In a manual process the shipping team either knows this from experience, asks customer service, or guesses. All three approaches introduce error. Service type preferences. A customer might default to Ground for standard orders but require Next Day Air for anything production-critical. That preference is in the sales order. It doesn’t reach the floor unless someone communicates it manually. Delivery flags. Saturday delivery. Residential delivery. Signature required. Each of these affects the label, the carrier charge, and whether the shipment is delivered successfully on the first attempt. Missing any of them means a failed delivery or a billing discrepancy. Address accuracy. Corporate billing addresses, regional distribution centers, receiving docks with specific delivery window requirements. These details should be stored in the customer record and flow to the label automatically. In a manual process they depend on the shipping team knowing them or catching the discrepancy before the truck leaves. When none of this flows automatically, your floor is operating on partial information. The team fills the gaps with memory, verbal handoffs, and personal spreadsheets. That’s not a process. That’s controlled improvisation under time pressure. The Accountability Gap When a shipment goes out wrong in a manual process, tracing the error is genuinely difficult. Was the wrong collect number entered because customer service didn’t communicate it? Because the shipping team selected from memory and got it wrong? Because the spreadsheet of account numbers hadn’t been updated when the customer switched accounts last quarter? The answer is usually unclear. The error happened somewhere in the chain of people, spreadsheets, and verbal communications between the sales order and the floor. You can retrain the team, update the spreadsheet, add a checklist. But the next error will come from a slightly different gap in the same informal chain. When shipping data flows from D365 to WorldShip through a defined integration, every step is traceable. If a customer’s account number is wrong, the fix is in D365 at the customer record level. The next order ships correctly automatically. One fix applied system-wide. That’s the difference between managing errors and eliminating their source. What Happens When Your Operation Grows Manual shipping processes don’t scale. They absorb each new layer of complexity as additional tribal knowledge somebody has to carry. New customer with three different UPS accounts depending on order type? Someone learns that and adds it to their personal spreadsheet. New national retailer with specific labeling and EDI requirements? Someone builds a workaround outside the system. Second warehouse? Now two teams are managing the same informal process independently. We worked with a contract manufacturer shipping to national retailers across multiple facilities. Each retailer had specific labeling standards, documentation requirements, and EDI needs. Managing those manually across multiple shipping locations wasn’t sustainable. Peak season had become its own operational project requiring dedicated oversight just to keep the manual process from breaking down. The solution wasn’t more documentation or more oversight. It was moving the retailer-specific requirements into D365 where they could be stored at the customer level, triggered automatically at shipment, and applied consistently across every facility. When your shipping requirements live in D365, adding a new customer … Read more