Turn Order Items into Packing Rows

Create a Zapier packing table with one checklist row for every order item.

Introduction

30 Second Summary

Large orders are difficult to pack when every product is squeezed into one block of text. Missing one small item becomes far too easy.

In this project, you will build a Zap that writes each order line item into its own row in Zapier Tables. Each row has its own Packed checkbox for a clear packing checklist.

What You'll Build

You will send a sample order through your Zap to fill the Packing table with one checkable row per product.

By the end of this project, you'll have:

A packing checklist that turns every product in an order into a separate row.
Clear product details across Product, Quantity, and Order columns.
A repeatable automation that adds a fresh group of rows whenever another order arrives.
Secret Mission: An optional challenge to push your automation skills further.

Are there any prerequisites?

A free Zapier account is required.

A test store or sample order source must also provide orders with line items.

Before We Start

Your packing workflow can only split an order when the source keeps each product as a separate line item. A sample order gives the workflow real product data to use later.

This step gets your Zapier account ready for the build. You'll also prepare a two-product sample order for the trigger test.

In this step, get ready to:

Sign in to your Zapier account.
Confirm that Zapier Tables is available.
Prepare a sample order with two product line items.

Sign in and confirm Tables access

Your Zapier account holds the automation you'll build. Zapier Tables stores the packing rows created by that automation.

Account setup involves your login details. Keep those details inside Zapier's official pages.

Create an account through the official Zapier sign-up page if you do not already have one.
Sign in through the official Zapier login page.
Open Zapier Tables in the same browser.
Confirm that the Tables page shows the + Create button.

Good progress. Seeing + Create confirms that your account can reach the table workspace needed for the packing checklist.

Can't reach Zapier Tables?

Check that your browser is signed in to the Zapier account you plan to use for this project.
Use any access prompt on the Tables page to identify the plan or account permission blocking the workspace.

Still blocked? Help me work out why my Zapier account cannot access Zapier Tables. You can also ask the Zapier Community.

Choose an order source with line items

An order source is the store or app that sends each new order to your Zap. It needs to preserve every product as its own entry.

What is a line item?

A line item is one product entry inside an order. It carries product-level values such as the product name and quantity.

Your sample order needs separate entries for two products. That structure lets the later Tables action create one packing row for each product.

Test orders keep real customer information out of the project. Use test products plus test customer details throughout this walkthrough.

Open the test store or order source you plan to connect to Zapier.
Locate the area that lets you create a sample order.
Confirm that one order can contain more than one product entry.
Confirm that each product entry keeps its own product name.
Confirm that each product entry keeps its own quantity.

Create and verify a sample order

The sample order becomes the test record for your trigger. Two distinct products give you enough data to prove that the later action splits the order correctly.

Start a new sample order in your selected order source.
Add a test product named Packing Tape as the first line item.
Set the quantity for Packing Tape to 2.
Add a test product named Shipping Labels as the second line item.
Set the quantity for Shipping Labels to 1.
Use test customer information for any required customer fields.
Save the sample order as a new order.

Before you check, how many separate product entries should Zapier receive from this order?

Open the saved order's details in your order source.
Count the product entries shown in the order.

You should see two separate line items. Packing Tape should show a quantity of 2.

Shipping Labels should show a quantity of 1.

That's your test data ready. Zapier now has a two-product order it can use to build the packing workflow.

Only seeing one product entry?

Return to the sample order if one product was entered as a note instead of a separate line item.
Confirm that both products appear as separate entries before saving the order again.
Check that each entry has its own quantity value.

Still stuck? Help me create a sample order with two separate line items for a Zapier trigger test..

Your Zapier account and sample order are ready. Next up, you'll create the Packing table that turns those products into a clear checklist.

Create the Packing Table

A packing checklist only works when every product has a clear place to land. Before automation can split an order, its destination needs fields that match each line item.

You'll create that destination in Zapier Tables. The finished table gives each future product row a consistent packing structure.

In this step, get ready to:

Create a blank table named Packing.
Configure the four packing fields with matching data types.
Verify the finished table structure.

Create the blank Packing table

In Zapier Tables, each row is a record. Each column is a field.

Switch back to the Zapier workspace from earlier.
Select Tables in the left sidebar.
Click Create.
Select Blank table.
Enter Packing in the Name field.
Click Create table.

You'll see an empty table named Packing with starter text fields.

That's the destination created. The table is ready for its packing fields.

Prepare the Product field

The blank table includes starter fields. You'll keep one as the product name field.

Deleting the other starter fields can feel drastic. This empty table contains no order data.

Click the header of the leftmost starter field.
Select Edit field.
Replace the Name value with Product.
Click Field Type.
Select Text.
Click the header of another starter field.
Select Delete field.
Repeat the previous two actions until Product is the only field.

You'll see a single Product header in the table.

Deleted the wrong field?

Click the Trash icon in the table toolbar.
Select the Fields tab.
Open the deleted field.
Click Restore this field.

Still stuck? Help me restore a deleted Zapier Tables field.

Add the remaining packing fields

Each field type controls what one column stores. Matching the types now keeps later line-item mapping predictable.

Click the Add field icon on the right side of the table.
Select Number.
Enter Quantity in the Name field.
Click Create.
Click the Add field icon again.
Select Text.
Enter Order in the Name field.
Click Create.

Good progress. Your table can now hold each product's quantity beside its name.

What Do These Field Types Do?

The Quantity field uses Number because it stores the amount of one product.
The Order field uses Text because order references can contain letters or punctuation.

Click the Add field icon.
Select Checkbox.
Enter Packed in the Name field.
Click Create.

Before you inspect the finished table, which field do you expect to look different from the three data-entry fields?

Scan the field headers from left to right.

You'll see Product first. Quantity appears next.

Order follows. Packed appears last as a checkbox field.

That's the table structure sorted. Each future line item now has a clear place for its packing details.

Does a Field Look Wrong?

Click the affected field header.
Select Edit field.
Correct the Name setting.
Correct the Field Type setting.

Still stuck? Help me correct my Packing table field settings.

Your Packing table now has a field for each piece of packing data. Next, you'll connect the order source that supplies those line items.

Set Up the New Order Trigger

Your Packing table in Zapier Tables now has a place for each product in an order. It needs order data before it can fill those rows.

A Zapier trigger catches each new order at the start of the workflow. This step captures a sample order with its line items. The next action can map those fields into the table.

In this step, get ready to:

Create a draft Zap with a clear name.
Connect your order-source app to the trigger.
Test the trigger with a sample order that contains line items.

Create and name the Zap

A clear name makes this workflow easy to identify when you return to it later. The Zap stays as a draft while you build its trigger.

In your Zapier account home, click + Create in the left sidebar.
Select Zap workflows from the menu.

You'll see the Zap editor with an empty trigger step. Zapier saves changes to this workflow as a draft.

Click the current Zap name in the middle of the top menu.
Select Rename.
Enter Order Line Items to Packing in the name field.

Good start. Your draft now has a name that describes the complete handoff from an order to the packing table.

Configure the new-order trigger

The trigger app supplies the order data that starts each run. Its trigger event must fire when the source receives a new order.

Select the Trigger step in the Zap editor.
Enter your order-source app in the search box.
Select your order-source app from the results.
Click the Trigger event field.
Select the event whose description says it starts the workflow when a new order is created.

Connecting an account can feel sensitive. The authorization window shows the access Zapier requests before you approve the connection.

Click the Account field.
Select the existing connection for your test order source if it appears.
Click Sign in if your order source has no existing connection.
Complete the authorization steps in the window for your test order source.

You should return to the Zap editor with your selected connection shown in the Account field.

Select the Configure tab.
Set every required field to the source that contains your sample order.

Required fields have an asterisk beside their names. Your trigger is configured once each required field points to the source containing the sample order.

What does this trigger do?

The trigger watches the connected order source for newly created orders. Each matching order becomes the starting record for one Zap run.

That record must expose the order identifier plus its line-item product names and quantities. Those fields provide the raw material for the packing rows.

Test with an order that has line items

A trigger test loads a representative order into the editor. Later steps can use that test record when you map each line item to a table field.

Select the Test tab.

Before you test, do you expect the returned record to show one product or the full set of line items from the order?

Click Test trigger.

Zapier loads one or more test records from the connected order source.

Review the data inside each returned test record.
Select the record that contains your sample order's line-item product names and quantities.
Click Continue with selected record.

You should see an order identifier in the selected test record. You should also see product names paired with quantities in the line-item data.

Can't find an order with line items?

Confirm that the trigger uses the connection for the order source containing your sample order.
Create another sample order with multiple products in your order source.
Return to the Test tab in the trigger step.
Click Find new records to load the new order.

Still stuck? Why is my Zap trigger missing the product names or quantities from my sample order?

That's the trigger ready. Your draft Zap can now receive an order with the product names and quantities needed for packing. Next, you'll connect that data to the Packing table.

Map Line Items to Packing Rows

The Packing table can hold a clean checklist. Your tested order trigger already supplies a sample order with line items.

The missing link is a mapping that keeps each product separate. The Zapier Tables Create Multiple Records action turns those collections into one packing row per product.

In this step, get ready to:

Add the Create Multiple Records action.
Connect the action to the Packing table.
Map each destination field to its matching order data.

Add the multi-record action

The automation needs an action that understands collections. Create Multiple Records handles the whole set in one step.

Click the plus sign below the tested trigger in the Zap from earlier.
Type Zapier Tables into the app search field.

You'll see Zapier Tables in the matching apps.

Select Zapier Tables from the app list.
Choose Create Multiple Records from the event list.

The action now asks which table should receive the new records.

Select Packing from the table list.

Good work. The action now points to Packing and shows its four destination fields.

Don't see the Packing fields?

Confirm that Packing is selected as the destination table.
Check that the table from earlier still contains the Product field.
Check that the table still contains the Quantity field.
Check that the table still contains the Order field.
Check that the table still contains the Packed field.

Still stuck. Help me connect my Zapier Tables action to the Packing table.

Map the order data

A field mapping connects data from the trigger to a destination field. Each mapped collection stays aligned by its line-item position.

Click the plus sign in the Product field.
Select the full line-item product-name collection from the tested trigger.

The Product field now shows a mapped token with sample values from the order.

Click the plus sign in the Quantity field.
Select the full line-item quantity collection from the tested trigger.

The Quantity field now shows its own mapped token from the same line-item group.

Click the plus sign in the Order field.
Select the order identifier from the tested trigger.

The order identifier now appears as a mapped token.

Keep the Packed field empty.

How Does One Order Become Many Rows?

Create Multiple Records pairs product names with quantities by their position in each collection.

The order identifier is copied into every new record.

An empty Packed mapping starts each checkbox unchecked.

Can't Find the Line Items?

Line-item fields can be fiddly because each order app names them differently.

Switch back to the trigger from earlier.
Select the Test tab.
Click Test trigger to refresh the sample data.
Return to the Create Multiple Records action.
Hover over the nested product-name field if the source displays a data tree.
Click Get all values.
Repeat the same choice for the nested quantity field.

Still stuck. Help me find the line-item fields in my tested order trigger.

Verify the row blueprint

The configured action is a blueprint for every row the Zap creates. The final check confirms that each destination field receives the right kind of data.

Before you check, predict how many packing rows a three-product sample order should create.

Confirm the Product field points to the complete product-name collection.
Confirm the Quantity field points to the complete quantity collection.
Confirm the Order field points to one order identifier.
Confirm the Packed field remains empty.

You should see mapped tokens in all three data fields. Packed stays empty.

That is the critical wiring complete. A three-product order is now configured to create three packing records.

Do the Mappings Look Uneven?

Confirm that Product and Quantity come from the same line-item group in the trigger.
Reselect the full collection if either field shows only one sample value.
Use Get all values when the source presents either collection as nested data.

Still stuck. Help me check whether my product and quantity mappings stay aligned.

Your row blueprint is ready. Next up, a test order fans out into separate packing rows.

Test the Packing Rows

Your new-order trigger already carries every mapped line-item value from the sample order. The next question is whether those values become a practical packing checklist.

The Zapier Tables action is ready to turn that data into records. Testing it proves whether each product stays separate.

In this step, get ready to:

Test the Create Multiple Records action with the sample order.
Inspect the Packing table for one new row per line item.
Confirm every Packed checkbox stayed unchecked.

Test the table action

An action test is live. It sends the sample data to the connected app.

This test creates real rows in Packing. Those rows are the evidence you need.

In the open Zap, select the configured Create Multiple Records action.
Select the Test tab in the action panel.

Before you run the test, how many table rows do you expect from the sample order?

Click Test step.

You should see returned results under Data out. No error should be present.

Action Test Not Completing?

Return to the Configure tab in the action step.
Confirm the selected table is Packing.
Confirm Product shows sample product names.
Confirm Quantity shows sample quantities.
Confirm Order shows the sample order identifier.

Still stuck? Help me diagnose why my Create Multiple Records action test is failing.

Verify the packing rows

The table is where you compare the result with the sample order. Use the sample product count as your reference.

Before you open Packing, how many new rows should the sample order have created?

Click the assets icon in Zapier's left sidebar.
Select Tables in the second left sidebar.
Click the Packing table name.

Compare the number of new rows with the sample order's product count.
Check each Product cell against the sample products.
Check each Quantity cell against the sample quantities.
Confirm every Order cell contains the sample order identifier.
Confirm every Packed checkbox is unchecked.

You should see one new row for each product in the sample order. Every row should contain a product name in Product.

Each row should contain its quantity in Quantity. The sample order identifier should appear in Order.

The Packed checkbox should remain unchecked on every row.

Rows Do Not Match the Sample Order?

Return to the action's Configure tab.
Confirm Product is mapped to the line-item product names.
Confirm Quantity is mapped to the line-item quantities.
Confirm Order is mapped to the order identifier.
Delete the incorrect test rows from Packing.
Run the corrected test by clicking Retest step.

Still stuck? Help me find why my sample order is not splitting into separate Packing rows.

You have the proof now. Your sample order is a row-by-row packing checklist.

Your packing rows are ready. Next up, you'll mark a few products as packed. Then you'll turn on the Zap.

Activate the Packing Zap

Your sample order is already split into a separate row for every product. That gives your packing team a checklist they can work through.

The unchecked boxes still represent outstanding work. In this step, you'll update a few products before activating the Zap for new orders.

In this step, get ready to:

Mark selected test products as packed in Zapier Tables.
Publish the Order Line Items to Packing Zap.
Confirm the Zap is active.

Mark a few products as packed

The Packed checkbox carries the checklist's human status. A checked row tells the packer that the product is ready.

Find a test row that represents a product you want to mark as packed.
Click the empty checkbox in the Packed column for that row.
Click the checkbox in one or two additional test rows.

You'll see checks on the selected rows. The remaining rows stay unchecked.

Your first packing updates are in place. The table now gives packers a clear view of completed products.

Publish the Zap

A draft holds your tested setup without processing future trigger data. Publishing tells Zapier to monitor the selected order source for new orders.

Each matching order can then run Create Multiple Records to add one packing row for every line item.

Switch back to the Order Line Items to Packing Zap in the Zap editor from earlier.
Confirm the new-order trigger card has no warning indicator.
Confirm the Create Multiple Records action card has no warning indicator.

Before you publish, consider which status you expect to see near the Zap name when activation succeeds.

Click Publish in the upper-right corner of the Zap editor.

The label near the Zap name should change from Draft to Published. The top-left toggle should show that the Zap is on.

That's the activation complete. Your packing checklist can now receive a separate row for every line item in each new order.

Can't publish the Zap?

An unavailable Publish button usually means a step needs attention.

Check each Zap step for a warning indicator.
Return to the affected step to finish any missing setup.
Confirm that you own the Zap if you are working in a shared workspace.

Still stuck? Why can't I publish my Zap? You can also ask the Zapier Community.

Your packing workflow is live. Each new order now sends one row per line item to Packing.

Each row carries its Product, Quantity, and Order values. Packed starts unchecked so packers can complete the checklist one product at a time.

Secret mission

Audit an Order End to End

One missing row can leave a product behind. Audit one existing test order against the Packing table. Prove that its row count, item details, and packing status agree with the source.

Clean Up Your Resources

This project creates no local resources or ongoing local costs. Your cleanup choice determines whether new orders keep using your Zapier Tables record allowance.

Resources you used:

The Order Line Items to Packing Zap that creates one Packing row for each order line item.
The Packing table with its test-generated rows.

Keep everything running

No action is needed. Choose this option while you still want new orders to become packing rows.

New orders continue to add one Packing row per line item.
Existing Packed checkbox states remain available.
Each added row counts toward your Zapier Tables record allowance.

Your packing checklist remains active for incoming orders.

Pause - I'll come back to this later

Pause new records while keeping your existing checklist ready for another session.

Switch back to the Order Line Items to Packing Zap from earlier.
Use the Zap's on/off control to turn it off.
Confirm that the Zap shows an off state.

Your automation is safely paused. The Packing checklist remains ready for your return.

Delete - I don't want to use this again

Deleting Packing permanently removes every test row. The cleanup stays contained to this project table because your selected order source remains connected to Zapier.

Stop the Zap:

Switch back to the Order Line Items to Packing Zap from earlier.
Use the Zap's on/off control to turn it off.
Confirm that the Zap shows an off state.

Delete the Packing table:

Return to the Packing table in Zapier Tables.
Open the table's options menu.
Select the table deletion option.
Approve the confirmation prompt for Packing.
Return to your Zapier Tables table list.
Confirm that Packing is no longer listed.

Your test packing data is gone. The disabled Zap can no longer create new rows.

Nice Work!

You did it! Your turned-on workflow now transforms each new order into a practical packing checklist using Zapier.

Every product gets its own row in the Packing table. Packers can track each item through its own Packed checkbox.

You've learned how to:

Built an automated order-to-packing workflow that creates a separate record for every line item in a new order.
Mapped line-item data into the Packing table with Zapier Tables. Product names land in Product. Quantities land in Quantity. The order identifier lands in Order.
Verified the one-row-per-product result with a sample order. You also used the Packed checkboxes to track selected items.
Completed an optional Secret Mission to push your order automation skills further.

Ready to quiz yourself?