You must create a tender for each ordering channel (DSP/partner) that sends orders into your Micros POS. Without a matching tender, Stream may not be able to close the order to the correct payment type.
1. Understand how Stream selects a tender
When an order arrives, Stream will attempt to assign a tender in this order:
A tender whose name matches the DSP/partner the order came from (for example DoorDash or Uber Eats).
If none is found, any tender with partner in its name, which acts as a catch-all.
As a last resort, the Auto Close tender source, if one is configured.
2. Create a tender for each DSP/partner in Simphony
In Simphony, create a Tender/Media record for each ordering channel you receive orders from. For the steps to do this in Simphony, see Oracle's guide: Configuring Tender/Media.
3. Name each tender so the channel is identifiable
Name each tender after the DSP/partner it represents. Common Examples:
DoorDash =DOORDASH
Uber Eats = UBEREATS
Grubhub = GRUBHUB
Catch-all generic = PARTNER, THIRD PARTY, or 3RD PARTY
Tender names and IDs vary by Simphony configuration. Use the channel names that apply to your venue — the names above are examples.
4. Confirm with a test order
Place a test order from each channel and confirm it closes to the correct tender.
Important: If no tender matches the DSP/partner name, the order may fall back to a generic tender or fail to close correctly. Make sure each active ordering channel has a matching tender.