Kitenzo work splits into three jobs that get confused with each other: app configuration, theme integration, and bundle merchandising. Knowing which one you need is most of the value.
Diagnose where the problem actually sits. If the bundle builds correctly but looks wrong in cart, that's theme integration. If it builds incorrectly, that's configuration or Conditions Engine rules. If it works perfectly and nobody buys it, that's merchandising. Three different specialists, three different rates. Describing the symptom precisely gets you routed correctly.
For fulfilment problems, involve whoever packs the orders. Packing slip and picking issues are the complaint most likely to be handed to a developer when the real fix is a configuration decision about whether bundles present as one line item or several. Your warehouse or 3PL has an opinion about which they want, and it should drive the configuration. Ask them before you brief anyone.
For custom builds, ask which path they'd use. Kitenzo offers the visual Design Editor, the Template Creator for coded templates, and an SDK for fully custom front ends. A developer who reaches straight for the SDK when the Design Editor would do is building something expensive to maintain. Ask them to justify the choice.
Check theme compatibility early. Bundle display depends on line item property handling, which varies by theme. If you're on an Eight theme, note that Kitenzo is built by the same company — see our Eight Themes experts if the theme side is where the work sits.
Ask for a live store with bundles running. Bundle UX is visual and interactive. Two minutes on a working store tells you more than a case study.