What we look for in a Blue Yonder upgrade assessment
The five questions we run through before quoting an upgrade — and why three of them are about the customization layer rather than the version gap.
Read post →We help warehouses run Blue Yonder well — implementation, customization, day-to-day production support, and upgrades. Small senior team. One stack. Same time zone as the people we work with.
Everything we do is Blue Yonder WMS. We don't run TMS engagements, we don't sell robotics, and we don't take on generalist supply chain consulting. The tradeoff is a deeper bench in the things we do take on.
Blueprint, configuration, integration, data migration, training, go-live, hypercare. We work alongside your internal team or as a sub-contracted delivery partner to a primary SI.
Custom logic that holds up in production. We write code that follows Blue Yonder's customization framework so it survives the next upgrade rather than getting wiped out by it.
L2 and L3 support for live Blue Yonder environments. SLA-backed incident response, root-cause analysis, MOCA tuning, and database performance work — aligned to GCC business hours with on-call coverage for P1 incidents.
Upgrade impact assessment, customization retrofit, regression test planning, parallel-run validation, and cutover. We've handled migrations from JDA 2016.x, RedPrairie, and earlier Discrete versions.
Anonymized for confidentiality — happy to walk through any of these in detail under NDA. References available on request.
Existing cycle count workflow was producing high false-positive rates in fast-moving zones, driving unnecessary recount loops and operator frustration. We rewrote the count threshold logic in MOCA, retired four legacy custom commands in the process.
Inherited a sprawl of 22 point-to-point interfaces accumulated over six years, with overlapping responsibilities and unclear failure modes. Re-architected onto consolidated Integrator routing with proper retry, dead-letter handling, and observability.
Standing retainer covering after-hours P1 incident response, monthly MOCA performance reviews, and a backlog of small enhancements (RF screen tweaks, label format changes, report tuning). Embedded with the client's IT operations team.
We've kept the engagement model deliberately simple. Most clients start with a paid diagnostic before committing to anything larger.
A fixed-fee 5-day engagement to understand your environment, customizations, and the actual problem. You get a written report at the end whether or not we move forward together.
Fixed-fee where the work is well-defined, time-and-materials where it isn't. Either way, milestone-based with clear deliverables. We don't bill for surprises.
Your team is in the room from day one. Documentation, code reviews, and knowledge transfer are part of the work — not a phase at the end. We don't lock you into us.
Blue Yonder is the system of record across a fairly narrow set of industries in the GCC. Most of our work falls into one of four:
A free utility we're building for Blue Yonder customers planning an upgrade. Drop in your current version and customization surface area, get a written impact report. No sales call attached. Targeting public beta later this year.
Notes from active engagements, mostly aimed at architects and delivery managers working with Blue Yonder. Cross-posted to LinkedIn.
The five questions we run through before quoting an upgrade — and why three of them are about the customization layer rather than the version gap.
Read post →Most "MOCA is slow" tickets we triage turn out not to be MOCA. Here's the working order we go through before opening an Oracle / SQL Server ticket.
Read post →A practical decision matrix for SI architects weighing native Blue Yonder Integrator against MuleSoft, Boomi, and friends. Three rules of thumb.
Read post →JayLogix Consulting was founded in 2025 in Dubai's IFZA Free Zone as a focused Blue Yonder WMS practice. We were built around a specific gap our team kept seeing across the GCC: warehouses running Blue Yonder without a local partner with the technical depth to support customizations, integrations, and upgrades end-to-end.
Our practice is deliberately small. We work directly — no offshore back-end, no rotating bench, no layers between you and the engineer doing the work. That's the model, and it's what we plan to stay.
If your warehouse runs Blue Yonder and you'd like to talk to people who've spent careers inside it rather than people who learned about it from a slide deck, we'd be glad to hear from you.
Whether you're scoping a fresh implementation, planning an upgrade, or just need someone reliable on call when production goes sideways — we'd like to hear about it. We typically reply within one business day.