Home / Case studies
Case studies
Projects we have delivered for Business Central customers and Microsoft partners. Client names are withheld unless the client has agreed to be named.
Embroidery orders shared with an outside team
The client
An Australian business selling safety equipment, with embroidery on garments such as workwear and uniforms. The client's name is withheld.
What they needed
The embroidery is done by a separate, third-party team. That team needed to see which orders were ready for embroidery and record when each one was done. The client needed that progress in Business Central, and a reliable way to bill the embroidery work by the number of orders completed.
Giving an outside team access to Business Central was not the answer: it adds licence costs and exposes far more data than they need.
What we built
- Orders sent automatically. When a sales order is released in Business Central, its order data is sent to the web app. Nobody re-keys or emails order details.
- A simple app for the embroidery team. The team logs in to the web app, sees the embroidery orders waiting for them, and works through the list.
- Completion flows back. When the team marks an order complete, the status is updated in Business Central, so sales and dispatch staff see progress without chasing anyone.
- Reports. The app reports on orders waiting and completed, so both sides can see the workload and what has been done.
- Billing by completed orders. Invoices for the embroidery work are produced from the number of orders completed, so billing matches the work actually done.
The result
Order release, embroidery, completion and billing now run as one connected process between the client and their outside team. The embroidery team works in an app built for their job, and Business Central stays the single source of truth for orders.
Automatic shipment confirmation emails
The client
A company in the United States running Microsoft Dynamics 365 Business Central with Insight Works apps. The client's name is withheld.
What they needed
Customers should receive a shipment confirmation as soon as their order ships, with the tracking details and the packing slip, without staff writing each email by hand. The office team also needed to change the wording themselves, without a developer.
What we built
- An email is created automatically when a warehouse shipment is posted, and can be switched on or off in setup.
- An email template edited inside Business Central with a rich text editor, using placeholders that are filled in from the shipment: sales order, customer PO, invoice number, part numbers, item lines, ship-to address, shipment date, tracking number, shipping agent and service.
- The recipient comes from the posted sales shipment or the customer card, chosen in setup.
- An optional packing slip PDF, using a report chosen in setup and based on either the warehouse shipment or the sales shipment.
- A safeguard for shared shipments: when one warehouse shipment covers several customers, the combined PDF is not attached, so no customer sees another customer's details.
- A one-click option to restore the default template.
The result
Customers get a consistent confirmation with tracking and paperwork when their order ships, and the client's team can change the email without a developer.
Automated bank file uploads from Business Central
The client
A company in Abu Dhabi, United Arab Emirates, running Microsoft Dynamics 365 Business Central.
The problem
The client needed to upload bank files to their bank. Doing this by hand meant staff exporting files from Business Central and uploading them separately, which is slow and easy to get wrong.
What we built
We connected Business Central to the bank through Microsoft Azure. Azure Logic Apps run the workflow, and Azure Functions handle the file processing, so bank files move from Business Central to the bank without anyone downloading and uploading them.
Keeping the integration in Azure, rather than inside Business Central, means it can be monitored, changed and rerun on its own, without touching the client's ERP.
The result
Bank files now flow from Business Central to the bank as one connected process, instead of a manual export and upload.