AI Shipment365 Setup Guide: What Happens After You Purchase on Microsoft Marketplace
AI Shipment365 Setup Guide: What Happens After You Purchase on Microsoft Marketplace
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 operations and the most relief once it’s working automatically.
Saturday delivery flag. Test a customer with a standing Saturday delivery requirement. Confirm the flag shows in WorldShip before generating the label. A missed Saturday flag on a production-critical shipment leaving on a Friday is the kind of error that ends up in a customer meeting.
Multiple account customer. For any customer with account logic depending on order type or destination, test every variation. Don’t assume one path validates the others.
High volume. If your floor processes 50 or more orders per day, post multiple test packing slips simultaneously before go-live. The Azure database handles concurrent records cleanly, but validate it at your actual volume before the first peak shipping day.
Day One on the Shipping Floor
Pick and pack happens as normal. The packing slip prints as normal. The change starts at the WorldShip workstation.
Instead of typing in customer details from memory or a spreadsheet, the shipping team scans the packing slip barcode. WorldShip retrieves the shipment record and populates everything automatically. The team reviews the pre-populated fields, enters box weights, generates the label, and submits.
The review step is a feature, not a formality. It’s the quality check that catches any customer record error before it becomes a shipment error. Build it into the workflow and don’t let it get rushed away.
Tracking numbers flow back into D365 on the next flow run. Customer service has the tracking information without calling the shipping floor. When estimated delivery dates change, the system flags it before the customer calls.
Day one will feel slightly different. Day three will feel faster than manual ever did. By the end of the first week the team won’t want to go back.
Where Configuration Gets Specific: What We See Most Often
WorldShip version mismatches. Mapping that works on a current WorldShip installation doesn’t always transfer to an older version. The backend table names and field names change between major releases. Always confirm your WorldShip version and match the setup documentation to it before starting mapping configuration.
Account number format. UPS shipper account numbers are 6 characters. Collect account numbers follow a different format. When entering account numbers into D365, the format has to match exactly what WorldShip expects to receive, leading zeros included. A collect account entered in the wrong format will appear to populate in WorldShip correctly but fail at label generation, which is a harder failure to diagnose than a blank field.
Power Automate throttling at peak volume. Power Automate has per-flow run limits depending on your licensing tier. At normal volumes this is never an issue. During a peak shipping week, Black Friday, end of quarter, a large product launch, if flow runs are being queued and delayed, the packing slip data push slows down. Confirm your Power Automate capacity against your peak volume before that week arrives.
Multi-facility ODBC scope. Each WorldShip workstation in a multi-facility operation connects to the same Azure database but should only retrieve shipment records for its own facility. The AI Shipment365 table design includes a facility identifier field for this reason. If it isn’t configured correctly, a workstation at one facility can pull shipment records for another. Validate facility scoping explicitly in a multi-facility UAT before go-live.
Packing slip barcode format. If your D365 environment includes customizations to the packing slip report, your barcode format may differ from the standard D365 output. Confirm that the barcode scanner at the WorldShip workstation reads the actual format your packing slips produce. This takes ten minutes to test and prevents a go-live failure that looks mysterious until someone checks the barcode format.
Adding FedEx ShipManager
If your operation uses FedEx alongside UPS, add FedEx after the UPS configuration is stable and validated. The architecture is identical. The Azure database is extended with FedEx-specific tables, the Power Automate flows are updated for FedEx carrier selection, and FedEx workstations are configured with their own ODBC mapping.
The main complexity is service type codes. FedEx and UPS use entirely different code systems. If you’ve stored service type preferences in D365 using UPS codes, you’ll need either separate fields for each carrier or translation logic in the Power Automate flow that reads the carrier selection and maps accordingly. Run a full UAT cycle for FedEx independently from UPS.
Ongoing Maintenance
WorldShip updates. Major UPS WorldShip releases occasionally change backend database table structures. After a significant update, test your import and export mapping on a non-live order before your shipping team runs full production volume. UPS publishes release notes and schema references with major updates.
Power Automate and D365 updates. Microsoft’s connector and platform updates are backward-compatible in most cases. Monitor release notes for changes to the D365 sales order, packing slip, or customer record entities, particularly if your D365 environment is customized.
Azure database hygiene. Configure automated backups. Set a record retention policy. Completed shipment records don’t need to stay in the Azure database indefinitely after they’ve been posted back to D365. Ninety days covers most audit and dispute resolution windows.
The Bottom Line
AI Shipment365 deploys fast because we built it that way. The technology stack is entirely Microsoft. The configuration is well-defined. Once it’s configured, it runs without babysitting.
What makes it go live correctly the first time is preparation. The right customer data, the right WorldShip version, the right UAT coverage. That’s what Ascent brings.
We built it. We implement it. We stay engaged after go-live.
Frequently Asked Questions
Why implement with Ascent?
We built it. Every edge case in this guide comes from implementations we've run. We handle Azure provisioning, Power Automate deployment, WorldShip mapping, customer data setup, and full UAT in a single session. You go live the same day, correctly.
What does an Ascent implementation look like?
One session. We arrive prepared, configure everything, run UAT with your team, and stay available through your first live shipping period. If something unexpected comes up, we already know where to look.
What D365 version is required?
Current supported versions of D365 Finance and Operations cloud. For on-premises or older versions, contact Ascent before purchasing to confirm compatibility.
Does this work with a customized D365 environment?
In most cases yes. The integration uses standard data entities. The two things worth confirming in a customized environment are barcode format on the packing slip report and account number field accessibility in the customer record.
What happens if Power Automate is unavailable?
Shipment records queue in D365 and process once connectivity restores. Power Automate's published SLA is 99.9% monthly uptime. Brief outages don't lose data. They delay processing until the flow runs again.
Can we update customer data after go-live?
Yes. Account numbers, service types, and delivery flags are all managed in D365 at the customer record level. No changes to the integration required.
What support is available?
Ascent provides direct product support. We built AI Shipment365 and maintain it. For configuration questions, implementation guidance, or anything that comes up post-go-live, we're the right team to call.
Other Content In This Stream :
Ready to start transforming your business?
Talk to us about how Ascent Innovations can help you realize business value faster with end-to-end solutions and cloud services.
