Skip to content

Integrations

Route orders from Local Line, Barn2Door, GrazeCart and Local Food Marketplace

Local Line, Barn2Door, Local Food Marketplace and GrazeCart are built for selling and taking orders, not for planning delivery routes. Export a day's orders as a CSV, import it into Porch Routes with the matching column layout, fix any address Porch Routes couldn't place, and build the route — the same steps regardless of which platform the file came from.

Last updated By Porch Routes

Why farm-platform storefronts hand off routing

Local Line, Barn2Door, Local Food Marketplace and GrazeCart are built for the storefront side of a farm or food hub: listing products, taking orders, collecting payment, printing pack lists. None of them plans a multi-stop route, dispatches a driver, or texts a customer when their box is on the way — that's a different problem, and it's the one Porch Routes solves. Selling and packing stay in the platform your customers already order from; routing, drivers and delivery texts move to Porch Routes once a day's orders are exported.

The column layouts Porch Routes already knows

Pick your platform on the import screen and Porch Routes pre-fills the column mapping for the export you already have:

Farm-platform exports Porch Routes has a ready-made layout for
PlatformExport to chooseWhat Porch Routes reads from it
Local LineOrders → select orders → Export → Delivery Routing exportCustomer name, address, phone, email, order number, delivery date and window, items, delivery notes, package codes
Barn2DoorOrders → Pack list (CSV) for the delivery dayCustomer name, address (with latitude and longitude when the pack list has them), phone, email, delivery date, order notes, items
Local Food MarketplaceReports → Orders (delivery) → Export CSV, or the Routific exportCustomer name, address, delivery date, phone, email, delivery instructions, items
GrazeCartOrders → filter → Export (CSV)Customer name, address, phone, email, order ID, fulfillment date, order notes, items, weight
All four layouts are a best-effort match, built from each platform's own export field names and the routing tools their exports already feed, not from a published header list — check the preview before you build, and fix and save any column that lands wrong.

Selling on Shopify or Square Online instead? Porch Routes also knows their orders-export layouts, or, for Shopify, a live connector that skips the CSV step entirely.

Import the day's orders

  1. Export the day's orders

    From your platform, export the orders due for delivery as a CSV — the table above has the export to choose for Local Line, Barn2Door, Local Food Marketplace and GrazeCart.

  2. Open Import CSV

    In Porch Routes, open Orders for the day and choose “Import CSV” — the Import orders sheet opens. Choose the file, or paste rows; files up to 5 MB.

  3. Match your columns

    On the Match your columns step, use “Start from” to pick your platform. Porch Routes pre-fills the mapping and previews the first orders exactly as they'd import. Pick a day for rows with no date, then set anything left unmatched by hand.

  4. Fix anything flagged

    Rows with a problem come first in the results, each with the reason and a way to fix it. An address Porch Routes couldn't place shows “Check address”, so you can search for it or drop a pin before the route is built.

  5. Build the route

    Once the day's orders are in, build routes the same way as any other day — the same vehicle, temperature and time-window rules apply no matter where an order came from.

If your platform isn't listed, or a column lands wrong

Choose “My own columns” instead of a preset, and match each field by hand from a dropdown of your file's own headers — the same screen every layout uses. Save the result with a name and it's offered next time, so a weekly export only needs matching once. Re-uploading never doubles deliveries: rows update the orders they imported before, and the same file inside 24 hours returns that earlier import unless you choose to import it again.

What happens after the import

Imported orders sit with every other open order for their delivery date, ready to be built into a route the same way as an order added by hand, sent through the API, or synced from a store connector — the same solver, the same vehicle and temperature rules, the same driver app and the same customer texts once the route is dispatched.

Questions

Do I need to install anything in Local Line, Barn2Door, GrazeCart or Local Food Marketplace?

No. Export the CSV the way you already can, then import it into Porch Routes — nothing changes on the platform side.

What if I sell on a platform other than these four?

Square Online and Shopify's own orders export also have a ready-made layout, and Shopify sellers can use a live connector instead of a CSV. Any other spreadsheet works with My own columns, matched once and saved for next time.

How exact are these column layouts?

All four are a best-effort match built from each platform's own field names and the routing tools their exports already feed — none of the four publishes its export's exact header row. Check the preview before you build; a misread column is a one-time fix, not a repeat problem, once you save your own layout.

What happens to an address Porch Routes can't find?

It's flagged for review rather than guessed. Open “Check address” to search for the right one or drop a pin on the map before the route is built.

Does importing the same file twice create duplicate deliveries?

No. Re-uploading updates the orders it imported before, and the same file inside 24 hours returns that same import unless you choose to import it again.

Local Line, Barn2Door, Local Food Marketplace, GrazeCart, Square and Shopify are trademarks of their respective owners. Porch Routes isn't affiliated with or endorsed by any of them.

Plan your next delivery day in a few minutes.

Add your vehicles and a day of orders — by hand, from a CSV or over the API — and build your first routes.

Free up to 150 orders a month · No credit card