AI Shipment365 is available on Microsoft Marketplace today! Setup is fast. We designed it to deploy in hours, not weeks. But getting every customer account structure, service type preference, and delivery flag configured correctly from day one is where the detail matters. That’s where Ascent’s experience changes the outcome. We built AI Shipment365. We’ve implemented it across manufacturers in steel, bedding, food, pharma, and chemicals. When we configure it, you go live the same day. Here’s exactly what that looks like… Before You Start: What You Need in Place The one to two hour deployment timeline holds when everything on this list is ready before configuration begins. Most setups that run long don’t hit technical problems. They hit preparation gaps. D365 F&O environment. AI Shipment365 runs on D365 Finance and Operations cloud deployments using standard data entities via Power Automate. No X++ code, no custom extensions. Confirm your environment is on a current supported version. Power Automate needs to reach it. Power Automate licensing. Many D365 F&O customers already have Power Automate capacity in their existing licensing they’ve never activated. Check before purchasing a separate plan. A per-flow or per-user plan covers what the integration needs. Azure subscription. The integration uses an Azure SQL database as the intermediary between D365 and WorldShip. If you already run Azure workloads, provision it there. If not, a standalone subscription works. At mid-market shipment volumes, the database cost is minimal. UPS WorldShip version. This one matters more than people expect. WorldShip import and export mapping is version-specific. Older versions use different backend database table structures than current ones. A manufacturer who ran setup assuming a current schema on a two-year-old WorldShip installation spent two hours troubleshooting mapping failures that were version mismatches the whole time. Check your version before starting. Customer shipping data. This step determines how well the integration performs from day one. Before configuration starts, compile the following for every customer: UPS account numbers. Identify whether each customer ships on your account, their own corporate account, or a branch-level collect account. A distributor with three regional offices might have three different collect numbers depending on which location is receiving the order. Document all of them and the logic for when each applies. Service type defaults. Flag any customer who requires Next Day Air or Second Day Air by default, or under specific order conditions like production-critical flags. Delivery flags. Saturday delivery, residential delivery, signature required, adult signature required. These are the flags most commonly missed in manual processes. One manufacturer lost a production line for a Monday morning because a Saturday delivery flag wasn’t stored and didn’t make it to the shipping team on Friday. Address accuracy. Review your D365 customer address records before go-live. Inaccurate addresses that were being caught and corrected manually during WorldShip entry will flow directly to labels once the integration is live. Thirty minutes of address review before go-live is worth more than any amount of fixing afterward. The Configuration Sequence Step 1: Provision the Azure SQL database. Create the database in your Azure subscription. The AI Shipment365 schema includes specific tables for inbound shipment records from D365 and outbound tracking records from WorldShip. Configure a SQL Server login scoped only to those tables. This login is used by both Power Automate and the WorldShip ODBC connection and doesn’t need broad database access. Step 2: Deploy the Power Automate flows. AI Shipment365 ships as Power Automate solution packages. Import them into your Power Automate environment and configure the D365 and Azure SQL connection references. The D365 connector runs under a service account scoped to sales orders, packing slips, customer records, and the tracking fields the integration writes back. Nothing broader. The tracking update flow runs on a schedule. Every 30 minutes covers most manufacturers. If you have customers who expect near-real-time visibility, every 15 minutes is the practical floor. Running it more frequently adds API call volume without meaningful improvement. Step 3: Configure the WorldShip ODBC connection. On each WorldShip workstation, set up an ODBC data source pointing to the Azure SQL database using the login from Step 1. Before moving to mapping configuration, test the connection explicitly. Most corporate firewalls allow outbound connections to Azure SQL on port 1433, but if your environment has egress filtering, confirm that port is open first. Discovering a firewall block after spending an hour on WorldShip mapping configuration is avoidable. Step 4: Configure WorldShip import and export mapping. Import mapping defines which Azure database fields populate which WorldShip fields when the barcode is scanned. At minimum: ship-to name, all address lines, city, state, zip, country, UPS account number, service type, and delivery flags. Export mapping defines what WorldShip writes back after label generation: tracking number, published rate, billed rate, service type used, and packing slip ID as the key field linking the return record back to the original D365 order. The packing slip ID is the link in both directions. Confirm barcode format compatibility between D365 and WorldShip before completing this step. Step 5: Enter customer data in D365. Using the data compiled during preparation, enter account numbers, service type defaults, and delivery flags into D365 customer records. For customers with multiple UPS accounts depending on order type or destination, configure the selection logic at the sales order level and validate each variation explicitly during UAT. A customer with a corporate account for orders over a certain value and a branch collect account below that threshold needs both paths tested, not just the default. The UAT Process: What to Test Before Go-Live Standard shipment on your account. Post a test packing slip, scan the barcode in WorldShip, and confirm ship-to address, account number, and service type populate correctly. Generate a label. Confirm the tracking number appears in the D365 sales order within the next flow run interval. Customer collect account. Test at least one customer shipping on their own UPS account. Confirm the correct collect number populates. This is the scenario that causes the most freight disputes in manual … Read more