How to send delivery order emails to GetSwift

New! Ready-made Deliveries parser.

We are now able to extract data from delivery emails automatically for a wide range of ordering companies:

• Grubhub
• Eat24
• Revelup.com
• Wix for restaurants
• EatStreet
• Chownow
• Delivery.com
• Menufy
• BeyondMenu
• Clorder
• CollegeTown bagels
• Zuppler
• ezCater
• OpenCart
• Seamless
• Woocommerce
• Wix Stores
• Eatzer
• Eatnow.com.au
• OrderUp

With this feature that we call “ready-made parser”, just create a mailbox in Parseur and forward your emails to it. If the email is from one of our supported providers, we’ll parse it automatically for you! If your provider isn’t recognised you can contact us and we’ll add it to the list. Alternatively, you can still build your own template as described further down in this article.

As we described in a previous article, you can use Parseur to centralize your food delivery orders from Grubhub, Eat24 and others. Using our new integration with GetSwift, you can now turn these delivery orders into actual delivery jobs in GetSwift, and then manage your fleet of courriers. Actually, since Parseur is a generic email parer, you’re not limited to food delivery orders. Any type of delivery order emails can be sent to GetSwift using Parseur! Yes, you read that correctly, you can completely automate your delivery process, integrate with third party ordering sites and send delivery order emails to GetSwift!

1. What is GetSwift

GetSwift is a delivery management software. As they say on their website:

Dispatch like Uber
Track like Dominos
Set routes like FedEx

GetSwift core features include:

• automated dispatching,
• smart routing,
• real time job tracking,
• real time service tracking,
• proof of delivery,
• white label booking form,
• live management dashboard,
• iOS and Android apps for courriers
• API to integrate with third parties.

2. Create a Parseur account and a new parser

If you’re new to using Parseur, get started by reading our tutorial on how to setup your first Parseur mailbox. Once done, you should have an parser mailbox that looks like this: [email protected]

You must redirect the food order emails to this email address so that Parseur, then GetSwift, could process the orders automatically. The following article covers how to setup automatic email forwarding.

3. Create templates or use automatic templates for food delivery

While creating your template(s), you have to give specific names to your fields so that they can be sent to GetSwift.

Here is the list of all the field names (you don’t have to specify all of them, of course) :

Information about the pickup:
 - pickupTime (date and time)
 - pickupName (text)
 - pickupPhone (text)
 - pickupEmail (text)
 - pickupDescription (text)
 - pickupAddress (text)
 - pickupCity (text) : merged into pickupAddress
 - pickupState (text): merged into pickupAddress
 - pickupZip (text): merged into pickupAddress
 - pickupStateProvince (text)
 - pickupCountry (text)
 - pickupSuburbLocality (text)
 - pickupPostcode (text)
 - pickupLatitude (decimal number)
 - pickupLongitude (decimal number)

Information about the dropoff:
 - dropoffEarliestTime (date and time)
 - dropoffLatestTime (date and time)
 - dropoffDate (date): added before dropoffEarliestTime and dropoffLatestTime (only use when these fields don't contain the date)
 - dropoffName (text)
 - dropoffPhone (text)
 - dropoffEmail (text)
 - dropoffDescription (text)
 - dropoffAddress (text)
 - dropoffCity (text): merged into dropoffAddress
 - dropoffState (text): merged into dropoffAddress
 - dropoffZip (text): merged into dropoffAddress
 - dropoffStateProvince (text)
 - dropoffCountry (text)
 - dropoffSuburbLocality (text)
 - dropoffPostcode (text)
 - dropoffLatitude (decimal number)
 - dropoffLongitude (decimal number)

General information about the delivery:
 - reference (text)
 - getSwiftTemplate (text)
 - deliveryInstructions (text)
 - unitNumber (text): merged into deliveryInstructions
 - crossStreet (text): merged into deliveryInstructions
 - grandTotal (text): merged into deliveryInstructions
 - paymentMode (text): merged into deliveryInstructions
 - source (text): merged into deliveryInstructions
 - itemsRequirePurchase (true/false)
 - items (list)
   - quantity (integer, GetSwift does not handle fractional quantities yet)
   - description (text)
   - sku (text)
   - price (decimal number)
 - subTotal (decimal number, only used if items list is missing)
 - customerFee (decimal number)
 - customerReference (text)
 - tax (decimal number)
 - taxInclusivePrice (decimal number)
 - tip (decimal number)
 - driverFeePercentage (decimal number)
 - driverMatchCode (text)
 - deliverySequence (integer)

These fields match those found on the GetSwift API.

 Note: For a delivery job to be valid, GetSwift needs a minimum of a pickup address and a dropoff address. You don’t always have the full pickup address of the restaurant or shop mentioned in the delivery order email. You can get around that by creating Templates in GetSwift and pre-filling the pickup address. In that case, you have to perfectly match your GetSwift template name with the content captured in the getSwiftTemplate field. Typically, your GetSwift template name should be the name of your restaurant (or pickup location) as it appears in the delivery email. Feel free to contact us through the chat if you need any help with that feature.

4. Set up your GetSwift API key

Log in to your GetSwift account.

Then navigate to the Integration > API Settings page, generate an API key and copy it into the clipboard.

Back on Parseur, go to the “Export” section of your parser scroll down and paste your GetSwift API key into the field. Optionally, if you have a default driver fee percentage, you can enter it as well.

Then, click Save.

5. Test sending delivery order emails to GetSwift!

If all is in order, you should see your order emails turn into deliveries jobs on your GetSwift account. If not, you’ll receive an email detailing what went wrong.

Note: if your orders where already processed before you added the GetSwift key, click on the double-arrow refresh icon to reprocess a document and send to GetSwift again.

6. Frequently Asked Questions

Problem: My scheduled order was sent to GetSwift with the wrong time or did not get into GetSwift

Solution: Make sure that your time zone is properly set in your settings, here: https://app.parseur.com/account/edit

Your time zone should match the time zone of your pick-up and drop-off addresses. If you deliver across time zones or have addresses in different time zones, please contact us.

Problem: Parseur displays “Export failed”

Solution: there can be several reasons why an export failed. To get more information, click on the magnifying glass icon to see the logs and open the message about the failed export. Check the answers below to solve most common solutions to export problems.

Problem: My emails did not contain the whole address, just the name of the place to pickup from or dropoff to.

Solution: Make sure that you have created a template in GetSwift with relevant pickup and/or dropoff addresses with the name matching the content of the getSwiftTemplate field exactly.

Problem: the order went through GetSwift but was wrongly tagged (wrong country or city).

Solution: Try adding more address details if you have them (like the country, city or zip). If that doesn’t help, please contact GetSwift for more information.

Problem: GetSwift sends back an error code 500 with no error message.

Solution: This usually happens when GetSwift was not able to geolocate the address you sent. Try adding more address details if you have them. Also, put any company name or apartment/unit number out of the address and into their own fields. If that doesn’t help, please contact GetSwift for more information.

Feel free to ask for help on the chat system in the bottom right corner of your screen.

Happy parseuring!