How should ordering-system integration be evaluated when buying a rotating clay-pot cooker?

Before signing, have the supplier expose four data points—order number, burner-slot occupancy, cook-complete signal and fault alarm—and state whether the link runs over Modbus TCP, serial or HTTP push. Then fire ten consecutive orders at real peak pace: does the rotary claypot cooker queue batches by order sequence, prompt pickup on time, and stop accepting orders when a fault trips? Acceptance passes only after two hours with no dropped or misrouted tickets, and the kitchen lead should keep the integration log handy so remapping slots after a menu change never goes wrong.