Clone loads from an email (beta)

When a customer emails a batch of loads on the same lane, with only the POs, dates and times changing, you don't have to build each one. Open one existing load as the template, click Clone Load with AI, and Kit creates a new load for every PO in the email. Load cloning is in beta and turned on per team, so ask your Drumkit admin if you don't see it.

Here's the kind of email we mean

What gets copied, and what changes

Everything comes from the load you pick as the template except the few things the email changes. That's why picking the right template matters.

Copied from the template load	Taken from the email, per load	Left blank
Customer, lane, pickup and delivery locations, equipment, commodities, weight	PO or load reference, sales order number, pickup and delivery dates and times, pickup and delivery reference numbers	Rates and carrier. Each new load comes through unpriced so you can set it yourself.

1. Open the email and the template load

Open the email with the batch of loads, then switch the sidebar to the Active view and open an existing load with the right customer, lane and equipment. Search for it by its load number if it isn't already showing. The load can be in any status, including tendered or delivered.

If Kit spots a batch like this in the New view, it may also suggest Clone from this load with a load it picked. Click Change to use a different source load (enter its exact load number and click Find), or Use Load Builder instead to build a single load.

2. Click Clone Load with AI

On the load's overview, click Clone Load with AI. Kit reads the email and its attachments and starts creating loads in the background. You can keep working, switch emails or close Drumkit. Open the same load again later to see where it got to.

While it runs you'll see Reading email... ("Finding the loads to create.") and then Creating loads with a count, like "3 of 7 complete".

3. Read the results

When the job finishes, the card says one of:

• N loads created or Load cloning complete: everything went through.
• Load cloning finished with notes: some loads were skipped or failed, or Kit wants you to double-check something. It opens on its own.
• No new loads created: usually because every PO already exists in your TMS (see below).
• Load cloning failed: the job couldn't run. The reason shows underneath.

Each row shows a PO and its outcome: Created, Skipped or Failed. Click a created load to open it in Drumkit, or copy its number to find it in your TMS. Under Extraction notes, Kit lists anything it had to assume, for example a time with no AM or PM. Treat them as places to double-check. They aren't errors.

Skipped as "Already exists"

Before creating anything, Drumkit checks every PO against the loads in your TMS. If a load with that PO is already there, it skips it and links you to the existing load ("This load already exists in your TMS. Nothing new was created."). Cloning is for loads that haven't been built yet, so a run where every row says Already exists means those loads were already built.

The check uses the loads Drumkit has synced from your TMS, so a load someone typed into the TMS a few minutes ago may not be caught yet. If you've just built some by hand, check before you clone.

The same goes for a PO listed twice in the email (created once) and a PO another teammate is cloning at the same moment ("This load is already being created by another clone request.").

4. Teach Kit how this customer writes (optional)

Choose Clone Load and Review AI Instructions from the menu next to the button. Under Customer instructions, tell Kit in plain English how to read this customer's emails, for example "Pickup times are AM and delivery times are PM unless the email says otherwise." Click Save and clone. The instructions are saved for that customer and used on every future clone for them, so you only write them once.

This step changes how Kit reads the email. It doesn't preview the loads Kit will create.

If something failed

Row or message	What it means	What to do
Already exists / Duplicate in email / Already being created	Skipped to avoid a duplicate.	Nothing. Click the row to see the existing load.
Missing reference	Kit found a load in the email with no PO or load number.	Build that one with Builder, or ask the customer for the PO.
Could not build this load	A date or time in the email couldn't be read.	Check the Extraction notes, add a customer instruction if it's a pattern, and retry.
TMS creation failed	Your TMS rejected the load. Its message shows under the row.	Fix what the message says on the template load if you can, then retry. Otherwise send it to support@drumkit.ai.
Creation may have succeeded. Verify in the TMS.	The job was interrupted right as it wrote to your TMS.	Check your TMS before retrying, then contact support. Retrying blindly can create a duplicate.
Could not check existing loads / Could not reserve this load / Load reservation was lost / Not attempted	A hiccup before anything was created.	Click Try again.
The email contains more than 50 loads. Narrow the request and try again.	One job creates up to 50 loads.	Split the email, or build the rest with Builder.

When a job can be retried, you'll see Try again and Edit instructions and retry. Retrying uses the same template load, and POs that already exist are skipped, so it won't duplicate what was created the first time.

FAQs

---

Related

• How Builder works

• After you build: Load ID and already-built loads

• Report a Builder miss