Model nested modifier groups across delivery channels

Steps

1. Design your modifier tree with a maximum of two levels of nesting for broad channel compatibility; avoid going deeper unless all target channels explicitly support deeper nesting
2. Represent each level as a ModifierGroup containing Modifier items; a Modifier that itself has choices should reference a child ModifierGroup by ID — never create circular references between groups
3. Assign unique GUIDs or PLU codes to every item, modifier, and modifier group; reusing the same identifier across different entities causes platform-side mapping failures
4. Store your internal POS identifiers in the custom_integration_attributes or equivalent externalId field so inbound orders can be reverse-mapped to your POS data model
5. Test the full nesting tree against each target platform's sandbox menu validator; some platforms (such as DoorDash Drive) reject more than two nesting levels
6. Document which channels support nested modifiers and at what depth; maintain a channel capability matrix to gate which menu models are pushed to which channels