Product·Intermediate·5 min·Updated 2026-10-05
Products created by API can behave differently from identical ones created in the UI
A bundle built by bulk API refused to open the configurator. A hand-built equivalent worked. The records looked the same.
Two dozen products and a bundle were created by bulk API. At configuration time the bundle failed with a null-success error from the configuration response — an error that says nothing about its cause.
What the elimination proved, in order:
- Not the pricing. Rolling back the pricing orchestration settings changed nothing, which ruled out the whole pricing path.
- Not the obvious field. Correcting the configure-during-sale flag on the components had no effect.
- Not a null sequence — a known cause of index errors on bundle components — because there were none.
What remained: an equivalent bundle built by hand in the UI worked. The working hypothesis is that the UI populates fields the API call does not, and the diagnostic that follows is mechanical — build one product by hand, then compare it field by field against one created by API.
The transferable lesson is about method rather than about products: change one thing at a time. The pricing rollback is what made it possible to say with certainty that pricing was not involved. Had two things changed together, nothing could have been eliminated.