Products, growth & targets
The Products tab of a sales plan has one row per product. It’s where you adjust a product’s growth, set its total target in units or revenue, and add or remove products. For targets per week or month, use the plan grid.
On this page
Section titled “On this page”- The Products tab
- How a target is seeded
- Changing growth for one product
- Growth from sales history
- Recalculate targets
- Products sold under a year
- Products that need data
- Changing a target
- Revenue
- Adding products later
- Products not in Shopify yet
- Removing a product
- Products deleted in Shopify
- Searching the tab
- See also
The Products tab
Section titled “The Products tab”The tab follows the location switcher. At one location, each row is that product at that location. On All locations, each row adds the product up over every location of the plan. When you pick several locations, each row adds the product up over those locations only.
| Column | What it shows |
|---|---|
| Product | The product and variant. While the plan is Draft or Confirmed, the checkbox in front of it selects it for Recalculate targets. A product sold under a year shows under its name how it is estimated; see Products sold under a year. |
| Growth | How much the targets are above or below last year, in percent, for example +20 or −10. On a row that adds up several locations it reads Mixed when the locations have different growth. A growth measured from sales history names its method when you hover it, and a Not enough data badge marks the rate for products without enough data; see Growth from sales history. |
| Last year | Units sold in the same dates one year earlier. “-” means no sales history there. On All locations, the sum of the locations with history; hover the number to see which locations have none. |
| Target units | The product’s target over the whole plan. |
| Target revenue | The same target in money, in your shop’s currency. |
| Locations | On All locations, or with several locations picked: at how many of the locations shown the product has a target above 0, for example 3 of 3, or 2 of 3 with three locations picked. Hover it to see where it’s planned and where nothing is. |
At the end of each row, while the plan is Draft or Confirmed, are the ⋯ menu with Recalculate targets… and the bin icon to remove the product.
A long product name is cut short. Hover it, or move to it with the Tab key, to read it in full. On a narrow screen the Product column stays in place while you scroll the other columns sideways.
Growth, Target units and Target revenue are editable while the plan is Draft or Confirmed. Type a value and press Enter or click away; press Escape to undo what you typed. A comma works as the decimal mark too. Rows with unsaved changes are highlighted, and the changes are held in the save bar at the bottom of the page until you click Save changes. See Saving changes.
Units can have two decimals, because targets are planned day by day. When any product in the column has decimals, the whole column shows two.
The Details card above the table is described on the Sales Plans overview.
How a target is seeded
Section titled “How a target is seeded”When a product joins the plan, its target at each location is seeded from that location’s own sales:
- Each day of the plan takes the same day one year earlier at that location.
- That is multiplied by the product’s growth, so +20% means 1.2 times last year.
- The target keeps last year’s seasonal shape: a busy December last year means a busy December in the plan.
Only sales count as last year. If your shop is connected to an ERP (for example Fishbowl), the stock its completed work orders used up as ingredients or components is not a sale: it is left out of Last year, of growth from sales history and of new targets. Targets a plan already has stay as they are.
Each day’s target is rounded to two decimal places. “Last year” means the same calendar dates one year back, and leap days are handled as described in Creating a sales plan.
Logistified only reads days that are over. When the same date one year back is today or later, the day takes the same date two years back. So a plan that starts in the future reads the most recent full year. For example, a plan for 2027 created on 7 November 2026 reads 1 January to 6 November 2026 for its days up to 6 November 2027, and 7 November to 31 December 2025 for the rest. Last year is worked out the same way each time you open the plan, so until the plan starts it moves to more recent days as time goes by.
Sales at other locations are never copied over. A product that didn’t sell at a location last year starts at 0 there, and its Last year reads “-”. Type a target for it yourself.
A product that started selling at a location less than a year ago is different: it gets an estimated full year there instead of its few months, even if it didn’t sell on last year’s dates, and its growth works on the estimate like on any other product. See Products sold under a year. Only without an estimate does it start from last year’s days like every other product: when the estimate is switched off, when Use actual sales from last year is chosen for it, or when its source couldn’t estimate it (its badge then says why).
Changing growth for one product
Section titled “Changing growth for one product”Every product starts with the growth you chose when you created the plan. Products you add later start at 0%. To change one product:
-
Click the product’s Growth field.
-
Type the new growth, for example 30 for +30% or -10 for -10%, and press Enter. The targets change straight away.
-
Click Save changes in the bar at the bottom of the page.
How the change is applied:
- The targets scale with the growth. Going from +20% to +30% multiplies the targets by 1.30 ÷ 1.20. Changes you made by hand in the plan grid keep their proportions, and a revenue you typed scales by the same ratio.
- A target at 0 is seeded again. If the product was at -100%, or its targets were all 0, there’s nothing to scale. Logistified seeds it again from last year’s sales at the new growth, or, for a product sold under a year with an estimate, estimates its year again from its source. While it loads, the row is locked with a spinner and Save changes waits. A location with no sales last year and no estimate stays at 0 and a message says so, for example “No sales last year for Mug at Hamburg, so growth wasn’t applied there.”
- On All locations, growth applies to the product at every location. With several locations picked, it applies at those locations only. If the locations have different growth, the field reads Mixed.
- A growth you type replaces a measured one. If the product’s growth came from its sales history, typing a new one removes the method from the hover and the Not enough data badge.
Growth can be anywhere from -100% to +900%. Outside that range the field says “Growth must be between −100% and +900% (factor 0–10×).” and nothing changes. Between -99% and -100%, only -100% itself is allowed. Growth is shown to one decimal, for example +12.5.
Changing a target directly doesn’t change the growth. A product with no sales last year that is at -100% can’t be grown at all: its Growth reads n/a (“No sales here last year. Type a target instead”). A product sold under a year with an estimate can: its Growth works as on any other product, and growing it from -100% estimates its year again (see Products sold under a year).
Growth from sales history
Section titled “Growth from sales history”Instead of one percentage for every product, Logistified can measure each product’s growth from its own sales, separately at each location. You choose this when you create the plan, with From each product’s sales history (see Creating a sales plan), and you can measure it again on a running plan with Recalculate targets.
What is compared
Section titled “What is compared”Each product is measured at each location from what it sold at that location. Sales at other locations never count.
- The last 12 months are compared with the 12 months before. Average yearly growth (CAGR) and Trend, damped also use the 12 months before those, so up to three years.
- The last 12 months are the 12 months before today. Once the plan has started, they are the 12 months before the plan’s start, so the growth describes the years before the plan.
The methods
Section titled “The methods”| Method | How it measures growth | What the product needs at the location |
|---|---|---|
| Year-over-year growth | The last 12 months against the 12 months before. | Sales there for two whole years. |
| Average yearly growth (CAGR) | The yearly rate over the last two years, so one unusual year weighs less. When the third year is missing or too unreliable, it measures year-over-year instead, and the method reads Year-over-year growth. | Sales there for three whole years (two for its year-over-year fallback). |
| Trend, damped | The average yearly change over the last two or three years, continued at 80% of its pace. | Sales there for two whole years; three are used when available. |
| Recent level (as Yearly seasonal) | The last 8 weeks against the same weeks in up to three earlier years (their median), as the Yearly seasonal forecast reads them. The result stays between −25% and +25%. | Sales there for a little over a year. |
| Average of methods (the default) | The average of every method above that can measure the product. | At least one method that can measure it. |
Not enough data
Section titled “Not enough data”A method only measures a growth when the product’s sales history at that location is good enough:
- Long enough. The product must have sold there for the whole of every 12-month period the method compares. A product that started selling there more recently has no full year to compare with. Part of a year is never stretched to a full one.
- Reliable enough. The product must have sold enough for the comparison to be precise. With few or very uneven sales, the same history fits very different growth rates. The likely range, shown when you hover the growth, must be narrow enough: for a measured +20%, no wider than about −4% to +50%.
When the method can’t measure a product at a location, Logistified doesn’t guess. The row reads Not enough data, and you set its growth: Growth for products without enough data when you create the plan and when you recalculate targets, or, when you recalculate, a percentage typed for that row. Average of methods needs only one method that can measure.
A product that didn’t sell at a location in the plan’s dates last year gets no growth there: its target starts at 0 whatever the growth. Type a target for it yourself. A product sold under a year with an estimate is the exception: its growth applies to the estimate, and in Recalculate targets it reads Not enough data.
Review
Section titled “Review”A measured growth below −50% or above +50%, or a trend that would bring next year’s sales down to 0, is marked Review: in the Create Sales Plan dialog, in the Recalculate targets dialog and on the Products tab. Logistified applies it as measured and never caps it. Check the product, and change its growth if its history misleads, for example after a one-off large order.
Suspected stock-outs
Section titled “Suspected stock-outs”Days when a product was out of stock look like days without demand, and they can pull its measured growth down. Switch on Leave out suspected stock-outs to leave them out:
- Stock-out detection: Unusual for this item (the default) leaves out a stretch without sales only when it is unusually long for how often the product sells. All long runs leaves out every stretch without sales of at least the minimum length.
- Minimum empty run (days): the shortest stretch without sales that can count as a stock-out. 5 days by default, whole days from 1 to 365.
- A date left out in one year is left out of every year compared, so the years still compare the same days.
- A stretch without sales that runs up to today (or the plan’s start) always stays in: a product that hasn’t sold in the last weeks may simply not be sold any more. So does a stretch at the very start of the history read.
- Recent level (as Yearly seasonal) always reads every day, with the switch on or off.
- Fewer days are left to compare, so a product can have Not enough data with the switch on and a measured growth with it off.
Apart from the start and end rule, these follow the forecast’s stock-out detection; see Excluding stock-out periods.
What it doesn’t do
Section titled “What it doesn’t do”- It doesn’t guess. When a method can’t measure a product, you set the growth.
- It doesn’t speed growth up. Every method measures the growth the product already had. None assumes that growth will accelerate, and Trend, damped continues the trend at a slower pace.
- It doesn’t change the daily pattern. The method only sets the growth percentage. Each target still follows last year’s day-by-day shape at its location, as in How a target is seeded, or the estimated year of a product sold under a year.
- It stays within the growth range. Like a growth you type, a measured growth is between -100% and +900%.
On the Products tab
Section titled “On the Products tab”- Hover a product’s Growth to see which method set it, for example “+12.4% · Average yearly growth (CAGR)”. A growth you typed shows no method.
- On a row that adds up several locations, the hover reads, for example, “+20% · Mixed: the locations’ growth comes from different methods” when they share one growth but not one method, and “Mixed: the locations have different growth” when the growth differs.
- A Not enough data badge marks a growth that is the rate for products without enough data. Hover it, or move to it with the Tab key, to see why. On a row that adds up several locations, the hover says at which of them the rate is used, for example “At Hamburg (1 of 3 locations)”.
- A Review badge marks a growth a method measured below −50% or above +50%; see Review. On a row that adds up several locations it shows when any of them is, and its hover says at how many.
Recalculate targets
Section titled “Recalculate targets”Measure products’ growth again from their own sales history, for example a few months into the plan, or to replace a growth you typed. You can do this while the plan is Draft or Confirmed.
- One product: open the ⋯ menu at the end of its row and choose Recalculate targets…. It covers the product at the location you’re looking at, or at every location the row adds up.
- Every product: click Recalculate targets… above the table, next to Add products. It covers every product at the locations you’re looking at, even while a search narrows the table.
- Selected products: tick them, then click Recalculate targets… in the bar above the table. See Several products at once.
The toolbar button is greyed out while any growth change is still loading; a product’s menu item while that product’s is.
-
In the Recalculate targets for product dialog (or Recalculate targets for 40 products at 2 locations), pick the Growth method. It starts on the method the products already have when they all share one, otherwise on Average of methods. Switch on Leave out suspected stock-outs if you want; see Suspected stock-outs.
-
Wait for the sales history to load. Each row is one location (from the toolbar, one product at one location) with the units sold in the Last 12 months, the Year before and Two years before, the measured Growth, the Method that measured it, and the Target as current → new, or “(unchanged)”. A year the product hasn’t sold through yet at that location reads “Not a full year yet”. When only the year before isn’t full yet, Last 12 months shows the units sold over the plan’s dates last year instead, marked “on the plan’s dates”: that isn’t a 12-month total, and the 12-month totals aren’t compared. A measured growth outside −50% to +50% wears a Review badge. Hover a Growth for the same details as in the Create Sales Plan dialog.
-
Rows with Not enough data get Growth for products without enough data, above the table. It starts at their current growth when they all have the same one, and is empty otherwise. To give one row another growth, type it in that row’s field. A row with both empty stays as it is. Text that isn’t a growth percentage says “Enter a growth % such as 10 or −5.” and Apply waits until you fix it. Next to Apply, a line says how many rows that is and names the first, for example “2 rows have a growth % that can’t be read (Berlin, …).” Click Show to go to that row. A row with “No sales last year” isn’t changed.
-
If some of the products started selling less than a year ago, a Sold under a year section lists them. Leave it on Keep each product’s current source, or change how they are estimated; see Changing the source.
-
Click Apply, then Save changes in the bar at the bottom of the page.
What happens:
- Nothing is saved until you save. The new growth waits in the save bar like a growth you typed, and Discard changes throws it away.
- Targets scale with the new growth, so hand edits keep their proportions. A target at 0 is seeded again from last year’s sales at the new growth, one location after the other, and Save changes waits for it.
- Your edits win. A product you changed while the dialog was open keeps your change, and a message names it: “… changed while the targets were being recalculated, so the new growth wasn’t applied there. Recalculate again if you still want it.”
- A different method in the dialog updates the rows straight away. A different Stock-out detection or Minimum empty run (days) loads the sales history again.
- If loading fails, the dialog says so, for example “Couldn’t read the sales history for targets 501–1,000.”, with Retry. Closing the dialog stops it. If someone deleted the plan meanwhile, it says “This plan no longer exists.”
Several products at once
Section titled “Several products at once”While the plan is Draft or Confirmed, each row has a checkbox in front of the product. Tick the rows you want, or tick the box in the Product header to select every row in view (a search narrows it).
A bar above the table then reads, for example, “3 rows selected”, with Recalculate targets… (4 products at 3 locations). Click it to open the same dialog for those products at those locations: Recalculate targets for 4 products at 3 locations, or the product’s name when you picked one. On All locations, or with several locations picked, a ticked row covers the product at each of those locations.
Use it to recalculate the growth of a group of products, or to change in one go how the products sold under a year among them are estimated.
Clear selection unticks every row. The selection also clears when you change the locations or the search, and after Apply in the dialog you opened from that bar. Opening the dialog from a row’s ⋯ menu or with Recalculate targets… above the table keeps the rows you ticked.
Products sold under a year
Section titled “Products sold under a year”A product that started selling at a location less than a year ago has only a few months of sales there. Copied day by day, its targets would repeat its first weeks and stay empty for the months before it existed. Instead, Logistified estimates a full year for it: its own recent sales set how much it sells, and a source you choose gives the seasonal shape. You set this up when you create the plan (see Setup: products sold under a year) and can change it per product later.
Which products
Section titled “Which products”A product counts as sold under a year at a location when its first sale there is less than a year before the plan starts, or before today if the plan starts later. Each location is judged on its own: a product can be sold under a year at a new store and established at the others. A product with older sales at a location is planned from last year’s days as always.
How the estimate is worked out
Section titled “How the estimate is worked out”- The level. Logistified takes the product’s sales at that location over the last 90 days. Its first 30 days there (its launch month) are left out, so a launch rush doesn’t inflate the level. With Leave out suspected stock-outs switched on when the plan was created, suspected stock-outs are left out too. It needs at least 30 days that count; with fewer, the product is Too new to estimate. If it sold nothing on those days, it isn’t estimated either: its badge reads Not estimated, “No sales here in the last 90 days”.
- The share. It compares the product with the source over those same days. If the source sold 9,000 units and the product 450, the product’s share is 5%.
- The year. The estimate is that share of what the source sold over last year’s dates, with the source’s seasonal shape. If the source sold 48,000 units, the estimate is 2,400 units, busy where the source is busy.
- The growth. The product’s growth applies on top, as for any other product. At +20%, the target is 2,880 units.
Last year still shows what the product actually sold, so you can compare it with the estimate.
Sources
Section titled “Sources”| Source | What gives the shape |
|---|---|
| Established products of the same type at that location | Products with the same product type in Shopify that have sold at that location for more than a year. Products of that type that are new themselves are left out. The default when you create a plan. |
| Products I pick | Up to 10 products you pick, each with a weight (1 by default). Each one is read at the product’s own location and counts by its weight, not by how much it sells. A picked product counts only where it has sold for a full year and sold in the last 90 days. |
| Use actual sales from last year | No estimate: the product uses its actual sales from last year, day by day, and its badge reads Full-year estimate off. Choose it per product in the wizard’s review, or later on the plan with Changing the source. |
When a product can’t be estimated, it uses its actual sales from last year and its badge reads Not estimated, with why, for example that no established Tops have sold at Hamburg for a full year, that the product has no product type, or that it didn’t sell at Hamburg in the last 90 days. Logistified never switches it to another source on its own. Pick similar products for it, or give it a product type in Shopify.
On the Products tab
Section titled “On the Products tab”A product sold under a year shows a badge under its name:
- Estimated: the targets come from the estimate, shaped like established products of the same type or like your picked products. It doesn’t count the picks, because a picked product only counts where it has sold for a full year and sold in the last 90 days.
- Pick products: the source is Products I pick, but none were picked for it yet.
- Not estimated: it couldn’t be estimated.
- Too new to estimate: it hasn’t sold there long enough yet.
- Full-year estimate off: you chose actual sales from last year for it.
Hover a badge, or move to it with the Tab key, for what shaped the estimate or why there is none. A badge that isn’t estimated also says how to change that, for example by ticking the product, clicking Recalculate targets… and choosing Products I pick…. On a row that adds up several locations, a badge shows just the status when every location has it, and counts them when only some do, for example “Estimated · 2 of 3”; its hover lists each location’s result.
Growth works on an estimated product like on any other: at -100% its targets are 0, and a growth above that estimates its year again from its source.
Changing the source
Section titled “Changing the source”Use the Sold under a year section of the Recalculate targets dialog. Open it for one product (⋯ › Recalculate targets…), for every product in view (Recalculate targets… above the table) or for the products you ticked (Recalculate targets… in the selection bar). The section’s title counts them, for example “Sold under a year · 2 products · 4 location targets”. It lists each product at its location with its badge and a short line under it, for example “Shaped like established Tops”, and offers one choice for all of them under Seasonal shape from:
- Keep each product’s current source (the default): only the growth changes, as before.
- Established products of the same type
- Products I pick…: pick up to 10 products with Add similar products and set their weights, as in the Create Sales Plan dialog. One set of picks applies to every product in the section; each uses those products’ sales at its own location. Apply waits until you pick one: “Pick at least one similar product, or choose another source.”
- Use actual sales from last year: no estimate; the badge then reads Full-year estimate off.
A product with a new source shows “re-estimated on apply” in the Target column. With Use actual sales from last year it shows its new target right away: what it sold at its location over the same dates last year, with the growth applied. Click Apply: its targets are worked out again from the new source, at its new growth or the one it has. Then click Save changes. This works on any plan, also one created with the estimate switched off.
- If some of your picks don’t count for a product at a location, a message after Apply names them and says why, for example “Some picked products were left out, so they don’t shape the estimate there: Linen Shirt at Berlin: Oxford Shirt (didn’t sell there in the last 90 days).”
- If the targets can’t be worked out again at a location, a message says so, for example “The source change for Linen Shirt wasn’t applied at Berlin.”, with what to do next. The product keeps its source there; try again later.
When the estimate is worked out again
Section titled “When the estimate is worked out again”The estimate is worked out again whenever a product’s targets are rebuilt: when you change the plan’s dates, when you grow it from -100%, and when you change its source. Until the plan starts, each day that passes adds to the recent sales. So a product that was Too new to estimate gets its estimate once it has sold there long enough, the next time its targets are rebuilt, for example when you choose its source again. Likewise, a product that is no longer sold under a year by then goes back to last year’s days.
- Add products estimates new products sold under a year with the plan’s source, when the plan was created with the estimate on.
- Add location…, Sync locations and Add missing products… give a product at a new location the source it has at its other locations, when that source is the same everywhere. Otherwise it takes the plan’s source, when the plan was created with the estimate on.
Products that need data
Section titled “Products that need data”Some products don’t have the sales history a target can be planned from. The Needs data filter, above the table next to the search, shows them: click Needs data (N) to see only those products, and All products to see every product again. N counts the products at the locations you’re looking at. The search still works on top of the filter.
Each of these products shows a badge under its name with the reason:
| Badge | What it means |
|---|---|
| No sales here yet | It hasn’t sold at this location before the plan’s dates, so its targets start at 0. Type a target, remove it if you don’t sell it there, or have Claude plan it from similar products: it then shows Estimated with From similar products or Like established … under its name. |
| Too new to plan from | It started selling here so recently that its sales can’t be read as a level yet. |
| Sold under a year | It started selling here less than a year ago, so last year holds only part of a year. Plan it from similar products; see Products sold under a year. |
| No sales last year | It sold here before, but nothing in the plan’s dates last year. |
| Mostly out of stock | It was probably out of stock here on most days of the last 12 months, so its sales understate its demand. |
| Growth not measurable | Its sales history is too thin for its growth method to measure a rate; set its growth yourself. See Not enough data. |
Hover the badge, or move to it with the Tab key, to see its first sale, how many days of sales it has and its other reasons. On All locations, or with several locations picked, the badge reads, for example, Needs data · 2 of 3 when only some of the locations need data, and the hover names each one. To plan a product that sold under a year from similar products, tick it, click Recalculate targets… and choose Products I pick….
Changing a target
Section titled “Changing a target”Type a new Target units or Target revenue to set the product’s total over the whole plan. Logistified spreads it over the days the same way as before, so the seasonal shape stays. A new Target revenue first asks whether to raise the units to match: see Typing a target revenue.
On All locations, the total you type is split across the locations in proportion to what each one had. With several locations picked, it is split across those locations only, and the plan’s other locations keep their targets. To change one location only, pick it in the location switcher first.
Targets can’t be negative: a negative number is refused with “A target can’t be negative.” and nothing changes. A typo of a few extra zeros is caught: “That target is too large (max 1,000,000,000).”
A new Target units total also scales a revenue you typed by hand, by the same ratio as the units.
Revenue
Section titled “Revenue”Target revenue is worked out from the units: target units × the product’s price.
- Which price. The price the product had in Shopify when it was added to the plan at that location. Changing the price in Shopify later doesn’t change the plan’s revenue. A location added to the plan later uses the price of that day, so on All locations each location counts at its own price.
- No price. If the product has no price, its revenue field reads No price and it isn’t counted in revenue totals. You can still type a revenue for it here, with Set revenue only.
- Rounding. Each total is rounded to the cent once, so 10 units at €885.45 read €8,854.50 however they are spread over the days.
Typing a target revenue
Section titled “Typing a target revenue”When you type a new Target revenue, nothing changes yet: the field shows its old number and Logistified asks what the new revenue should mean, as in the plan grid. The question reads, for example, “Target revenue: €9,100.00 → €18,200.00 (+100%)”:
- Raise units changes the product’s target units over the whole plan so that it reaches the new revenue. When the new revenue is lower, this answer reads Lower units and plans fewer. The units change by the same percentage as the revenue: +100% revenue means twice the units. On All locations, or with several locations picked, the units are split across the locations in proportion to what each one plans, like a new Target units total. Revenue stays units × price, so no blue dot appears.
- Set revenue only keeps the units and stores the revenue you typed by hand, as described below.
- Cancel (or Escape) changes nothing.
Before you answer, the dialog shows the units and the revenue that results, for example “Units 1,000 → 2,000 at Berlin, Hamburg. Revenue becomes €18,200.00.” A location where units can’t move the revenue (no price there, or a revenue typed by hand over 0 units or as 0) keeps its numbers, and the dialog names it. When no location’s units can move the revenue, for example for a product without a price, only Set revenue only is offered, and the dialog says why. More on the dialog: Typing a revenue.
A revenue typed by hand
Section titled “A revenue typed by hand”Choose Set revenue only to keep a revenue of your own, for example when you plan to sell at a discount. The product then keeps your revenue:
- A blue dot in the revenue field marks a revenue you typed. Hover it: “Revenue typed by hand, not units × price. Reset to go back to units × price.” On All locations it reads “Revenue typed by hand at one or more locations”.
- Your revenue is spread over the days the way the old revenue was, so the shape stays.
- It follows the units from then on: a growth change scales it, so does a new Target units total, and a units change in one period of the plan grid scales that period’s revenue.
To go back to units × price, click the reset icon next to the revenue: Reset to derived (units × price). On All locations this resets the revenue at every location, and with several locations picked, at those locations. The reset waits in the save bar like any other change.
Analytics compares revenue the same way: see Plan analytics.
Adding products later
Section titled “Adding products later”Click Add products above the table and choose a source: Browse products, Scan barcodes, Upload a spreadsheet, From a forecast view or Virtual materials. They work like in the Create Sales Plan dialog.
- Each new product is added at every location of the plan, seeded from last year’s sales at each location.
- Products added later start at 0% growth. Change their Growth if you want them to grow too.
- On a plan created with the estimate for products sold under a year switched on, a new product that started selling at a location less than a year ago is estimated there; see Products sold under a year.
- A product that’s already in the plan, at any location, is marked Already added and skipped.
Logistified confirms what was added, for example “Added 5 products at 3 locations (15 targets), seeded from last year’s sales”. Products that were already in the plan are counted separately, for example “2 already on the plan (skipped)”. A location that is no longer active in Shopify gets no new products, and a message names it. When a plan gets close to the most products it can hold, a line next to Add products says so, for example “This plan holds 520 of 547 products.” If a pick doesn’t fit, nothing is added and the message says how many products the plan can hold.
For the add-once rule, and how to bring back a product you removed at one location, see Adding products to a plan.
Products not in Shopify yet
Section titled “Products not in Shopify yet”A product that launches later and isn’t in Shopify yet, such as a new line on your planning sheet, can be in the plan too. It gets a target at each location you pick, like any other product, and you link it to its product once it exists in Shopify. Until then nothing sells against it, and it never changes your forecast.
Adding one
Section titled “Adding one”- Click Add products above the table and choose New product not in Shopify yet….
- Enter its Name as it reads on your sheet. SKU, Price and Product type are optional.
- Pick its Locations. The locations you’re looking at are picked to start with.
- Add up to 10 similar products and give each a weight. Its targets at each location are worked out from how those products sell there. Without similar products it starts at 0, and you type its months in the plan grid instead.
- Click Add product.
When you upload a spreadsheet through Add products › Upload a spreadsheet, the SKUs that match no product in Shopify are offered too: Add 4 as new products not in Shopify yet… opens the same dialog with one new product per SKU, its SKU filled in. A SKU that a product in Shopify already has can’t be used for a new product: the dialog names that product and offers to add it instead. Claude can add these products for you from your sheet, with their similar products and their months.
What it shows
Section titled “What it shows”- In the Product column, an empty dashed frame where a product’s picture would be, the name and SKU from your sheet, and the badge Not in Shopify yet.
- Once a product in Shopify has the same SKU, the badge reads Found in Shopify. Click it to link the two.
- Growth reads n/a: growth works on last year’s sales, and it has none. Change its targets with Target units, Target revenue, its months in the plan grid, or its similar products (⋯ › Recalculate targets…, where Last year isn’t available).
- Last year reads “–”.
- Not in Shopify yet (N), next to Needs data, shows only these products. When there are none: “Every product in this plan is in Shopify.”
- Without similar products and with nothing planned yet, it also shows No reference yet.
Its ⋯ menu has Link to product…, Edit details… (name, SKU, price, product type and a note), Add to locations…, Recalculate targets…, Copy SKU and Delete from plan…, which removes it at every location. On a plan that is Locked, Completed or Cancelled the menu has only Copy SKU, plus Link to product… on a Locked plan.
Linking it to its product
Section titled “Linking it to its product”Once the product exists in Shopify, click Link to product… (or the Found in Shopify badge):
- This could be lists the product with the same SKU first, already picked, then products with a similar name, SKU or price, with the reason next to each. Search products… finds any other product. Nothing is linked until you click Link product.
- For each location, the dialog shows what happens. Where the product is already planned, choose whether to combine the two targets, keep these targets or keep the product’s own. On a Locked plan, a location where the product is already planned can’t be combined: unlock the plan first.
- Price starts with the price from your sheet, with the Shopify price next to it and Use Shopify’s price. Without a sheet price it starts with Shopify’s. Whatever is in the field is used from then on; you can change it later with Edit details…. On a Locked plan the price can’t change: the field reads “Prices stay as planned on a Locked plan.”, and a product without a price stays without one.
Linking keeps the planned numbers; where you combine two targets, they are added up. From then on the product counts like any other: its sales count against its targets for the whole plan, and its targets show in the forecast’s sales-plan chart. If you have unsaved changes, save or discard them first.
In Analytics
Section titled “In Analytics”The plan’s own figures include products not in Shopify yet: Gap to goal (it says how many), the planned mix and the plan’s side of Plan vs. benchmark. The cards that compare with what sold leave them out until they’re linked, and say so in one line, for example “4 products aren’t in Shopify yet (1,550 units planned, $27,900). They count once linked.” Accuracy by layer doesn’t measure them. See Plan analytics.
In the line export they’re marked in the Not in Shopify Yet column, and the plan’s PDF prints “Not in Shopify yet” under their name.
Removing a product
Section titled “Removing a product”Click the bin icon at the end of the row:
- At one location, the product is removed there straight away. It stays in the plan at its other locations.
- On All locations, Logistified asks first: “Remove product from all locations?” Click Remove from 3 locations to remove it everywhere.
- With several locations picked, Logistified asks “Remove product from the 2 selected locations?”, names those locations and says that the plan’s other locations keep theirs. Click Remove from 2 locations.
Removals are saved immediately; they don’t wait for the save bar. Logistified confirms, for example “Removed 3 location targets”.
Products deleted in Shopify
Section titled “Products deleted in Shopify”When you delete a product in Shopify, the plan keeps the targets it already has, and they still count. It is never planned anywhere new: Add products can’t find it any more (a product deleted while you were picking is reported as not found), and Add location…, Add missing products… and Sync locations skip it. See Adding products to a plan.
Searching the tab
Section titled “Searching the tab”Use Search products or SKUs… above the table to narrow the rows. While you search, the tab shows how many rows match, for example 4 of 120. The × in the box (or Clear search when nothing matches) shows every row again.
See also
Section titled “See also”- The plan grid: edit targets per period.
- Plans at several locations: how edits on All locations are split.
- Adding products to a plan: product sources and the add-once rule.
- Sales Plans: the plan page and saving changes.