Courier Integrations

Hello, don’t think this has been requested yet so thought I’d get this in.

It would be great to get integrations with couriers so we could book deliveries, print labels and have Breww update the customer with tracking info all from within Breww. Ideally this would work with orders placed natively in Breww, as well as orders that were pulled from ecommerce platforms like Shopify and Sellar. We currently use APC for our shipping but I’m sure there’s a fair few people using DPD and others too.

Thanks

3 Likes

Thanks, Jack, for putting this on the community - you’re right, it’s high time this was on here :+1:

Can we please have some feedback on how you (and others) would feel about this being an addon, which costs ballpark 5 pence per order? (For orders where you generate courier labels only.)

Due to the number of couriers, that are used, this could easily escalate out of hand on the number of requests and from past experience, (in a previous life I build warehouse management software) couriers change their requirements often, so there would be a lot of on-going work to support multiple courier integrations.

For everyone who’d like to see this supported, please give this a vote using the button in the top-left and tick all the couriers below that you’d like to see supported.

Which couriers would you like to see label creation/tracking for?

  • APC
  • DHL
  • DPD
  • Fedex
  • Hermes
  • Pallet-Track
  • Palletforce
  • Palletways
  • Pallex
  • Parcelforce
  • Royal Mail
  • THE Pallet Network
  • UPS
  • Yodel
  • Other (please comment below)

0 voters

1 Like

Thanks Luke, 5 pence per order doesn’t sound crazy and for the ease of use would not be an issue for us to pay for so happy to see it as an addon.

Cheers

1 Like

Definitely curious about this, costs seem fair, and have a couple questions:

  • If integrated how would the user workload compare to the speed/ease of downloading a batch CSV & uploading to the appropriate courier (as we currently do)? Granted this doesn’t put the tracking information into breww for us, but it is extremely quick, and tracking can be carried out on couriers online portal.

  • With regards to B2C/third party platforms like shopify, squarespace.etc would breww be able to feed back tracking information alongside fulfilment to ensure customers receive tracking information?

1 Like

Thanks for the great question, Steve, and everyone else for your votes on this. Please keep them coming in.

Our current thinking is as follows:

Allow for courier labels to be generated directly in Breww as PDFs that you can print, just like other labels Breww generates. These can be generated per delivery, or in batches like the current CSV exports. You could, for example, in a couple of clicks generate delivery labels for all APC orders for a day and print them off in the same order as these orders are shown on Breww & the pick list.

You would also be able to re-print or cancel labels generated and generate end-of-day manifests if required by your courier.

As Breww has generated the label, it knows the tracking numbers already and will link these to the orders in Breww and allow viewing the tracking details directly within Breww without having to go off to the courier’s own website to view it. Some couriers allow great “deep links” directly to the tracking information and some don’t, so this could save lots of time filling in forms on the courier’s website.

Where supported by integrated e-commerce platforms, we could sync over the tracking numbers. This is already done on our Shopify integration (if a tracking number is entered manually before marking the delivery as complete). Squarespace’s API supports this feature too, so this could be added for Squarespace too (and most of the other integrations).

In order to allow label generation, Breww would need to know the number of labels needed and courier service to use (e.g. 24h, 48h, etc and these would vary from courier to courier). Our thinking is that we build a tool to let you specify rules, so these values can be derived automatically to save you specifying them on each individual order. You could also use the rules to have Breww automatically determine which orders go via APC and which go via Royal Mail (for example), to save you choosing this on each individual order.

What are your thoughts on this? Is there anything else you’d like to see this support?

3 Likes

Thanks for the detailed response - sounds good to me. I’ll take it back to the team & see if they have any further input.

1 Like

we use palletonline a lot of the time

1 Like

A vote for DX (https://www.dxdelivery.com)

1 Like

Just had another thought/question on this - how deep do these links go - for instance, as it currently stands we generate our labels, then when they are collected, we mark our courier orders as Out for Delivery, but do not Complete them until we can see on the portal they have been delivered (hopefully to catch problems earlier) - how much of this would breww be able to automate? Or is this integration purely about label generation?
E.g.
Would breww know that they had left duty suspense once the courier had scanned the delivery out & update accordingly?
Would breww know that a delivery had been delivered and update accordingly?

I was thinking this the other day too Neil.

It would be amazing to have the functionality where we could mark orders as left duty suspense/picked up but they weren’t marked as delivered until the courier marked as so on their own systems.

1 Like

Thanks for the suggestion, guys.

I think we could do the following:

  1. You generate the labels (you’d be able to do all for a chosen courier at once or one-by-one). This doesn’t update the status of the delivery at all.
  2. You mark as left duty suspense when the collection occurs.
  3. If step 2 wasn’t done, but we found a tracking event that was clearly after collection (e.g. at delivery hub, consignee carded, etc), we could mark the delivery as left duty suspense for you automatically.
  4. Upon delivery completion coming through on the tracking, we could mark the delivery as completed in Breww.

I don’t see a problem with that process for 99% of cases, but sometimes couriers fail to update their tracking 100% of the time, it’s quite rare, but does happen, so you’d probably want to keep an eye on any that hadn’t been marked as complete after a few days and may need to mark the odd one as complete manually.

The tracking functionality will likely vary from courier to courier and there may be some where tracking isn’t available at all (e.g. some Royal Mail services), so sometimes it would be up to you to complete all the deliveries yourself, but even now you can do these in bulk per-courier, so I don’t see this being a problem.

We also envisage showing tracking history/events directly within the delivery section on an order and on the main page for a delivery, so you can see all the tracking history available to us from the courier.

1 Like

Thanks Luke, makes sense.
We’d still be checking, but it reduces the workload if some of this is automated, which is really helpful.

So, related, your answer got me thinking with the history/events could there be some sort of notification of failed delivery.etc within breww also?

1 Like

Good thinking! I’m sure there could be! We’ll see what we can do on this front when we get into the nitty-gritty of the project :+1:

1 Like