Group 65Go to Parseur
All Collections
Extracting data
Predefined mailboxes and ready-made templates
Food Ordering predefined mailbox

Food Ordering predefined mailbox

Supported platforms and extracted fields of the "food ordering" predefined mailbox
Sylvestre Dupont avatar
Written by Sylvestre Dupont
Updated over a week ago

How to use the food ordering predefined mailbox?

If creating a new mailbox:

  • Enter the name for you mailbox
  • Click Next
  • Choose Food delivery orders

If you want to convert an existing custom mailbox into food ordering:

  • Open your mailbox
  • Go to Settings
  • Under Mailbox type, choose Food delivery orders

Check out this article for general information about using predefined mailboxes.

What platforms are supported out of the box?

Here is the list platforms and POS currently supported by Parseur, in alphabetical order:

What platforms are not currently supported?

The following platforms are currently NOT supported:

If you are able to procure sample restaurant order emails for them, let us know and we'll be happy to add support for those platforms!

What fields are extracted from a food order using ready-made templates?

Fields extracted from one order to the next can vary depending on what information is present on the email

The following are the fields commonly extracted:

  • confirmationCode: order confirmation code
  • confirmationLink: link for the restaurant to confirm the order
  • customerFee: price paid by the customer for the delivery (if any)
  • date / datetime / time: date and time stamp of the order
  • deliveryInstructions: customer instructions for the delivery
  • discount: discount applied (if any)
  • dropoffAddress, unitNumber, dropoffCity, dropoffState, dropoffZip, dropoffCountry: customer or delivery address (legacy, see note #1 below)
  • dropoffFullAddress: the full address parsed and geolocated (see more about the Address format)
  • dropoffDescription: additional instructions from the customer. Should be merged with deliveryInstructions
  • dropoffEarliestDateTime, dropoffEarliestTime: in case of future orders, date and/or time of the scheduled delivery or pickup
  • dropoffEmail: customer's email
  • dropoffName: customer's name
  • getSwiftTemplate: restaurant's name (legacy see note #2 below)
  • grandTotal: total price paid by the customer including currency sign
  • itemCount: number of items in the order
  • items: list of ordered items (see below for details)
  • link: in case the order needs to be downloaded first, URL to download (see more about the Linked format)
  • orderSubType: sub order type (see note #3 below)
  • orderType: type of order (Delivery, Pickup, Scheduled, see note #3 below)
  • paymentMode: mode of payment
  • pickupAddress, pickupCity, pickupState, pickupZip: restaurant address (most of the time, the full address is included into pickupAddress)
  • pickupName: restaurant name
  • pickupPhone: restaurant phone
  • reference: order number
  • serviceFee: platform service fee
  • source: ordering platform or POS name
  • subTotal: order total before tips, taxes and fees including currency sign
  • tax: tax amount including currency sign
  • textItems: for some (rare) platforms, Parseur isn't able to split items ordered into a list. When this happens, Parseur will store items as text into this field
  • tip: tip amount including currency sign (can also be a text like CASH)
  • unitNumber: Customer's unit or apartment number

The items field is a Table field and contains the list of ordered items. Each item can contain the following attributes:

  • description
  • extra: more details about the item
  • price: total price for this item
  • quantity
  • unitPrice: price per unit for this item

Tips and best practices using working with a food ordering mailbox

#1 dropoffAddress vs dropoffFullAddress

Most customer addresses are extracted using the dropoffAddress, unitNumber, dropoffCity, dropoffState, dropoffZip, dropoffCountry sequence.

However we are progressively replacing those legacy fields with the new dropoffFullAddress field which is more reliable and also sends geolocated coordinates of the location.

If you build a custom integration, you should make sure you both accept the legacy and the newer form.

#2 getSwiftTemplate vs pickupName

Older templates use the getSwiftTemplate to store the restaurant name.

This is being progressively replaced by the more appropriately named pickupName field.

If you build a custom integration, you should make sure you both accept the legacy and the newer field names.

#3 orderType and orderSubType

orderType is extracted from the order is not always standardized across all platforms:

  • Delivery orders: orderType usually contains Delivery or Deliver
  • Pickup orders: orderType usually contains Pickup or Carry out
  • Future orders: orderSubType usually contains the information of a future order and scheduled date can be found in dropoffEarliestDateTime
  • Adjustments to existing orders: orderType usually contains adjustment with original order type in orderSubType
  • Cancelled orders: orderType usually contains cancelled with original order type in orderSubType

#4 working with amounts

Amounts are extracted with the currency symbol ($, £ etc.). Sometimes, amounts can contain text like CASH (tips especially)

If you build a custom integration, you should make sure to only keep number character set (0-9, . and ,).

Did this answer your question?