Review fulfillment costs
When VeraCore ships an order it tells SKU.io what the freight cost. You can see that figure on the report task rows as Freight, and on the fulfillment itself.
By default it stops there — a number recorded against the shipment, not part of your accounts. The Financial tab is where you connect it, so every shipping cost VeraCore reports becomes a financial line on the sales order.
What the setting does
There is one setting on the tab: Fulfillment Cost Financial Line Type.
When set, a financial line is created for each fulfillment's shipping cost returned by VeraCore. Only Cost-classified financial line types are allowed.
Pick a type, save, and from then on every fulfillment that comes back from VeraCore with a shipping cost gets a financial line of that type, carrying that amount.
Clear it and the behaviour stops. The costs are still reported by VeraCore and still visible on the fulfillment — they just stop becoming financial lines.
Only cost types appear
The dropdown lists only financial line types classified as Cost. This is a freight expense; recording it as revenue would be wrong in a way that is tedious to unpick afterwards, so the interface will not let you.
Each option shows its classification underneath the name, so if you have several similarly named types you can tell them apart before selecting.
If the list is empty or does not contain what you want, create the type first in the financial line type settings, then come back.
The change is retroactive — read this before saving
This is the one genuinely surprising thing about the page, and it is what the warning at the top is for:
Heads up: Changing this type will update financial lines on all past fulfillments in this warehouse — not just future ones. Setting it for the first time will backfill lines for every past fulfillment with a shipping cost.
Most settings in SKU.io take effect going forward. This one reaches backwards, and deliberately so — a shipping cost that only applies to shipments after a Tuesday afternoon makes for a useless cost report.
But it does mean that saving this setting is a bulk edit to historical financial data. Two things happen, depending on what was there before:
| What happens | When |
|---|---|
| Rewire | A financial line already exists for that fulfillment's cost. It changes type but keeps its amount |
| Backfill | No line existed. A new one is created with the cost VeraCore reported |
Neither invents a number. The amount always comes from what VeraCore reported on that fulfillment — this setting only decides whether, and under which type, it is recorded.
Save it
- Open the connection's Financial tab.
- Pick a type in Fulfillment Cost Financial Line Type, or clear it to switch the behaviour off.
- Click Save Changes.
Save Changes stays unavailable until you have actually changed something, and a Discard button appears alongside it while there are unsaved changes.
Clicking save does not save yet. It opens Confirm Financial Line Type Change and calculates what your change would do — Calculating impact... — before asking you to commit.
Read the impact preview
The dialog tells you the blast radius in advance:
This change will retroactively update financial data on N existing sales orders.
with a breakdown beneath it:
| Row | Means |
|---|---|
| Sales orders impacted | How many sales orders will have their financial data changed |
| Existing lines rewired to new type | Lines that already exist and will change type, keeping their amount |
| New lines backfilled for past fulfillments | Fulfillments that had no line and will get one |
The two detail rows only appear when they are non-zero, so a pure first-time setup shows only a backfill count.
If nothing historical is affected, the dialog says so plainly instead: No past fulfillments will be affected by this change. That is the safe case — a brand-new connection, or a change with no shipped history behind it.
Cancel leaves everything exactly as it was. Confirm & Save commits.
On a connection with real history this can be large. It is not a warning that something is wrong — retroactive is the intended behaviour — but it is worth reading rather than clicking through, particularly if your accounting period is closed.
If the count surprises you, cancel and check the type you selected before committing.
After saving
Small changes apply immediately and you get Financial settings saved.
When there is history to reconcile, the work runs in the background: Financial settings saved — backfill running in the job tray, under the job name Reconcile Fulfillment Cost Financial Lines:. The page refreshes itself when the job finishes, so you can leave it open.
Give it time on a large connection. The financial lines appear on the sales orders as the job works through them, not all at once.
Where the costs come from
Worth being clear about the chain, because a missing cost is usually missing further upstream than this tab:
- VeraCore ships the order and records the freight cost.
- The Dynamic Report returns that cost alongside the tracking number — the Freight column on the task rows.
- SKU.io stores it on the fulfillment.
- If this setting is configured, a financial line is created for it.
So if a fulfillment has no cost line, work backwards. Is there a cost on the fulfillment? If not, did the report row carry a Freight value? If VeraCore did not report one, there is nothing for this setting to record, and the fix is with your 3PL's report definition rather than in SKU.io.
Next steps
- Set up tracking with Dynamic Reporting — the pipeline that delivers the freight figures.
- Sync and link orders — the fulfillments these costs attach to.
- Settings reference — every other connection-level setting.