Transformations

Your data, your rules

Every e-commerce stack has its own quirks. Shopify sends SKUs one way, your warehouse expects them another. Addresses need normalizing. VIP customers need flagging. Transformations let you write a few lines of JavaScript that fix all of it — automatically, on every order.

No more spreadsheet gymnastics. No more manual data cleanup. Write it once, test it against real orders, and let it run.

RAW ORDER FROM SHOPIFY
sku: "SH-COLD-PACK-LG"
tags: []
total: 249.99
address.state: "california"
transform
TRANSFORMED OUTPUT
sku: "WH-COLD-PACK-LG" ← mapped
tags: ["high-value", "vip"] ← flagged
total: 249.99
address.state: "CA" ← normalized
The editor

Write it, test it, ship it

The transformation editor isn't a toy. It's a real code environment with a visual field browser, live testing against actual orders, and priority chaining so you can compose complex pipelines from simple building blocks.

Visual field browser

Click any field from a real order — SKU, address, tags, line items — and it inserts into your code. No guessing field paths.

Test with real data

Enter any order ID, run your transformation, and see the exact output before you save. Catch bugs before they hit production.

Priority chaining

Stack multiple transformations that run in sequence. SKU mapping at priority 10, VIP tagging at 20, address normalization at 30. Each receives the previous output.

Four trigger points

Run on order ingest, order export, shipment ingest, or shipment export. Target the exact moment data needs transforming.

sku-mapping.js
vip-tagger.js
order_ingest · priority: 10
1
2
3
4
5
6
7
8
9
10
11
12
13
14
// Map Shopify SKUs → warehouse codes
for (const item of data.line_items) {
item.sku = item.sku
?.replace("SH-", "WH-");
}
 
// Tag high-value orders for VIP handling
if (data.totals?.total > 200) {
data.tags = [...(data.tags || [])];
data.tags.push("high-value", "vip");
}
 
// Normalize state abbreviations
data.address.state = normalize(data.address.state);
Test result: Order #4201Pass — 3 fields modified
Use cases

Transformations teams actually use

SKU mapping

order_ingest

Your storefront SKUs don't match your warehouse codes. Map "SH-COLD-PACK-LG" → "WH-COLD-PACK-LG" automatically on every ingest.

VIP flagging

order_ingest

Automatically tag orders over $200 as "high-value" so your ops team prioritizes them. Add custom tags based on any order field.

Address normalization

order_export

Customers type "california", "Calif.", "CA". Normalize state codes, zip formats, and country codes before they hit your carrier API.

Line item restructuring

order_export

Split bundles into individual items, merge sample packs, or add handling instructions based on product type.

Weight calculation

shipment_ingest

Look up product weights from your catalog and calculate total shipment weight before rate shopping. No more manual weight entry.

Tracking enrichment

shipment_export

Append carrier-specific tracking URLs, estimated delivery dates, or custom status messages to shipment data on export.

Stop cleaning data by hand

Write your first transformation in minutes. Test it against real orders. Never manually fix a SKU again.