Skip to content
NewAI dashboards.See how →
Open MammothTry free
Workflow · Stock and products · Opening soon

Landed cost by SKU

Use your Shopify order, shipping label, and product exports to allocate freight, duty, and fees by SKU value. You get landed cost per unit for each order SKU, with status flags for matches and exceptions.

Early access opens shortly. Check back soon.

Book a demo
Someone typed

“match our shopify orders to the shipping labels, spread freight duty and fees by each sku’s share of the order value, show landed cost per unit for every order sku, with Status "Agrees" when the label matches and costs look normal, else missing, duplicate, or cross-border”

The agent read it as

match our Shopify orders to the Shopify shipping labels, spread freight duty and fees by each sku’s share of the order value, show landed cost per unit for every order sku, with Status "Agrees" when the label matches and costs look normal, else missing, duplicate, or cross-border, using Shopify products for cost per item

What the agent built

6 steps, each one an ordinary Mammoth step you can open and change.

  1. File
    Shopify orders
    CSV export · 14 rows
  2. File
    Shopify shipping labels
    CSV export · 14 rows
  3. File
    Shopify products
    CSV export · 12 rows
  4. Step
    Normalize order lines
    Step 1
  5. Step
    Sum labels by order
    Step 2
  6. Step
    Normalize skus
    Step 3
  7. Join
    Add label costs
    13 of 14 paired
  8. Join
    Add product cost
    14 of 14 paired
  9. Step
    Calculate landed costs
    Step 6
  10. Result
    Order SKU landed costs
    14 rows · 4 flagged
  11. Schedule
    Runs when you say
    Proposed

Checked on the sample files: every step ran, 14 rows came out, and the join paired 13 of 14 rows; the join paired 14 of 14 rows.

What you get back

The result of that run, the rows to look at first.

Order SKU landed costsSample data14 rows
10 agrees2 cross-border1 duplicate1 missing label
Order idOrder SKUQuantityLine subtotalShipping countryShipping methodLabel countFreightDutyFeesLabel totalProduct unit costAllocated freightAllocated dutyAllocated feesLanded cost per unitStatus
#1004SDC-SA6120CAStandard1126.200.5018.706.75126.200.509.87Cross-border
#1009LMT-IN496GBStandard1143.800.5518.359.60143.800.5514.19Cross-border
#1014TSB-SL4128CAPriority22200.8022.8013.402200.8019.10Duplicate
#1013AMG-12236USStandard·····7.250007.25Missing label
#1006MDL-BK158USOversize11600.9016.9026.501600.9043.40Agrees
#1005RHJ-A5254USGround1800.308.3011.20800.3015.35Agrees
#1001AMG-12472USStandard19.5000.359.857.259.5000.359.71Agrees
#1007AMG-16363USStandard19.5000.409.908.109.5000.4011.40Agrees
#1008TSB-FO264USPriority11100.4011.4013.401100.4019.10Agrees
#1002TSB-SL396USPriority11100.4011.4013.401100.4017.20Agrees
#1011RHJ-B6381USGround1800.308.3011.20800.3013.97Agrees
#1012MDL-WH2116USOversize11600.9016.9026.501600.9034.95Agrees
14 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How do you allocate landed cost by SKU from Shopify exports?

Export your Shopify orders, shipping labels, and products, then load them into the workflow. It matches orders to labels, spreads freight, duty, and fees across SKUs by each SKU’s share of order value, and calculates landed cost per unit. Rows that match the label and look normal are marked Agrees. Rows can also be flagged as missing, duplicate, or cross-border when they do not match the expected pattern.

How it works

How to use the Order SKU landed costs workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and checked on the sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Order SKU landed costs: questions

Which Shopify export should I use?
Use your Shopify orders export, your shipping labels export, and your products export. The workflow uses the order data, the label costs, and the product cost per item.
What happens to rows that do not match?
They stay in the output with a status flag. For this workflow, rows can be marked missing, duplicate, or cross-border when the records do not line up or the costs do not look normal.
How do I change the rules?
You change the rules by editing the written steps and matching conditions in the workflow. You can adjust how orders, labels, and SKUs are matched, and how costs are spread across line items.

Get early access to this workflow

It will open already built and checked on the sample files. Swap in your own exports and see your result.

Early access opens shortly. Check back soon.

Book a demo

Workflows like this

Find the few products that make most of your sales, what sells together, and the stock that sits too long.

All stock and product templates →

Keep reading

Read nextAll workflowsDescribe yours, or start from one the agent already built.Take a lookProductData EngineConnected sources, cleaning and scheduled refresh.Take a lookConnectorsConnectorsBring the data in from the tools you already use.Take a look