Orders and consignments that cannot be priced

Forensik never guesses. A consignment missing something shows Cannot price with the reason, and its expected cost and price stay empty. Approving a rate card or fuel levy version effective on or before the ship date re-prices the consignments it covers.

No cartons

Cannot price: Order number: no cartons set up for SKU code

Cause. An order line names a SKU with no cartons, or a SKU code Forensik does not know. An order keeps the cartons its SKUs had when it was taken.

Fix. Set up the SKU with its cartons, using your store's exact code. That fixes new orders. Adding cartons later does not re-price orders already in Forensik: this is a known limit.

When to contact support. For orders already showing this reason that you need priced, contact support with the order numbers.

SKU not set up

SKU code is not set up in FORENSIK

Cause. A cart in Test a quote or at checkout holds a SKU code with no matching SKU, or a store product with no SKU at all ("a cart item has no SKU").

Fix. Add the SKU with its cartons on the SKUs page, with the same code as your store, or give the store product its SKU. See SKUs and cartons.

When to contact support. If the SKU exists with that exact code and the message remains, contact support.

No rate card in force

No approved rate card version is in force for the service on the ship date

Cause. The service has no approved rate card covering the ship date, or the consignment names no carrier service ("has no carrier service, so no rate card applies").

Fix. Import the service's rate card with an effective date on or before the ship date, and approve it. See Rate card approval.

When to contact support. If a consignment has no carrier service, or an approved card covers the date, contact support.

No fuel levy in force

No approved fuel levy version is in force for the carrier on the ship date

Cause. The carrier, or the service, has no approved fuel levy covering the ship date.

Fix. On Fuel levies, add a version with an effective date on or before the ship date and approve it. See Fuel levies.

When to contact support. If an approved levy covers the date, contact support.

No markup in force

No global markup rule version is in force on the date

Cause. No global markup was in force when the order was priced. Every organisation starts with a 0% global markup, so this is rare.

Fix. Check the global markup on the Pricing page. Markups cannot be back-dated.

When to contact support. For consignments showing this reason, contact support.

Postcode or weight not on the rate card

Postcode not on rate card

Cause. The rate card in force has no zone for the origin or destination postcode, no band for that lane and rated weight ("No rate for this lane or weight"), or could not rate it ("Rate card problem").

Fix. Import a corrected version effective from the ship date and approve it.

When to contact support. If the card covers the lane and weight, contact support with the consignment.

Invoice lines not checked

The consignment has no expected cost (it could not be priced), so its charges could not be checked

Cause. The freight audit compares invoice lines with the expected cost, and this consignment has none.

Fix. Clear the consignment's reason above. When an approval re-prices it, its invoice lines are checked again.

When to contact support. If the consignment is priced and its lines are still unchecked, contact support.