Items, dates & probability

Elevate plan

The products of a commitment are its items. Each item says how many units of one variant you expect to need, where, when, and how likely that is. You add and edit items on the commitment’s Items tab while the commitment is Draft or Confirmed. Changes save as you make them: a quantity or probability when you click away from the field, a location or date as soon as you pick it.

The Items tab

The Items tab shows the commitment’s details, then the Items table:

Column	What it shows
Product / Variant	The product and variant.
Location	Where the demand happens.
Estimated qty	The units you expect to need if the demand happens in full.
Probability %	How likely this item is. Empty means it uses the commitment’s default probability, shown in grey.
Target date	When the demand happens. Plan default means it uses the commitment’s date.
Expected qty	Estimated qty times probability, rounded to whole units. This is what the forecast counts.

Each column header has an info button with a short explanation. The table shows 25 items per page.

A commitment without items says “No items yet” with the Add items button in the middle of the card.

Adding items

Click Add items above the table and pick a way:

Add from Shopify: browse your products and tick the variants.
Virtual materials: pick raw materials you manage in Assemblified.
Scan barcode: scan products with a barcode scanner, or type a barcode or SKU; see the walkthrough below.
Upload CSV: add items from a spreadsheet; see Uploading items from a file.

A variant can be on a commitment only once. In the product picker, a variant that’s already on it is marked Already added and can’t be ticked. If someone else added the same product in the meantime, Logistified skips it and says so, for example “1 already on the plan (skipped)”. See Adding products to a plan.

Items you pick from Shopify or from your virtual materials start with an Estimated qty of 0, with the commitment’s date and probability. They go to the location most of the commitment’s items are at (your first location while no item has one). Type each item’s quantity, and change its location if needed.

Add items by scanning

On the commitment’s Items tab, click Add items › Scan barcode. The “Scan to add items” dialog opens: “Scan a barcode or SKU; the count becomes the estimated quantity. Re-scans accumulate.”
Scan a barcode or SKU. The product appears in the list with a count of 1.
Scan the same product again for each unit: every scan adds one to its count. You can also type the count.
Check the list. New products are marked Add; products already on the commitment are marked Update, and their count is added to the quantity they already have.
Click Add N items. The count becomes each new item’s Estimated qty, at the location most of the commitment’s items are at. Logistified confirms with, for example, “2 added, 1 updated”.

To close without adding anything, click Cancel. If you’ve already scanned, Logistified asks “Discard scan results?” first.

Location per item

Pick a location in the item’s Location column:

A location: the demand counts in forecast views that include that location.
Unallocated (all locations): the demand counts once in forecast views that cover all your locations, and not in views limited to some locations. A view covers all locations when it’s set to All locations or when it picks every one of your locations. Pick a location to count it there.

A commitment can have items at different locations. The list’s Location(s) column then reads “Multiple (n)”. See Plans in the forecast.

Dates per item

By default, every item uses the commitment’s Target date and shows Plan default. Point at it to see the date, for example “Inherited from plan: Mar 1, 2027 – Mar 31, 2027”. To give one item its own timing, click its Plan default (or Set date / Set range if the commitment has no date yet):

On a commitment with a single date, click one day for the item. It’s saved straight away; Done closes the calendar.
On a commitment with a date range, click a start and an end, then click Done. If you click only one day, the item gets that single day.
Clear removes the item’s own date, so it uses the commitment’s date again.

What the forecast uses: the item’s own date when it has one, otherwise the commitment’s. A single date puts the whole expected quantity on that day; a range spreads it evenly over every day. Days that have already passed don’t count.

An item keeps its own timing even if you later switch the commitment between a single date and a date range. Such an item has a tooltip saying so, for example “This item keeps its own single date while the plan uses a date range. Clear it to use the plan default.”

Probability per item and Expected qty

Type a number from 0 to 100 in Probability % to give one item its own probability. Leave it empty to use the commitment’s Default probability.

Expected qty is calculated for you: Estimated qty times the probability. An item of 200 units at 50% has an expected quantity of 100. That’s the number the forecast adds while the commitment is Confirmed or Locked and not excluded from the forecast.

Use item probabilities when parts of a deal are less certain than others. For example, a customer is sure about the core range (100%) but only considering the new colours (40%).

Every change to an item is recorded on the Activity tab with the product, its location and what changed, for example “Updated Mug · Blue at Berlin: date Plan default → Nov 5, 2026 – Nov 6, 2026”.

Uploading items from a file

To add many items to an existing commitment at once, click Add items › Upload CSV. The “Upload commitment line items” dialog accepts CSV and XLSX files: “Add items to this commitment from a CSV/XLSX. Match by SKU or barcode; quantity sets the estimate.” To start from a template, click Example file › Download CSV or Download XLSX.

The file needs a SKU or Barcode column and a Quantity column. Optional columns: Location, Target date, Start date and End date, and Probability %. A new product whose row has no location, or a location name Logistified doesn’t recognise, goes to the location most of the commitment’s items are at.

After the upload, the Review line items step shows what will happen, for example “12 to add · 3 to update · 1 not found”:

New products are marked Add and added as new items.
Products already on the commitment are marked Update → n: the file’s quantity is added to their current Estimated qty, and the file’s dates, location and probability replace theirs. Below the product, the review lists what changes, for example “Target date → Dec 5, 2026 · Probability → 50% · Location → Munich”. A cell left empty keeps the item’s current value.
Values that can’t be applied are named in amber below the product, with the reason. For example, a location name Logistified doesn’t recognise is not applied to a product that’s already on the commitment: ‘Location “Berln” not applied: it matches no location of this shop.’ The product keeps its location. A row with both a Target date and a Start date and End date uses the start and end, and the review says the target date is not applied.
Rows without a quantity above 0, or without a SKU and a barcode, are left out, and the review counts them, for example “2 rows left out: no quantity above 0, or no SKU or barcode.”
Rows for the same product are added up into one item. Its location, probability and dates come from the last of those rows, and the review says so: “2 rows combined: dates, location and probability from the last row”.
Rows whose product isn’t found are marked Not found and left out.

Click Import N items to apply. Logistified confirms with, for example, “Imported 12 new items and updated 3 items (1 not found)”. If the items can’t be saved, the review stays open and says why. Use Change mapping or Upload a different file to start over.

Removing items

Click the trash button at the end of an item’s row (“Remove item”). The item is removed straight away, without a question, and stops counting in the forecast. You can add it again later.