Skip to main content

How Trackstar billing attribution works

Some warehouse systems send their billing through Trackstar. Star WMS does, for example. Each bill is one charge: an outbound handling fee for an order, a labeling fee, a day of storage, an inbound handling fee for a receipt, or an account charge. Each one carries the warehouse system's own code for the charge, its amount, its charge date, and, when the system sends one, the number of the invoice it's billed on.

When billing attribution is on, SKU.io copies every bill and asks one question of each: what caused this cost? The answer decides where the money lands. This page explains that decision. The tasks that act on it are Map Trackstar charges and Review Trackstar bills and fix unattributed charges.

From charge to destination​

Every charge code has a row in the connection's Charge mapping. The row gives the code a readable Display name, a Family, and a Treatment. The treatment says what kind of record SKU.io writes. The bill's own reference (an order, an inbound shipment, or nothing at all for storage) says which order or purchase order it's written against.

FamilyExample charge codes (Star WMS)Default treatmentLands on
FulfillmentOUTBOUND B2C S02, LabelingOrder feeA cost line on the sales order, type 3PL Fulfillment Fee
Storage产品库存仓租 (Storage — products (daily)), 箱库存仓租 (Storage — cartons (daily))Product storageThe monthly 3PL Storage Fees cost entry
ReceivingIB EH01 (Inbound handling)PO receivingThe purchase order, through the monthly 3PL Receiving Fees cost entry
ReturnsReturn processing codesReturn feeA cost line on the original sales order
ShippingFreight or postage codesOrder freightThe order's freight line
OtherAccount management, and any code SKU.io can't placeKeep unattributedThe monthly Unattributed 3PL Fees cost entry

How a charge code gets its mapping​

Warehouse systems use their own codes, and some send them in Chinese. The first sync that sees a new code adds a row for it, filled in like this, first match wins:

  1. Known codes for that warehouse system. The documented Star WMS codes come with an English display name, such as 产品库存仓租 → Storage — products (daily) and IB EH01 → Inbound handling. These rows say Seeded default.
  2. Words in the code, in English or Chinese. A code containing "outbound", "label", "pick", or "pack" is a Fulfillment fee, "storage" or 仓租 is Storage, "inbound" or "receiving" is Receiving, and so on. OUTBOUND B2C S02 and Labeling are mapped this way, with the code itself as the display name. These rows say Created by sync.
  3. Anything else, such as Account management, goes to the Other family as Keep unattributed, with a Review chip, so it's counted as overhead until you decide.

SKU.io never machine-translates a code. Rename any code to what you call it, on the Billing settings tab. See Map Trackstar charges.

Order fees land on the sales order​

An order fee becomes one cost line on the sales order it was charged for. On the order's Cost Lines card, each line written from Trackstar billing shows a Trackstar · Star WMS chip (the chip names your warehouse system) next to its type. Its description names the charge and the warehouse system's order reference, such as OUTBOUND B2C S02 · Star WMS OBS022610139LN. Below the lines, 3PL fees totals them, for example 3PL fees: $3.10 (2 fees from Trackstar billing).

The Cost Lines card on sales order SO-DOCS-0003 with two 3PL Fulfillment Fee lines tagged Trackstar · Star WMS, OUTBOUND B2C S02 for $2.75 and Labeling for $0.35, and a 3PL fees total of $3.10

The line is spread across the order's lines by its line type's rule, so each product's margin carries its share. These lines feed per-order and per-product margin and the profitability reports. They don't create accounting entries.

Because each line is spread across the order's lines, the fees also add up on each product. A product's Analytics page has a 3PL cost card that totals the 3PL fees on its orders over the last 30d or 90d, by cost line type, with the cost per unit sold.

The 3PL cost card for HL-CHAIR-WALNUT over 90 days: 3PL Fulfillment Fee $8.01, 5 units sold, $1.60 per unit, from Reno Fulfillment

Storage is a monthly period cost​

Star WMS bills storage once a day for the whole account, not per product. SKU.io adds each month's storage charges into one 3PL Storage Fees cost entry. Because the charge names no product, the entry stays unallocated: it shows in Profitability as overhead for the month and isn't spread onto products. If you'd rather share it out, set Split un-itemised storage to By on-hand units — allocate to products, and each month is allocated across your products by the units the warehouse holds of each.

Storage is never added to inventory value or cost of goods sold.

Receiving fees go to the purchase order​

An inbound handling fee names the warehouse system's inbound shipment. SKU.io looks for the purchase order behind it, first match wins:

  1. The purchase order the shipment was sent from, when you sent the ASN from SKU.io.
  2. The purchase order number on the inbound shipment, when exactly one SKU.io purchase order has that number.
  3. The products on the inbound shipment, weighted by their expected quantity, when there's no purchase order.

By default the fee is allocated to that purchase order or those products for reporting only, through the monthly 3PL Receiving Fees cost entry. Turn on Capitalise receiving into PO landed cost and the fee becomes a cost line on the purchase order instead, part of the stock's cost. If none of the three matches, the fee is unattributed as Purchase order not found.

How a charge finds its order​

A charge on an order names the warehouse system's own order number, such as OBS022610139LN. SKU.io follows it in two steps:

  1. The Trackstar order. SKU.io finds that order in the orders it has synced from Trackstar, or asks Trackstar for it if it hasn't synced yet.
  2. The SKU.io sales order. If SKU.io sent the order to the warehouse, the fee goes on the fulfillment it was sent as. If your sales channel sent the order to the warehouse directly, SKU.io matches the channel's own order number to exactly one SKU.io sales order. When two sales orders share the number, the one routed to a warehouse mapped to this connection wins. If that still leaves more than one, the fee is unattributed as Ambiguous order.

The bill drawer lists each lookup under Resolution trace, with a green tick where it matched and a red cross where it didn't.

Pending and unattributed​

A charge can arrive before its order reaches SKU.io, so a charge that can't be matched yet is Pending, not unattributed:

  • Pending charges are retried on every billing run.
  • A pending charge that still can't be matched 14 days after its charge date becomes Unattributed with the reason Order not imported. Usually the order came from a sales channel you don't import into SKU.io.
  • A charge for an order placed before its sales channel's start date in SKU.io is Shipped before the sales channel went live straight away. SKU.io never imported those orders on purpose, so there's nothing to fix.
  • An inbound handling fee waits as Pending until its inbound shipment syncs from the warehouse. Once the shipment is in SKU.io, a fee that matches no purchase order or product is Purchase order not found straight away.
  • Kept unattributed by fee mapping is unattributed straight away too, because the mapping asked for it.

Unattributed never means lost. Every unattributed charge goes into that month's Unattributed 3PL Fees cost entry, which shows as unallocated overhead in the profitability reports. SKU.io never spreads it onto products that didn't cause it, because that would make those products look less profitable than they are.

A charge for $0.00 is still attributed, but writes no line.

Changes are re-applied for you​

Warehouse systems sometimes change a bill after the fact: a new amount, or a later charge date when offline work is added. SKU.io picks up the change on the next sync, removes whatever the old version wrote, and attributes the new version. The order is recalculated once. Changing a charge's treatment or line type, or any billing setting, re-attributes the bills it affects in the same way. Renaming a charge changes no figures.

Everything adds up​

For the period you're looking at, the Bills tab holds this identity:

On orders + Storage + Receiving + Unattributed + Pending + Excluded = Total billed

The Reconciliation tab shows it as one bar, with a Reconciles line under it when every bill has a status. Then the Invoices tab checks each of your warehouse's invoices against the total on the warehouse's own invoice file. See Reconcile Trackstar invoices.

Attribution is for analytics. It shapes order and product margin and the profitability reports, and writes no journal entries of its own. Capitalised receiving fees are the one exception, because they change the cost of the stock they're added to.

Next steps​

Video transcript

When your warehouse bills through Trackstar, SKU.io can put each charge on the sales order or purchase order that caused the cost. This bar shows where every dollar went, and what is still unattributed. Everything that decides where a charge lands is configured on the connection. Open Settings from the connection's sections on the left. Then choose the Billing tab, under Money in the settings list. Attribute Star WMS bills is the master switch. Billing start date sets the first charge date that counts. Attribute to orders puts handling and labeling fees on the sales order. Attribute storage adds daily storage to a monthly cost entry. And capitalising receiving makes inbound handling part of the stock's cost. Below, the charge mapping lists every code the warehouse bills under. Each code, like OUTBOUND B2C S02, gets a display name, a family, and a treatment. Star's storage codes arrive in Chinese, and each one gets a readable display name. A code nobody recognizes is kept as overhead and flagged for review. On the Bills page, the All bills tab lists every charge. The cards split the total billed by where it landed. On orders is the share that reached sales orders. Each card is also a filter. Click Unattributed to list only the charges that landed nowhere. Now only those charges are listed. The Attributed to column gives each reason, such as Purchase order not found. Its drawer lists every lookup that was tried for this charge. The inbound shipment lookup matched. But the shipment names no purchase order, and lists no products. Link the shipment to a purchase order, then click Re-attribute. To follow one order, search by the warehouse's order reference. Each charge on that order has its own row, like Labeling. Select the outbound handling charge, and its drawer shows how it was matched. The trace matched the channel's order number to a sales order. Written to shows the cost line it created. Click the sales order to see where the fees went. On the sales order, each fee is a cost line tagged Trackstar. 3PL fees totals them, so the order's profit carries the real warehouse cost. The Invoices tab groups charges by the warehouse's own invoice number, one row per invoice. The first one already has its statement amount, so it's reconciled. For the next one, enter the total from Star's own invoice file. It's eighteen fifty more than the bills, so the status flags the difference. Star's file can include offline work orders that never come through the API. Click a row to list that invoice's bills. The bills list opens, filtered to that invoice.

Last verified: