Work
- Drupal 9
- Dynamics 365 API
- MySQL
- jQuery
Walnut Creek Foods
A Drupal 9 maintenance engagement (2024–2025) for a US food company — bug fixes, core/contrib updates, performance work, and a refactor of the Microsoft Dynamics 365 integration after a vendor API change.
What we shipped
Key outcomes
- Drupal 9 maintenance (2024–2025) — bug fixes, core/contrib updates, performance work
- Microsoft Dynamics 365 integration refactored after a vendor API update — kept order, product and sales flows working
- Full-stack work across back-end services, DB-query tuning and front-end styles
Walnut Creek Foods is a regional US food company on Drupal 9. Across 2024 and 2025 we ran its engineering — bug fixes, core and contrib updates, performance work, DB-query tuning, and front-end style adjustments — keeping the site stable while it kept selling.
The non-trivial piece was the Microsoft Dynamics 365 integration. Product, account, reorder-guide, sales-basket, sales-operations and sales-history data all flowed between Drupal and D365, and when Microsoft updated the API surface those services had to be refactored without breaking the order pipeline. We reworked the integration on the back end and adjusted the theme on the front end so the change was invisible to the buyer.

Got a similar build in mind?
Tell us about the platform, the constraints, and the timeline.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.