# Logistified documentation > Every page of https://docs.logistified.app/ in one file, in the order of the site's sidebar. Each page starts with its address. --- Source: https://docs.logistified.app/ # Logistified Documentation Inventory forecasting, supply orders, and supplier intelligence for Shopify. ## What Logistified does Forecasting Seven forecast models with automatic optimization: predict demand from your sales history and never get caught short. Inventory Planning Tell the forecast what your sales history can’t: a large order a customer has promised, a product you’re about to launch, next season’s sales goals and the yearly events that lift demand. See [Inventory Planning] (/features/inventory-planning/overview/). Purchase Orders Create supplier purchase orders from forecast signals. Export-ready documents, cost tracking, and supplier context built in. Transfer Orders Internal transfers between warehouses and stores. Keep locations balanced without waiting for supplier shipments. Stock Takes Barcode-guided inventory counts with label printing. Close the loop when goods arrive: no spreadsheet cleanup. Return Material Authorizations Manage returns and RMAs in one place. Track credits, process damaged goods, and reconcile supplier claims. Supplier Management Track lead times, MOQs, and supplier reliability per variant. Reorder suggestions take the guesswork out. Notifications Threshold-based alerts and daily email reports. Notify your team when restocking, conflicts, or exceptions arise. Reports Build saved reports from any combination of filters and columns, then email them to your team on a schedule. ## Where to start New to Logistified? Start with [Installation] (/getting-started/installation/). What changed recently? See [What’s new] (/whats-new/) for the latest features and improvements, newest first. Looking for a feature? Use the sidebar; every feature area has its own section. --- Source: https://docs.logistified.app/getting-started/installation/ # Installation Install Logistified from the Shopify App Store and approve the permission scopes. Logistified is a Shopify app. Install it from the Shopify App Store, approve the permissions, and the app opens in your Shopify admin. ## On this page - Steps - Permissions - First-time access - See also ## Steps 1. From the [Shopify App Store] (https://apps.shopify.com/logistified), search “Logistified.” 2. Click Install. 3. Approve the permission scopes (read/write products, inventory, orders, locations). 4. Logistified opens inside your Shopify admin. ## Permissions A brief table of what each permission scope is used for: Permission Used by Read products Forecast, Suppliers, Inventory. Write products Stock takes, PO receiving. Read inventory Forecast, Inventory. Write inventory PO and TO transitions, Stock takes. Read orders Forecast (sales history). Read locations Locations. ## First-time access After install, you’re taken to the Onboarding wizard; see [Onboarding wizard] (/getting-started/onboarding-wizard/). This is the recommended starting point for new shops. Caution Uninstalling deletes your Logistified data straight away: suppliers, purchase, transfer, manufacturing and return orders, stock takes, saved views, settings, notification rules and reports. Your Shopify products, inventory and orders are not touched. If you install again, setup starts from the beginning and your Shopify data is imported again. Export anything you want to keep before you uninstall. ## See also - [Initial setup] (/getting-started/initial-setup/): what happens after install. - [Onboarding wizard] (/getting-started/onboarding-wizard/): the six-step setup. - [Subscription plans] (/getting-started/subscription-plans/): which tier to pick. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/getting-started/initial-setup/ # Initial setup What to expect during the first data sync, plus the minimum config for a useful forecast. After installation, you’ll spend a few minutes telling Logistified how your shop works: your typical lead time, your minimum order, how much history to import. This page tells you what to expect. ## On this page - The Onboarding wizard - The initial data load - How long it takes - Minimum config before your first forecast - See also ## The Onboarding wizard The first thing you see is the [Onboarding wizard] (/reference/glossary/#onboarding): six guided steps. Most new shops walk through it once and are done. See [Onboarding wizard] (/getting-started/onboarding-wizard/). ## The initial data load After the wizard, Logistified pulls your Shopify data: - Products and variants. - Orders (historical, configurable by years). - Locations. - Inventory levels. Then it builds: - Sales history. - Forecast models per variant. - The [Default supplier] (/reference/glossary/#default-supplier) (attached to every variant). Progress is shown on the Onboarding wizard’s last step. You can leave and come back; the data syncs in the background. ## How long it takes Initial sync time depends almost entirely on how many orders you have. Logistified pulls products, locations, and inventory quickly; the bottleneck is order history. Order history Typical sync time ≤ 10,000 orders ~30 minutes. ~100,000 orders 1–2 hours. 500,000+ orders 4–5 hours. You can safely close the tab once the load is running. Logistified emails you when setup is complete in all cases; the address comes from step 4 of the wizard. The progress page also updates live every 10 seconds while it’s open. ## Minimum config before your first forecast Before reorder suggestions become meaningful, do these: 1. Pick a subscription plan (Billing). The default is Essential. 2. Configure your locations (Settings → Locations). 3. Set up at least one real supplier (Suppliers → New). 4. Map your most important variants to that supplier. Tip Don’t worry about getting everything right on day one. Settings can be changed any time. ## See also - [Onboarding wizard] (/getting-started/onboarding-wizard/): the six steps in detail. - [Subscription plans] (/getting-started/subscription-plans/): which tier to pick. - [Forecast → Overview] (/features/forecast/overview/): your first stop after setup. Last updated: 19 May 2026 --- Source: https://docs.logistified.app/getting-started/onboarding-wizard/ # Onboarding wizard The six-step setup wizard that runs once on install. Logistified’s [Onboarding wizard] (/reference/glossary/#onboarding) runs once on installation. It walks you through six steps that set the most-important defaults for your shop. The whole wizard takes about three minutes; the data sync that follows takes longer. ## On this page - The six steps - What you set vs. what you can change later - The progress page - Failures during setup - The welcome and setup-complete emails - Re-running the setup - See also ## The six steps Step What it collects 1. Welcome A brief intro. No data collected. 2. Supplier setup Default lead time (40 days), default MOQ (0), default pack size (1). Used as fallbacks for variants without a specific supplier link. 3. Data synchronization How many years of order history to pull. Default is 2 years; “All available history” is an option but takes much longer. 4. Setup notifications Email address to receive the welcome / setup-complete emails. 5. Summary Review your inputs. Click Confirm to proceed. 6. Start setup Visual animation while the initial data load begins. Not a submit step. ## What you set vs. what you can change later Wizard field Editable later? Where Default lead time Yes (per supplier–variant link) Suppliers → Mapping Default MOQ Yes (per supplier–variant link) Suppliers → Mapping Default pack size Yes (per supplier–variant link) Suppliers → Mapping Years of history No (contact support to re-sync) Email [support@p-h.solutions] (mailto:support@p-h.solutions) Notification email Yes Settings → Notifications Years of history is a one-way choice during onboarding. If you need a longer baseline later, support can trigger a manual re-sync. ## The progress page After the wizard, you land on a progress page showing six setup steps: Step What’s happening Products Pulling products and variants from Shopify. Orders Pulling order history. Locations Pulling location data. Order Histories Aggregating sales history into daily / weekly buckets. Default Supplier Creating the Default supplier and attaching it to every variant. Forecast Models Running automatic model optimization for the first time. Each step shows status, count, and any errors. Refresh the page periodically; it polls roughly every 10 seconds. ## Failures during setup If a step fails: - Logistified retries automatically a few times. - If retries don’t help, the step shows “Failed.” - There is no in-app retry button. Email [support@p-h.solutions] (mailto:support@p-h.solutions) with your store URL and a screenshot of the progress page, the team will manually re-run the sync for you until it completes. Your inputs from the wizard are reused; you don’t have to redo them. ## The welcome and setup-complete emails Once you confirm the wizard, a Welcome email goes to the address you provided in step 4. When all six progress steps complete, a Setup-complete email follows, with a short summary of what was loaded (products, variants, orders, locations). Both go to the same address; you can change it later in Settings → Notifications. ## Re-running the setup The wizard runs once on installation and is not re-shown afterwards. Everything you set in it can be edited from the relevant settings page (see the table above). If you genuinely need a fresh data sync from Shopify (e.g. to load more years of history), email [support@p-h.solutions] (mailto:support@p-h.solutions); re-sync is a support-assisted action, not a self-serve button. ## See also - [Installation] (/getting-started/installation/): what comes before. - [Subscription plans] (/getting-started/subscription-plans/): which tier to pick after onboarding. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/getting-started/subscription-plans/ # Subscription plans at a glance Logistified's three tiers (Essential, Enhanced, Elevate) and what each unlocks. Logistified offers three subscription tiers: [Essential] (/reference/glossary/#essential-plan), [Enhanced] (/reference/glossary/#enhanced-plan), [Elevate] (/reference/glossary/#elevate-plan). Each unlocks specific features. Pick the tier that matches what you need; switch any time. ## On this page - The three tiers at a glance - Picking a plan during onboarding - Upgrading - Downgrading - See also ## The three tiers at a glance Tier What you get Essential Forecast (7 models + Auto-select). Inventory. Suppliers. Purchase Orders (without constraint optimizer). Transfer Orders. Enhanced Everything in Essential, plus: Notifications. Reports. Holt and Seasonal forecast models. Cloud Platform (Beta). Supplier availability and supplier price-break configuration. Inventory Planning: New Product Planning and Promotional Events. Elevate Everything in Enhanced, plus: Return Orders (RMA). Supplier-held stock and Supplier Stock Releases. Supplier credit management. Constraint Studio and the Purchase Order Constraint Optimizer. Xero accounting integration. Inventory Planning: Inventory Commitments and Sales Plans. Auto-select is always the recommended default; it picks the best-fitting model per variant from the models your plan unlocks. Pick a specific model manually only if you have a reason (e.g. you know a SKU is strongly seasonal). For supplier workflows, the common split is: core supplier records and supplier-variant mapping are available on Essential, supplier availability and price breaks are configured on Enhanced, and supplier-held stock, Supplier Stock Releases, and supplier credit management are Elevate features. For the complete feature matrix, see [Reference → Subscription plans] (/reference/subscription-plans/). ## Picking a plan during onboarding The Onboarding wizard doesn’t ask you to pick a plan; Logistified starts on Essential by default. You can upgrade after onboarding from Settings → Billing. ## Upgrading Settings → Billing → “Upgrade” → choose tier → confirm via Shopify’s billing flow → return to Logistified. The new tier’s features unlock immediately. ## Downgrading Same flow, in reverse. When you downgrade: - Gated features paywall immediately. You can browse the corresponding sections but not modify. - Your data is not deleted. Notification rules, reports, RMAs, and constraint rules stay in the database. They become inaccessible until you re-upgrade. - Supplier supply data follows the same pattern: existing supplier availability, price breaks, supplier-held stock, stock-release history, and supplier credits are preserved, but lower plans may make those areas read-only or unavailable. - Already-scheduled background jobs may run one more time before falling silent. - If you re-upgrade, everything is right where you left it. Note If you downgrade and the gated features show errors instead of paywalls, contact support; the gating logic should catch every page. ## See also - [Reference → Subscription plans] (/reference/subscription-plans/): the full feature matrix. - [Settings → Billing] (/features/settings/billing/): the upgrade controls. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/getting-started/glossary-teaser/ # How these docs are organised A short orientation: Diátaxis sections, navigation, and where to look for what. Logistified’s docs are organised by Diátaxis; every page is one of four kinds: a tutorial, a feature reference, a how-to guide, or a spec lookup. This page tells you when to use which. ## On this page - The four sections - How to navigate - Last-updated dates - See also ## The four sections Section When to read Example Getting Started Reading from front to back, your first week. This page; the Onboarding wizard. Features Looking up “what does this thing do?” Forecast view table. Guides Solving a specific task. “Create a purchase order.” Reference Looking up a definition or formula. KPI reference. ## How to navigate - The sidebar: pick a section, navigate by feature. - Search: works across every page; uses your query against page bodies. - Glossary popovers: hover over any underlined term to see a quick definition. - From inside Logistified: the search box in the app’s top navigation searches these same docs (it’s the same search index as the Search here) without leaving the app. Results open on this site in a new tab. The Reference → Glossary page is the alphabetical list. Hover any term inline to see its definition without leaving the page you’re on. ## Last-updated dates Most pages carry a “Last updated” footer; a handful, including the home page, the Glossary index and the developer API section, don’t. Older pages may be slightly out of date; check the footer if something doesn’t match the live app. Tip If you’re new to Logistified, read Forecast → Overview and Purchase Orders → Overview first. They cover the two most-used features and give you the mental model for the rest. ## See also - [Reference → Glossary] (/reference/glossary/): the alphabetical term list. - [Subscription plans] (/getting-started/subscription-plans/): which tier you have decides which features unlock. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/whats-new/ # What's new Notable new features, improvements, and fixes in Logistified, grouped by month. This page lists notable new features and improvements to Logistified, newest first. Follow the links for the full documentation of each feature. ## November 2026 - Sales Plans: plan products that aren’t in Shopify yet. A new product from your planning sheet can be in a sales plan before it exists in Shopify: Add products › New product not in Shopify yet… takes its name, SKU, price, locations and up to 10 similar products whose sales give it its targets, or type its months in the plan grid. An uploaded spreadsheet offers the SKUs that match no product in Shopify the same way. On the Products tab it shows a dashed frame where the picture would be and a Not in Shopify yet badge, and Not in Shopify yet (N) shows only these products. Once the product exists, Link to product… suggests it (the same SKU first), keeps your sheet’s price unless you change it, and from then on its sales count. Until then, the plan’s figures and Gap to goal include it, and the cards that compare with what sold leave it out and say so. See [Products not in Shopify yet] (/features/inventory-planning/sales-plans/products-and-targets/#products-not-in-shopify-yet). - Plan Analytics: find a product by name or SKU. The Analytics tab’s toolbar has a search: type a product name or SKU, pick it, and every card shows that product. A second pick adds to the products on screen or replaces them; you choose each time, or set Add or Replace once. Accuracy by layer now says when the plan was closer in total but further off per product, and no longer lists the months behind plan in a red box: a month in which the locations you’re looking at fell behind keeps its Behind flag in the month strip, and Show months names each location and product group that fell behind under its month. See [Choose products and a location] (/features/inventory-planning/plan-analytics/#choose-products-and-a-location) and [Accuracy by layer] (/features/inventory-planning/plan-analytics/#accuracy-by-layer). - Sales Plans: see which layer of your plan was closest. The Analytics tab has a new card, Accuracy by layer: the baseline (what history said), your benchmark plan (such as your planners’ own sheet) and the plan itself, each against what sold, to date or month by month, with its error and whether it expected too much or too little. A month where the locations you’re looking at fall behind the plan is flagged. See [Accuracy by layer] (/features/inventory-planning/plan-analytics/#accuracy-by-layer). - Sales Plans: compare your plan with your planners’ spreadsheet. The Analytics tab has a new card, Plan vs. benchmark by month: pick another sales plan in Benchmark, such as your planners’ own sheet brought in as a plan by Claude, and see both month by month beside your goal, the difference in total and in the month that differs most, and where they differ by location and by product group. The choice is saved on the plan. See [Plan vs. benchmark] (/features/inventory-planning/plan-analytics/#plan-vs-benchmark). - Sales Plans: a workbook for your review. Actions › Export for review (XLSX) downloads a sales plan as an Excel workbook for the locations you picked: a summary per location with last year, baseline, initiatives, manual change, plan, goal and gap to goal, the same figures month by month, and the initiatives with their owners, probability and timing. Claude can build the same workbook and give you a download link. See [Export a sales plan for review] (/features/inventory-planning/exports-and-documents/#export-a-sales-plan-for-review). - Sales Plans: a full year for products sold under a year. A product that started selling at a location less than a year ago no longer gets a plan of its first few weeks and empty months. Logistified estimates a full year for it: its own sales over the last 90 days set the level (its launch month left out), and the seasonal shape comes from Established products of the same type at that location or from up to 10 Products I pick, each with a weight. It’s on by default when you create a plan, with the switch Estimate a full year for products that started selling within the last year. The Review step lists these products under Sold under a year, each with what its estimate did. Pick similar products… sets the picks for the products you tick, and Use actual sales from last year turns the estimate off for them: their badge then reads Full-year estimate off. A product the source can’t estimate uses its actual sales from last year and says why. On the Products tab, a badge under the product shows its estimate, and you can tick products and click Recalculate targets… to recompute growth or change the source for many products at many locations at once, including Use actual sales from last year to turn the estimate off. See [Products sold under a year] (/features/inventory-planning/sales-plans/products-and-targets/#products-sold-under-a-year). - Sales Plans: change a whole period at once, and turn a revenue goal into units. On the Plan grid, every week, month, quarter or year header of a Draft or Confirmed plan now opens bulk actions for that period: Change by % or Set total to, in Units or Revenue, for the products in view (the locations you picked and your search). A live result shows the change and how it splits across the locations, each location and product keeping its share, and Apply adds it to your unsaved changes. Typing a revenue in the grid, or a Target revenue on the Products tab, now asks first: Raise units plans the units that bring that revenue, split across the locations like a units edit, and names any row units can’t move, such as a product without a price; Set revenue only keeps the units and stores your revenue as before. See [Changing a whole period] (/features/inventory-planning/sales-plans/plan-grid/#changing-a-whole-period) and [Typing a revenue] (/features/inventory-planning/sales-plans/plan-grid/#typing-a-revenue). - New Product Planning: similar products for several locations at once. On All locations (summary), or with several locations picked, a product row now opens its similar products at every location of the product in view. They are grouped into tables by where they are used, values that differ show as a range (for example weight 1–10), and a change to a weight, History from or History start sets one value at all the locations of that table. Volume × can be set for all of them too. Each location’s curve is still rebuilt from its own sales history, and size groups are still changed one location at a time. See [Similar products across locations] (/features/inventory-planning/new-product-planning/launch-curve/#similar-products-across-locations). - Sales Plans: growth from each product’s own sales history. When you create a sales plan, choose From each product’s sales history instead of one percentage for every product, and Logistified measures each product’s growth at each location from what it sold there: the last 12 months against the 12 months before, and for some methods the year before that. Pick a Growth method (Year-over-year growth, Average yearly growth (CAGR), Trend, damped, Recent level (as Yearly seasonal) or Average of methods), and optionally leave out suspected stock-outs. A product without enough history is marked Not enough data and gets the growth you set for it, never a guess, and a big change is marked Review for you to check. On a running plan, Recalculate targets… measures it again for one product or all of them. See [Growth from sales history] (/features/inventory-planning/sales-plans/products-and-targets/#growth-from-sales-history). - Pick several locations on a sales plan or a launch plan. The location switcher on a plan’s page is now a list of checkboxes: All locations, any one location, or several, with Only to pick a single one quickly. The tabs show the picked locations combined, an edit on a combined row is split across those locations only, and the Analytics tab compares them with each other. See [The location switcher] (/features/inventory-planning/locations/#the-location-switcher). Inter-store transfers are new: move stock between your Shopify stores that run Logistified and are connected through Multi-Store. Switch them on per connection on the main store (Settings → Multi-Store, a connected store’s settings, Inter-store transfers). Create a transfer order with a Connected store as its destination and Send it: Logistified checks each SKU at the other store, books the stock out of your location and offers the transfer. The other store finds it under Procurement → Inter-store → Incoming, picks the location to receive into and accepts up to the shipped quantity per line; accepting books the units straight into its available stock. Each store needs the Elevate plan. See [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/overview/). - Ask a connected store for stock. Request stock from a connected store in the transfer orders list’s create menu sends a request with the products, quantities, delivery location, a needed-by date and a note. The other store accepts it into a Draft transfer order that it reviews and sends, or declines it with a reason. See [Stock requests] (/features/supply-orders/transfer-orders/inter-store/stock-requests/). - Nothing gets stuck out of sight. The Inter-store page’s Needs attention tab lists every exchange that’s stuck, with Retry book-out, Retry book-in, Force cancel and Close thread to finish or end it, and Settings → Multi-Store → Messages shows every message between the stores. Recovering an exchange never needs Elevate. See [Troubleshooting inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/). - Read-only through the API and MCP. The REST API and a connected AI assistant can read transfers to and from a connected store, but can’t create, change or answer them. ## October 2026 Inventory Planning is new: open it from the top navigation to tell the forecast what your sales history can’t see. Its hub has four tiles (Inventory Commitments, New Product Planning, Sales Plans and Promotional Events), your most recently changed plans and a search across all of them. Every plan gets its own number (IC-, NP- or SP-), moves through Draft, Confirmed, Locked, Completed and Cancelled, and keeps its documents, exports, PDF and activity log in one place; the plan lists share search, filters and saved presets. See [Inventory Planning] (/features/inventory-planning/overview/) and [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). - Floormode connects to Logistified. If you run your warehouse with Floormode, our companion warehouse app, connect it under Settings → Integrations and choose which warehouses it runs. At those warehouses Floormode receives your purchase orders and supplier stock releases, and the received quantities come back into the order here. Transfer orders from a Floormode warehouse go to Floormode for picking when you Send them, and a manufacturing order with one in-house, manual build produced there is picked and put away in Floormode while you record production here as usual. Planning, buying, forecasting and reports stay in Logistified. See [Connect Floormode and Assemblified] (/guides/connect-floormode-and-assemblified/), [Floormode warehouse execution] (/features/supply-orders/transfer-orders/floormode-execution/) and [Manufacturing in a Floormode warehouse] (/features/supply-orders/manufacturing-orders/floormode-execution/). - Which plan you need. New Product Planning and Promotional Events come with the Enhanced and Elevate plans; Inventory Commitments and Sales Plans come with Elevate. On the Inventory Planning hub, a tile your plan doesn’t include shows the plan it needs (Enhanced or Elevate) and still opens, so you can review what you already have. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements) and [Subscription plans] (/reference/subscription-plans/#inventory-planning). - Inventory Commitments: plan for a large order before it arrives. Write down a wholesale order, a contract, a tender or a promotion: each product’s estimated quantity, how likely it is, and a target date or date range, at one location or unallocated. While the commitment is Confirmed or Locked, the forecast counts its expected units (quantity × probability) as planned outflow, so your reorder suggestions cover it. Create a purchase order, a transfer order or a Shopify draft order straight from it. Comes with the Elevate plan. See [Inventory Commitments] (/features/inventory-planning/commitments/overview/) and [Plan for a large order] (/guides/plan-for-a-large-order/). - New Product Planning: forecast a launch from products you already sell. Pick the similar products the new one should sell like, weight them, set a Volume × and a launch date, and Logistified builds a launch curve from how they sold after their own first sale. Launch at several locations at once, each with its own curve. Plan the sizes of one product together in a size group, whose split always adds up to 100% and can follow the actual size mix once sales come in. With Feed into forecast on, a confirmed launch plan feeds your forecast; Create purchase order orders the launch stock, one PO per location or one combined PO, and the Analytics tab compares the launch with what actually sold. Comes with the Enhanced and Elevate plans. See [New Product Planning] (/features/inventory-planning/new-product-planning/overview/), [Size groups] (/features/inventory-planning/size-groups/) and [Plan a product launch] (/guides/plan-a-product-launch/). - Sales Plans: set sales goals and see whether you’re on track. Logistified starts each product’s target at each location from last year’s sales on the same dates, times the growth you choose; then shape the targets in units or revenue by week, month, quarter or year. A sales plan never changes your forecast. It shows next to it instead, in the Supply view’s sales-plan chart, and its Analytics tab tracks the plan against what actually sells, in units or revenue. Comes with the Elevate plan. See [Sales Plans] (/features/inventory-planning/sales-plans/overview/), [Build a sales plan for next season] (/guides/build-a-sales-plan/) and [Plan analytics] (/features/inventory-planning/plan-analytics/). - Promotional Events: a yearly calendar for the forecast. The Promotional Events tile keeps the holidays and sales that come back every year. Pick one from a list of popular shopping holidays around the world (Black Friday, Singles’ Day, Lunar New Year, Ramadan, Diwali, El Buen Fin and more) or create your own with a date rule such as the 2nd Thursday after Oct 1. Set the uplift you expect, or measure it from past years with Analyze, and switch the event on: every forecast view then expects that much more demand on its dates, year after year. Each product can also get its own uplift, measured from its own sales. The forecast’s Amplifiers popover shows the events above the view’s own amplifiers, lets you leave one out of a view, and warns where an event would count last year’s spike twice. Comes with the Enhanced and Elevate plans. See [Promotional events] (/features/inventory-planning/promotional-events/) and [Growth amplifiers] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast). - Supply view: your forecast as a stock calendar. Choose Supply in the forecast toolbar to see each variant’s stock week by week, month by month or quarter by quarter, up to two years ahead, with what to order and when. Every period cell answers one question at a glance: the stock at the end of the period, plus at most one thing to act on or expect, such as an order chip with the recommended quantity, +40 late or ≈ $420 lost. Red means the variant runs out, amber that it dips below safety stock, and healthy cells have no colour. Choose what the small icon row adds under Show in cells (Off, Icon or Value per item). Hover a cell for a quick preview, or click it for a card with the stock chart, inventory movements, plans and risk, and step through weeks and rows with the arrow keys. From the card, Create PO, Add to draft PO or Create transfer. Click a period header for a card covering every variant on the page, with Create POs for N variants, and drag across headers to set a growth amplifier. On Elevate, a sales-plan chart above the table shows Sold, Forecast and Plan bars per period, and you can leave single plans out of a view. See [Supply view] (/features/forecast/supply-view/). - Planning via MCP / API. REST API 1.5 adds inventory commitments, new product plans, sales plans, promotional events with their holiday catalogue, and the planning options (demand types, reasons and sources): create and change plans, move them through their statuses, and create orders from them, with safe retries through the Idempotency-Key header. A connected AI assistant with write access can work with your plans and events too; see [Operating inventory planning] (/features/agent-access/operating-inventory-planning/). The REST API needs the Elevate plan. See [REST API] (/developers/rest-api/overview/), the [inventory planning walkthrough] (/developers/rest-api/inventory-planning/) and the [API reference] (/developers/rest-api/reference/#inventory-planning). - AI search on the planning lists. The Inventory Commitments, Sales Plans and New Product Planning lists and Promotional Events now take AI search too. Press Tab in the search box and type a request such as “confirmed commitments at the Berlin warehouse due next month” or “holiday events”; the plan date filters also understand periods ahead, such as Next 30 days or Next month. See [Search, filters & saved views] (/features/inventory-planning/search-and-filters/#ai-search) and [Find orders and plans with AI search] (/guides/search-with-ai/). - Attach purchase order documents to the Xero bill. Once a purchase order is linked to a Xero bill, each file on its Documents tab gets an Attach to Xero bill button. One click sends the supplier invoice, quote or receipt to the bill; the button then shows a check mark with when and by whom it was attached, a View in Xero link and Send again, which replaces the earlier copy. Deleting an attached document in Logistified leaves the copy in Xero, and the delete dialog says so. Elevate plan; Xero only for now. See [Attaching a document to the Xero bill] (/features/supply-orders/purchase-orders/documents/#attaching-a-document-to-the-xero-bill). - Link your variants to Xero items and keep their purchase cost current. The new Items page under Settings → Accounting imports your Xero items once, then picks up new and changed items every night, or straight away with Sync items now. Variants whose SKU exactly matches one Xero item code link themselves; link the rest by hand, and an unlink you make stays unlinked. Choose whether your purchase orders update each linked item’s purchase cost in Xero: Copy from Shopify sends the cost your orders set in Shopify, Set new cost sends the order’s own direct or landed cost on completion, on re-sync and from a new Xero item cost choice in Update Unit Cost. Tracked items, sub-assemblies and organisations in a different base currency are left alone, and a Xero organisation can be connected to one shop only. If you connected Xero before, reconnect it once on Settings → Accounting before you turn on the item cost updates (Xero needs your permission to manage organisation settings, where item costs live); bills and item linking keep working without it. Elevate plan. See [Xero items and purchase cost] (/features/accounting/xero-items/). - See the materials a transfer will use before you send it. If your store uses Assemblified, a transfer order can show how many units of each product come from pre-assembled stock at the origin location and how many Assemblified will build from components, in three new Manufacturing (Assemblified) columns. A Materials (Estimated) card adds them up into one pick list of raw materials and sub-assemblies, and the transfer order PDF prints the same list (switch Materials from Assemblified off in a PDF template to leave it out). It’s an estimate for quantity not yet sent. See [Materials from Assemblified] (/features/supply-orders/transfer-orders/assemblified-materials/). - Buy, move and count Assemblified sub-assemblies. Sub-assemblies (SKUs starting with ASM-) can now go on purchase orders, transfer orders, return orders, supplier stock releases, stock takes and stock adjustments. Every stock change is sent to Assemblified, which stays in charge of their stock, and a purchase order sends Assemblified the purchase price instead of updating a cost in Logistified or Shopify. Map a sub-assembly to a supplier before ordering it: purchase orders generated for one supplier name the sub-assemblies no supplier is mapped to. Stock on hand gains a Cost method column. Transfers containing a sub-assembly can’t be sent to Floormode yet. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/). - Dropship orders read the customer’s address from Shopify. A dropship purchase order created from a customer order no longer copies the customer’s address into Logistified: its PDF reads the name and current delivery address from the Shopify order each time you download or send it, and the PO card shows Delivery address from Shopify order #1001 with an Enter address manually instead button. Shopify has now approved this access, so no manual address entry is needed for an order whose delivery details can be read. Such orders are sent as PDF only, no copy is kept, and every download or send appears under Protected data access in the order’s Log. See [Dropship POs] (/features/supply-orders/purchase-orders/dropship/#delivery-details-from-a-shopify-order). - Update Unit Cost says what happened and fixes itself where it can. Set New Price no longer stops with “The purchase order’s costs changed … Reload and try again” when the PO cost has more than two decimals. If the order changes while the dialog is open, the costs refresh in place and keep your method, selection and typed PO costs; an item waiting for an earlier update unblocks by itself. When something does need you, one message says why with the one button that fixes it (Refresh costs, Check again, Keep current cost, Switch to Set New Price, Skip these items). You choose the Shopify cost, the supplier catalogue cost or both on the review step, so when one of them can’t be updated right now you can still update the other. The confirm step lists each change (Shopify cost per item €10.00 → €5.50) and the result reads Costs updated, Some costs were not updated, Nothing was updated or (when Shopify hasn’t confirmed an update yet) Not confirmed yet, with a Cost history link per item. See [Update Unit Cost] (/features/supply-orders/purchase-orders/preferences/#update-unit-cost). - Cost messages in plain words. Completion, Quick Complete and Re-sync costs now say how many costs were updated and what to do about the rest, without internal codes; a cost still being sent to Shopify in the background is a note, not a warning. See [Re-sync costs] (/features/supply-orders/purchase-orders/preferences/#re-sync-costs). - Receiving never overwrites a receipt made elsewhere. Receive, Unreceive, Bulk Edit and the transfer-order Receive Items dialog now refuse (saving nothing) when someone received the same items on another device or tab while you were entering yours, refresh the numbers and keep your entries. A transfer-order receive whose Shopify update failed now says the quantities were saved and offers Retry Shopify update. See [Receiving] (/features/supply-orders/purchase-orders/receiving/) and [Transfer orders → Receiving] (/features/supply-orders/transfer-orders/shipping-receiving/). - Applying credits applies exactly what you see. The Apply credit dialog uses the same cent rule as the order, shows Still due after these credits, and refreshes in place instead of failing when a balance changed meanwhile. RMA credits keep their own currency and the RMA total always matches its credits. See [Applying supplier credits] (/features/supply-orders/purchase-orders/credits/) and [Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/). - Bulk Edit tells you what wasn’t saved. If part of a save is refused, Bulk Edit stays open on exactly those changes and names them. See [Line items → Bulk Edit] (/features/supply-orders/purchase-orders/line-items/#editing-inline-bulk-edit). - See at a glance which products need ordering. In a forecast view grouped by product, the product row’s Reorder Date column now shows the earliest reorder date and how many of its variants are out of stock or overdue (in red), due within the next N days (in amber) or later; N is the view’s Within N Days of Reorder Point filter, or 14 days. Exports of these views can add one summary row per product above its variants, with Row Type and Reorder Status columns; switch Include product summary rows off in the export dialog for a plain variant list. And Open Forecast on the Views page now shows a spinner while the forecast loads. See [What a product row shows] (/features/forecast/product-view/#what-a-product-row-shows) and [Product summary rows] (/features/forecast/export/#product-summary-rows). - Describe what you’re looking for with AI search. On the purchase order, transfer order, return order, manufacturing order, stock take and stock adjustment lists, click into the search box and press Tab (or tap AI search on a phone or tablet), then type a request such as “unpaid draft or sent POs from Acme created last month”. AI search turns it into that list’s filters and shows them in a preview to adjust before you click Apply; the result is ordinary filters you can edit or save as a preset. English only for now; if you don’t see the Tab: try AI search badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/). ## September 2026 - Receiving scans recognize a product’s current barcode. Scan to receive used to match only the barcode recorded on the order when the line was added, so a line created before the product had its barcode (or with an older one) rejected a correctly labelled box. It now also matches the barcode the product carries today, without changing what the order recorded, and Refresh barcodes pulls in the latest barcodes mid-session while keeping everything you’ve already scanned. See [The receive dialog] (/features/supply-orders/purchase-orders/receiving/#the-receive-dialog). - Selected items in the transfer picker no longer lose their available quantity when you search again. Previously, searching for another product in the Shopify picker while adding lines to a transfer order cleared the source and destination quantities for items you’d already picked, so they arrived at Configure Line Items marked Unavailable. Your selections and their quantities now stay in sync across searches, filters and paging, and reset together only when you close the picker or change locations. - Adding items to an order tells you what actually happened. The add-variants picker on purchase and return orders now waits until the lines are saved before confirming, shows one message with the real count (including items skipped because they were already on the order) and stays open with the error if nothing could be added. Quantities you correct in the forecast’s purchase order dialogs also stay corrected, instead of snapping back to the original values and flashing MOQ warnings as you submit. See [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/). - ChatGPT and Claude stay connected. Connections made through Agent access no longer stop working after 30 days (or 90 days for the app registration); they now stay valid until you revoke them. If a connection already dropped, reconnect it; the consent screen now tells you what to do instead of showing a generic expired-request error. See [Managing access & security] (/features/agent-access/managing-and-security/). - Shopify money metafields print and display correctly. A Shopify metafield of type money (a price or a surcharge) used to print as raw code on a label when its attribute was set to Text, and not at all when set to Number. Labels now print it as formatted money in its own currency, product & variant attributes gain a Money type you can sort, filter, import and export, and money values in purchase, transfer and return order line snapshots are shown the same way. See [Money values] (/features/settings/product-and-variant-attributes/#money-values) and [Label printing] (/features/settings/label-printing/#metafield-fields). - More at hand on purchase order line items. The Receipts tab now shows each line’s available stock at the order’s delivery location, Bulk Edit gives every row its own delete (trash) button so you can drop a line without leaving edit mode, and a new optional Received column shows a line’s total received quantity, with every receipt behind it on hover. See [Received column] (/features/supply-orders/purchase-orders/line-items/#received-column) and [The Receipts sub-tab] (/features/supply-orders/purchase-orders/receiving/#the-receipts-sub-tab). - Export any report as a PDF. The Reporting export menu gains Export PDF: an A4 document with the columns, filters, grouping and summary tiles you see on screen, in the same style as your purchase order PDFs. Auto orientation picks portrait or landscape, and the dialog warns before generating when a view is too wide for the page. Scorecards get an Export PDF button too, with their comparison lines. See [Exporting a report as PDF] (/features/reporting/pdf-export/). - A Total row on the purchase order reports. On the Purchase orders and Purchase order items reports, a Total row under the column headers sums every money and quantity column across all rows matching your filters, not just the page on screen. When the rows span more than one currency, the money total shows a dash instead of adding unlike currencies. See [Reporting] (/features/reporting/overview/). - Re-completing a purchase order no longer fails on costs it already synced. With Simple average or Weighted average, a purchase order’s cost is only auto-synced to Shopify or your supplier catalog once per order per target; a line already synced from this order (for example, after reopening and completing it again) is now skipped instead of blocking completion, and the completion and Quick Complete dialogs tell you how many lines that affects before you confirm. See [Auto sync costs on completion] (/features/supply-orders/purchase-orders/preferences/#auto-sync-costs-on-completion). - Your AI assistant can work with Data Modeling, attributes and Constraint Studio. Through Agent access, a connected assistant can now do what you do in the app on these screens (create and edit custom tables and columns, fill in values, manage product & variant attributes, and author purchase order constraint rules) under the same plan limits and guardrails. See [Operating data modeling] (/features/agent-access/operating-data-modeling/) and [Operating purchase-order constraint rules] (/features/agent-access/operating-constraint-studio/). - Suggested column mapping for imports. When a CSV or XLSX has columns Logistified doesn’t recognize, the mapping step now suggests a match for them using AI. Suggestions are highlighted as AI suggestion: review before importing for you to check; exact matches, saved templates and your own choices always come first, and if suggestions aren’t available you map columns by hand as before. Date columns now ask you to pick the date format instead of guessing it. See the [import guide] (/guides/import-data-csv-xlsx/). - Multi-store: partner locations and the real sales channel. Turn on Mirror partner locations in a connected store’s settings to copy its locations into your main store, labelled with the store’s name (for example Warehouse (side)). Mirrored orders then keep their own location, so per-location sales history and forecasts work without mapping every location. Partner locations are for analysis only; they can’t be picked on purchase orders, transfers, stock takes or any other inventory action. Mirrored orders also carry the other store’s real sales channel, money amounts with currency, cancellations and fulfillment orders, and Reporting gains optional Source store and Fulfillment location order columns. See [Mirroring partner locations] (/features/settings/multi-store/#mirroring-partner-locations). - Split a purchase order line into several deliveries. Give one line several dated deliveries (say 4 in August, 4 in September and 4 in October) instead of spreading it across separate purchase orders. Click Split into deliveries on a row to open the delivery schedule editor; the supplier PDF prints the plan, and receiving follows each delivery. See [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/). - Push a purchase order line’s Shopify SKU or barcode straight to Shopify. The line editor’s Shopify SKU and Barcode fields save to the order first; if either changed, a follow-up prompt offers to update the Shopify variant too, field by field, with a retry for anything that doesn’t land the first time. See [Editing the Shopify SKU and barcode] (/features/supply-orders/purchase-orders/line-items/#editing-the-shopify-sku-and-barcode). - Variants you remove from a supplier stay removed. Deleting a variant from a supplier connected to a Shopify vendor or collection used to be undone by the next sync; it came back overnight and reappeared in the forecast. Removed variants are now remembered and skipped by every sync; the Vendor connections dialog lists them with Restore and Restore all, and adding a variant back yourself restores it too. See [Vendor and collection groups] (/features/suppliers/vendor-and-collection-groups/#automatic-nightly-resync). - Purchase tax is set per line, independent of Shopify. A purchase order line used to take its tax status from the product’s Shopify sales-tax setting, so custom items were always tax-free and a product sold tax-exempt was bought tax-exempt too. Each line now has its own Apply purchase-order tax checkbox (on by default for new lines, custom items and imports, using the order’s tax rate) and changing it never touches your Shopify product. Existing lines keep their previous behavior until you change them. See [Per-PO assignment] (/features/settings/tax-rates/#per-po-assignment). - Landed cost no longer spikes on a partial delivery. Shipping, additional costs, payment tax and tariffs are now spread over the units a purchase order is still expected to deliver, not only over the units received so far: 10 ordered, 2 received and 100 shipping gives 10 per unit instead of 50. Once an order is completed or cancelled, the charges settle on the units that actually arrived, and the completion dialog warns when units are still outstanding so an earlier Update unit cost can be repeated. Purchase tax on a short-closed order is now capitalised on the received goods only. See [Additional costs] (/features/supply-orders/purchase-orders/additional-costs/#how-charges-are-spread-across-units). - Confirm a stock-take line without typing. A new check button on each uncounted row records the current quantity as the count in one click and moves on to the next row, and Scan Mode has a Confirm current option so a scan confirms the shelf matches instead of adding one; type a quantity only when there is a discrepancy. See [Stock takes] (/features/inventory/stock-takes/#filtering-and-status-dots). - Tag your supply-order documents. Create your own tags with a name and color under Settings → Tags, then put them on purchase orders, transfer orders, stock takes and stock adjustments; select documents on a list and choose Tags…, or edit them on the document itself. Each of those lists gets a Tags filter, and renaming or recoloring a tag updates it everywhere, saved filters included. - Change a purchase order’s due date in any status. The payment due date can now be edited on received, completed and cancelled orders too; previously the date picker stayed disabled after reopening a fully received order. Separately, Reporting now shows date-only columns such as due dates on the day you set: in time zones west of UTC they appeared one day early. See [Due Date and the payment-due badge] (/features/supply-orders/purchase-orders/payments/#due-date-and-the-payment-due-badge). - Purchase order list shows due dates for any open, unpaid order. The Due: line in the Dates column used to appear only on drafts; it now shows for Sent, Confirmed, In Progress, and every other status too, as long as the order is still open and unpaid, so upcoming payment dates for Net-terms suppliers are visible without opening each order. See [Payments → Due Date and the payment-due badge] (/features/supply-orders/purchase-orders/payments/#due-date-and-the-payment-due-badge). - A failed supplier email no longer leaves the order stuck in Sent. Send to Supplier moves a purchase order to Sent only once the email is actually recorded; if anything fails, the order stays in Draft so you can simply send it again. See [Sending] (/features/supply-orders/purchase-orders/sending/#the-send-button--two-paths). - An honest error screen, with a Copy error details button. If the app hits an unexpected error, the page no longer claims we were notified. It asks you to copy the error details and email them to support, with one button that copies the page, the time, and the error text. - Product-level MOQ. For suppliers whose minimum order applies once per product instead of once per size, set Minimum order quantities apply to Per product (or Both) on the supplier. The forecast then recommends one total per product and splits it across the sizes that sell, and purchase orders check the combined quantity against that one minimum. See [Suppliers → Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product). - Pull soon-due sizes into a product-minimum order. When a product is short of its supplier’s product minimum, the new Order soon-due variants too view setting (Off, or up to N days) also orders sizes that hit their reorder point inside that window, so you place one order instead of two. See [Reorder suggestions] (/features/forecast/reorder-suggestions/#order-soon-due-variants-too). - A default product minimum per supplier. Suppliers whose minimums apply per product now carry a Default Product MOQ, proposed for any product that has no minimum of its own, alongside the existing MOQ, pack size and lead-time defaults. See [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product). - Set product minimums from a spreadsheet. The supplier items download and upload now carry a Product MOQ column next to the per-variant MOQ. Logistified takes the highest value across a product’s rows, ignores blank cells, and warns you before importing when a product’s sizes disagree. See [Importing suppliers] (/features/suppliers/importing/#the-product-moq-column). - Supplier emails with more than one address now work correctly. If a supplier’s Email field held a list of addresses (common after some imports), sending a purchase order or return email, editing the supplier, and the Supplier & Location card now all handle every address individually instead of getting stuck. See [Suppliers → Default email recipients] (/features/suppliers/directory/#default-email-recipients). - Manufacturing planning columns on the Forecast page. If you use Assemblified for builds, five new columns (Buildable Now, Buildable incl. Supplier Stock, Limiting Component, Pre-Assembled, and In Pre-Assembled Stock) show your build capacity right alongside your regular forecast data. See [Forecast view table] (/features/forecast/view-table/#manufacturing-assemblified). - Create a manufacturing order straight from the Forecast page. Select rows and choose Actions → Create Manufacturing Order; the dialog opens with each build’s target already filled in from the suggested reorder quantity, flagging anything below the supplier’s minimum order or off its pack size with a one-click fix. Elevate plan. See [Manufacturing orders] (/features/supply-orders/manufacturing-orders/overview/#creating-a-manufacturing-order). - Multi-Location scheduled report. A new report type emails a Reporting view as a CSV with each location-dependent column split by location; pick up to three locations and choose Total, Per location, or Both per column, with a live preview of the header row. See [Report types] (/features/reports/report-types/#multi-location-report). - Location scope now applies to sales figures too. Reporting’s Locations control used to narrow only stock and incoming columns; units sold, revenue, refunds, and the fixed 3- and 12-month windows now follow it as well, attributed by where each order line was fulfilled from. See [Scoping a report to locations] (/features/reporting/overview/#scoping-a-report-to-locations). - Update purchase order lines from a spreadsheet. Upload one packing list or supplier confirmation and push new delivery dates, quantities, costs, tracking numbers and carriers onto existing orders; each row names its own PO, and you review every change before anything is written. See [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/). - Charges invoiced by someone else no longer inflate what you owe the supplier. Mark a positive additional cost Separately billed: landed cost only and it still counts toward landed cost and the order total, but drops out of Supplier payable, the credit cap and the supplier bill sent to accounting. See [Costs billed separately] (/features/supply-orders/purchase-orders/additional-costs/#costs-billed-separately). - Update Unit Cost shows you the real starting price. The dialog now averages from each item’s originally recorded cost instead of its own last answer, flags when the stock basis is only an approximation, and keeps Set New Price available where a weighted basis conflicts. See [Update Unit Cost] (/features/supply-orders/purchase-orders/preferences/#update-unit-cost). - See who created every document. Purchase orders, transfer orders, returns, manufacturing orders, stock takes, adjustments, releases and print runs now show who created them: a line under the title and a Created by column on the list, with a matching filter on all but releases. Includes documents raised over the API or on Shopify POS. See [Available filters] (/features/supply-orders/purchase-orders/search-and-filters/#available-filters). - Excluding a supplier in Reporting now really excludes it. An Exclude on the Supplier filter drops every variant that supplier supplies, even variants that also have other suppliers; previously those stayed in the report. Excluding the Default supplier now leaves only variants with a real supplier. See the [Reporting overview] (/features/reporting/overview/#what-reporting-shows). - Find a supplier by Shopify SKU. Supplier list search now matches the SKU, product title and variant title of the linked Shopify items, not just the supplier’s own article number, so searching a SKU surfaces every supplier that sells it, not only the Default supplier. See [Supplier directory] (/features/suppliers/directory/#the-supplier-list). - Stock-take header fields on line-item exports. A movements or count-sheet template can now repeat the take’s name, status, currency, creator, dates and notes on every row, so one export pivots in a spreadsheet without a second one. Opt-in, and available to stock adjustments too. See [Stock takes → Exporting] (/features/inventory/stock-takes/#templates). - More export controls for manufacturing order PDFs. The production PDF template now switches the Built quantity, the Remaining quantity, the build details block, the manufacturing notes, and the materials table on or off independently, instead of one combined toggle. See [Settings → Manufacturing Orders] (/features/supply-orders/manufacturing-orders/settings/#export-templates). - Scope report sales figures by sales channel. On the SKU / Variant and Products reports, a new Sales channels control narrows revenue, units sold, and other sales columns to the channels you pick (Online Store, Point of Sale, and so on) without hiding any rows. See the [Reporting overview] (/features/reporting/overview/#what-reporting-shows). - First and Last Received columns on purchase order lines. Two new optional columns show when each line’s first and most recent posted receipt landed, so you can add them to a saved view alongside your other columns. See [Line-item column views] (/features/supply-orders/line-item-views/). - Floormode warehouse execution for transfer orders. Send an eligible transfer order to Floormode for picking and dispatch, track its plan status, and receive each shipment position as it arrives. See [Floormode warehouse execution] (/features/supply-orders/transfer-orders/floormode-execution/). - Discount individual purchase order lines. Select lines and apply a percentage or a fixed amount per unit. The dialog previews each line’s original and net cost before you commit, and the net price flows into subtotals, PDFs, exports and imports. See [Line discounts] (/features/supply-orders/purchase-orders/line-items/#line-discounts). - Reusable address profiles for purchase orders. Save billing and delivery addresses once under Settings → Purchase Orders → Address profiles, set a default pair on each supplier, and pick one when creating or editing an order; each order keeps its own copy, so later profile edits never rewrite it. See [Address profiles] (/features/supply-orders/purchase-orders/settings/#address-profiles). - An Uncounted tab on stock takes. The count sheet now filters to All, Counted and Uncounted, each with a live number, so you can work straight down what’s still outstanding: Enter moves to the next quantity, the row you’re editing stays put, and typing a plain 0 records a real count instead of leaving the line uncounted. See [Stock takes] (/features/inventory/stock-takes/#filtering-and-status-dots). - Send a production order to your manufacturer. A subcontracted build can now be emailed its own production document as a PDF, XLSX or CSV, with attachments, an email history and a one-click revert to Draft, plus exports at item, material and order level, bulk export from the list, finished-goods labels, and an Overdue badge. Elevate plan. See [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/). - Floormode count reports. An inventory count approved in Floormode, our companion warehouse app, now arrives as a read-only stock take here automatically, valued at your Logistified unit costs. See [Stock takes] (/features/inventory/stock-takes/#floormode-count-reports). - Notifications is now a hub. Stock alerts and scheduled reports live together under one Notifications entry, with an Activity panel showing recent alerts and upcoming report runs side by side. The separate “Scheduled reports” sidebar entry is gone; old links forward automatically. See the [Notifications overview] (/features/notifications/overview/). - As many stock notification rules as you need. Instead of one shop-wide setting, create a named rule per team or per purpose, each with its own triggers, variants, recipients, and on/off switch. See [Notification rules] (/features/notifications/rules/). - Per-location stock alerts. A rule can now watch each location separately, so an item can alert for the warehouse where it ran out without going quiet because another one still has stock. See [Notification rules] (/features/notifications/rules/#scope--global-or-per-location). - Alert on a variant’s own minimum, reorder point, target, and maximum. Per-location rules unlock four new triggers that compare each variant against its own constants instead of one shared number, including an overstock warning when stock climbs above the maximum. See [Triggers] (/features/notifications/three-scenarios/). - The forecast view is now optional. Only the days-from-reorder trigger still needs one. Without a view a rule can watch your whole catalog, or just the locations you pick. See [Triggers] (/features/notifications/three-scenarios/#do-i-need-a-forecast-view). - Send a test email from any rule. Pick a real variant (and a location, on per-location rules) and get a [Test]-marked email using its actual stock. Test sends never suppress the real alert that follows. See [Send a test email] (/features/notifications/rules/#send-a-test-email). - Recipients moved to Settings. One shared list at Settings → Recipients, with editing, a Used by column showing which rules and reports each person is on, and a delete confirmation that tells you what will stop being sent. Any rule or report can also create a recipient inline. See [Settings → Recipients] (/features/settings/recipients/). - Send a scheduled report now. Email any report immediately without touching its schedule, optionally narrowing that one send to a few recipients or adding a one-off address. See [Preview, send now, and history] (/features/reports/preview-and-send/). - Report delivery history. Every report has a History tab and a “Last sent” column showing each run’s real delivery state: sent, delivered, bounced, or failed. See [Preview, send now, and history] (/features/reports/preview-and-send/#the-history-tab). - Load a rule’s variants from a spreadsheet. Upload a CSV or XLSX of variants with per-variant thresholds (optionally per location), merging into or replacing the current list, and download the current list back out in the same columns. You can also add variants by scanning a barcode. See [Monitored variants] (/features/notifications/monitored-variants/). - Filter a report by a pasted list of IDs. The Shopify ID, Product ID, and the new purchase-order-line Variant ID filters take a whole list at once; paste comma-, space-, or newline-separated IDs into Include or Exclude, full Shopify IDs included. See [Filtering by ID] (/features/reporting/overview/#filtering-by-id). - Group the Receive and Confirm dialogs by vendor. Both dialogs can now be grouped by vendor, the Confirm dialog gained the search and sortable columns the Receive dialog already had, and Settings → Purchase Orders → Preferences remembers the grouping and sort you want every time they open. See [Dialog group and sort defaults] (/features/supply-orders/purchase-orders/preferences/#dialog-group-and-sort-defaults). - Export suppliers from the list. Select suppliers and choose Actions → Export suppliers for a CSV or XLSX at either level (one row per supplier, or one row per supplier item with live product data) using column templates you manage in Settings. See [Exporting suppliers] (/features/suppliers/exports/#exporting-from-the-supplier-list). - Connect Floormode from Settings → Integrations. Turn the warehouse app on, hand it the Shopify locations it actually runs, and let it own receiving there; purchase and transfer orders then show a “Receiving happens in Floormode” panel, with a connection-health readout and a readiness check for custom items. See [Integrations → Floormode] (/features/settings/integrations/#floormode). - Manufacturing orders. Plan a production run you build in-house or hand to a subcontractor: set a target per item, see what materials are needed, turn shortfalls into purchase orders, transfers or stock releases in one step, record production, and send finished goods into a location. Elevate plan. See [Manufacturing orders] (/features/supply-orders/manufacturing-orders/overview/). - Count stock parked at a supplier as supply. New Stock at Supplier columns show what you already own but haven’t received, and an opt-in view setting lets those units count in reorder math, either as available now, or as arriving after the supplier’s release lead time. See [Supplier-held stock] (/features/forecast/supplier-held-stock/). - Stock at Supplier report. A new Suppliers section in Reporting, starting with one row per supplier and item: quantity and value held at each supplier, releases in transit, and the supplier’s credit balance, grouped by supplier by default. See the [Reporting overview] (/features/reporting/overview/#what-reporting-shows). - Backfill metafields on an existing order. Actions → Update Metafields on a purchase, transfer or return order fills in snapshot metafield values for lines added before you selected the field, and refreshes the rest from Shopify, without ever clearing a value you already have. See [Snapshot metafields] (/features/supply-orders/purchase-orders/line-items/#snapshot-metafields-shopify--po). - Ordering defaults per supplier. Set a Default MOQ, Default Pack Size and Default Lead Time on the supplier itself, and every new supplier item (added by hand, matched from a vendor, imported, or added from an order) starts from those numbers. Changing one asks whether to apply it to the items you already have. See [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#defaults-for-new-links). - Ship a transfer order to a supplier. Send stock from one of your locations to a manufacturer, finisher or 3PL, who receives and holds it as your own stock until a supplier stock release brings it back into a warehouse. Elevate plan. See [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/). ## August 2026 - Deliver a purchase order to another supplier. Buy from one supplier and have a second one take delivery and hold the goods as your stock, until a supplier stock release brings them into a warehouse. Elevate plan. See [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/). - Find your sporadic sellers. Two new column families (Sales Days/Month (3, 6, or 12 months of days with at least one sale) and Demand Pattern (Smooth, Intermittent, Lumpy, Erratic)) let you filter the forecast to items that sell in bursts. See the [forecast view table] (/features/forecast/view-table/#demand-pattern). - Shop-wide saved filter presets on every list. Purchase orders, transfer orders, returns, stock takes, and stock adjustments now share one search-and-filter bar where you save a filter set (search term included) as a named preset the whole shop sees, and star one as the default. See [Search, filters & saved views] (/features/supply-orders/purchase-orders/search-and-filters/). - Open any page in a new tab without logging in again. Right-click, middle-click, or cmd-click a link inside Logistified and the new tab now opens the page inside your Shopify admin instead of a re-login prompt. - Dropship a purchase order to your customer. Pick a customer delivery address instead of one of your locations and the supplier ships direct; the order carries a Dropship badge and filter, receiving becomes Mark Delivered, and marking delivered leaves Shopify stock unchanged. Optional Compensate Inventory offsets stock deducted by Shopify fulfillment. See [Dropship POs] (/features/supply-orders/purchase-orders/dropship/). - Replay last year’s demand as your forecast. The new History replay model repeats your selected history window instead of fitting a curve, ideal when next month should simply look like the same month last year. Available on every plan; pick it manually, since Auto never selects it. See [Forecast models] (/features/forecast/forecast-models/). - Print your supplier’s standing notes on every PO PDF. A new Include supplier notes toggle on PDF export templates prints the notes from the supplier’s own profile onto the order slip, separately from the order’s own supplier instructions. See [Export templates] (/features/supply-orders/purchase-orders/exports/#custom-column-sets-and-export-templates). - Keep auto-generated views out of the Create-PO picker. Turn on “Hide auto-generated views in the purchase order dialog” under Settings → Forecast preferences and the Use Existing View picker offers only views you saved yourself. See [Forecast preferences] (/features/forecast/forecast-preferences/#hide-auto-generated-views). - Filter the forecast by purchase order status. A new “On PO with Status” column and filter shows every status a variant is currently on order under, not just Draft. Exclude “Any open PO” to find items you haven’t already reordered. See the [column reference] (/reference/forecast-column-reference/). - Apply a new unit cost to a product’s other sizes. Change one line’s Cost in Bulk Edit and Logistified offers to spread it to the order’s other lines of the same product, showing each one’s current and new cost before you stage the change. See [Applying a cost change to other variants] (/features/supply-orders/purchase-orders/line-items/#applying-a-cost-change-to-other-variants). - Receive several purchase orders at once. Select orders on the list and choose Actions → Auto-receive: play them all the way to Received (or Completed), or build one partial receipt across them by scanning, typing or uploading a count sheet, with nothing ever over-received. See [Bulk auto-receive] (/features/supply-orders/purchase-orders/receiving/#bulk-auto-receive-from-the-list). - See stock per location without leaving the Forecast. Hovering the Inventory quantity cell now lists available quantity at every location, with a total, shown for all locations even when the view is filtered to one. See the [forecast view table] (/features/forecast/view-table/#inventory-quantity). - Label-checking sessions can expire on a date you pick. Alongside the fixed 1-hour to 7-day windows, choose Custom date and the session runs through the end of that day in your shop’s timezone. Unlike “No expiry (company device)”, you can set it when editing an existing session too. See [Creating a session] (/features/cloud-platform/creating-a-session/#step-by-step). - Print price tags before the delivery arrives. A Set To Ordered button in the label dialog fills the selected rows with the ordered quantity instead of leaving them at zero (it reads Set To Planned on a transfer order), and a new Label print order preference prints alphabetically by product instead of in order sequence. See [Label printing → Label print order] (/features/settings/label-printing/#label-print-order). - Jump to any page of the forecast. The page indicator is now a picker (choose or type a page number to go straight there) and each view reopens on the page you left it on. See [Paging] (/features/forecast/view-table/#paging). - Export several forecast views into one file. The forecast export dialog can now combine saved views: either one worksheet (or titled section) per view, or one combined table with a View column where each SKU repeats once per view it appears in. See [Exporting the forecast] (/features/forecast/export/). - Stock adjustments. Add or remove stock with a reason and an operator name, without counting a whole location. Every adjustment is saved as a document and can be reverted with one click. See [Stock adjustments] (/features/inventory/stock-adjustments/). - Quick Complete now refuses an unconfirmed order. Instead of closing a purchase order with an empty receipt, it asks you to record the supplier’s confirmations first. See [Receiving] (/features/supply-orders/purchase-orders/receiving/). - Reporting: a Delivery date column and a Yesterday date range. Both purchase-order reports now show one Delivery date by default (the requested date when set, the expected date otherwise) with the raw columns still available, and the date-range picker adds Yesterday alongside the 7/30/90/365-day presets and a custom range. See the [Reporting overview] (/features/reporting/overview/#what-reporting-shows). - Schedule status on the Scheduled reports list. Each row now shows whether its schedule is armed and when the next run is due, and saving a report still succeeds if the schedule can’t be set, with a warning so you can retry. See [Preview, send now, and history] (/features/reports/preview-and-send/#schedule-state-on-the-scheduled-reports-list). - Configurable line-item columns on supply orders. Purchase orders, transfer orders, return orders, and supplier stock releases now have saveable column views, including retail price, costs, margin, markup, and gross profit. Margin columns state which cost basis they use. See [Line-item column views] (/features/supply-orders/line-item-views/). - Edit retail and compare-at prices inline. Change a variant’s price directly from a purchase order line or a report row, and Logistified writes it back to Shopify. See [Editing retail prices] (/features/supply-orders/editing-prices/). - Margins in Reporting. Reports now offer margin, markup, and gross profit columns, each labelled with the cost basis behind the number, plus a new Purchase order items report. See [Margins and cost basis] (/features/reporting/margins-and-cost-basis/). - Tax-exclusive margins. If your retail prices include VAT, GST, or sales tax, a new setting under Settings → Tax rates calculates margin, markup, and gross profit from tax-exclusive prices. Affected columns are labelled “excl. tax”. See [Tax rates] (/features/settings/tax-rates/). - Taxes can count toward paid status. An optional purchase order setting includes recorded payment taxes and fees when deciding whether an order is fully paid. See [Payments] (/features/supply-orders/purchase-orders/payments/). - Landed-cost allocation by value. Shipping and other included charges can now spread proportionally to each line’s goods value instead of evenly per received unit. See [Purchase order settings] (/features/supply-orders/purchase-orders/settings/). - Inventory value at cost on the dashboard. The “Avg. Inventory Value” KPI now values stock at unit cost by default. A new Settings → Dashboard option switches it back to retail. See the [KPI reference] (/reference/kpi-reference/). - More reliable report schedules. Monthly schedules now fire on the day you choose with a new day-of-month picker, bi-weekly schedules fire every two weeks, and a missed run re-arms itself. See [Cadence and time] (/features/reports/cadence-and-time/). - Full timezone list for scheduled reports. The schedule timezone picker now offers every named timezone instead of a short list. - Quarterly report schedules retired. Quarterly never actually sent due to a scheduling bug, so the option was removed. If a report of yours was set to Quarterly, open it and pick another frequency. See [Cadence and time] (/features/reports/cadence-and-time/). - Stock takes show counted items with no difference. A counted line whose quantity matched gets its own indicator dot, and the filter is now labelled “Counted”. See [Stock takes] (/features/inventory/stock-takes/). - Vendor connections refresh nightly. Connected vendors re-sync their product variants every night, so new products are added and removed ones cleaned up without pressing Resync. See [Vendor and collection groups] (/features/suppliers/vendor-and-collection-groups/). - REST API purchase-order writes. Create, edit, and manage purchase orders programmatically. See the [REST API overview] (/developers/rest-api/overview/). - Label Checker updates. Scan any barcode to look up an item, sign in with just a PIN, and set a shop timezone so scan statistics follow your local day. See [Item look-up] (/features/cloud-platform/item-lookup/). - Turn off Shopify incoming for transfer orders. A new Sync incoming to Shopify switch under Settings → Transfer Orders → Preferences stops transfers from raising Shopify incoming at all; receiving then adds the units straight to destination available. See [Transfer order settings] (/features/supply-orders/transfer-orders/settings/#inventory-sync-preferences-tab). - Refresh supplier connections in bulk. Select suppliers on the list and choose Actions → Update connections to re-run every selected supplier’s vendor and collection links at once, with per-supplier progress and a summary, optionally making the supplier primary on each variant it adds. See [Supplier directory] (/features/suppliers/directory/#update-connections). - Adding an order’s items to its supplier keeps the terms you already set. The “N not from supplier” task now opens with each item’s supplier SKU, cost, MOQ and pack size filled in from the order line, and a Show more toggle adds supplier barcode, product URL and variant details. See [Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/#adding-an-orders-items-to-its-supplier). - See what your plan gates before you click. Settings navigation now badges the sections that need an upgrade, a gated page shows an in-app upgrade notice instead of bouncing you to Billing, and Billing displays the recurring price you’re actually paying. See [Billing] (/features/settings/billing/#what-this-shows). - Say “case” instead of “pack” on purchase order PDFs. PDF templates now choose between Pack / packs and Case / cases for the quantity breakdown, or switch the breakdown off entirely with Disable pack size breakdown. Existing templates keep saying “pack”. See [Export templates] (/features/supply-orders/purchase-orders/exports/#custom-column-sets-and-export-templates). - Labels print the current Shopify price. Every print re-checks Shopify for price, barcode, cost and compare-at price and uses those, so a price you changed five minutes ago is on the label. Negotiated purchase-order costs are left alone, and a Shopify outage falls back to stored values with a warning. See [Label printing → Live price, cost & barcode data] (/features/settings/label-printing/#live-price-cost--barcode-data). - Count completed purchase orders as paid. An optional preference marks every Completed order paid automatically (reflected in the paid/unpaid filter, the list and exports) while the default leaves it unpaid until you record a payment. See [Auto paid when completed] (/features/supply-orders/purchase-orders/preferences/#auto-paid-when-completed). - Unit costs keep sub-cent precision. Cost fields on order lines, supplier items, price breaks, the purchase order scanner, transfer and return order lines and label test prints hold more than two decimal places through edits, imports and cost sync; tables and logs show up to four decimals, and a negative unit cost is rejected before it can be saved. See [Cost calculation] (/features/supply-orders/purchase-orders/line-items/#cost-calculation). - Cost updates convert foreign-currency orders by default. When an order’s currency differs from your shop currency, Update Unit Cost now opens with Convert currencies on and the exchange rate pre-filled, with a manual fallback if the live rate can’t be fetched. See [Update Unit Cost] (/features/supply-orders/purchase-orders/preferences/#update-unit-cost). - Faster receiving. The receive dialog gained search and sortable columns, a scanned item jumps highlighted to the top, and with the scan box empty Enter adds one more unit of the last item while Backspace removes one. See [Receiving] (/features/supply-orders/purchase-orders/receiving/). - Deep search on purchase orders. Find an order by tracking number, invoice, document name, supplier instruction or product identifier, and optionally by the manual comments in each order’s activity log, with the current list filters scoping the search. See [Deep search] (/features/supply-orders/purchase-orders/search-and-filters/#deep-search). - Smarter Stocky purchase-order import. Rows without a SKU are matched by their Shopify ID, and unmatched rows can be imported as custom line items instead of being dropped. See [Creating a PO] (/features/supply-orders/purchase-orders/creating/#importing-from-stocky). - Create from Min/Max across all locations. An optional global scope counts stock you already own or have inbound at any location, for purchase orders and transfer orders alike. - Auto temporarily stops picking Holt and Seasonal. Automatic model selection no longer chooses the Holt or Seasonal models for steady sellers while we retune them. Variants already using one keep it until their next re-check, and you can still pick either by hand at the view level. See [Automatic model optimization] (/features/forecast/automatic-model-optimization/#what-auto-doesnt-do). - Set the expected shipping date while creating a purchase order. Every Create PO path (blank, from forecast, from sales history, from customer orders, from Min/Max) now carries an optional Expected Shipping Date, which also drives the payment due date from your supplier’s terms. See [Expected Shipping Date] (/features/supply-orders/purchase-orders/creating/#expected-shipping-date). - Filter the Orders tab by tag, and save your filters. Supply Orders → Orders now filters Shopify order tags with an Include / Exclude switch, and Save Filters keeps your whole toolbar (search, statuses, tags and dates) as the default next time you open the tab. See [The Orders tab] (/features/supply-orders/orders-tab/). - Attach paperwork to a closed purchase order. Completed and Cancelled orders keep their Documents card and Supplier Instructions editable (and instructions can now be read and edited straight from the Order Information card) so a final invoice no longer means reopening the order. See [What you can edit at each status] (/features/supply-orders/purchase-orders/lifecycle/#what-you-can-edit-at-each-status). ## July 2026 - Reporting launched. Build interactive reports on sales, stock on hand, ABC analysis, and more, with grouping, drill-down, saved views, scorecards, and CSV/XLSX export. See the [Reporting overview] (/features/reporting/overview/). - Shopify POS workflows. Staff without admin access can receive transfer orders and purchase orders and run stock takes from the Logistified tile in Shopify POS, counting with steppers, a barcode scanner or the camera. Stock-take counts are blind, and applying them to Shopify stays in the admin. See [Shopify POS] (/features/pos/overview/). - Xero accounting integration. Connect Xero and push purchase order bills across automatically, including supplier and tax rate mapping. See the [Accounting overview] (/features/accounting/overview/). - Printing Studio. A new label printing workspace: open a print run, scan or pick items, set copies per item, and generate the file, or use Quick create for a one-off batch. Generated files stay on the run for later download. See [Printing Studio] (/features/inventory/printing-studio/). - Redesigned app. Every list now shares the same toolbar with search, filters, and bulk selection, and the dashboard and setup guide were reworked. - Additional costs and discounts. A purchase order can carry several additional costs and discounts at once, each a fixed amount or a percentage with its own currency and tax rate. See [Additional costs] (/features/supply-orders/purchase-orders/additional-costs/). - Several shipments per purchase order. Split deliveries no longer need separate orders. Each shipment carries its own carrier, tracking, status, and dates, and can optionally list which line items travel in it. See [Shipments] (/features/supply-orders/purchase-orders/shipments/). - Better forecasts for irregular sellers. Items that sell in bursts now use models built for intermittent demand, and new controls cap safety stock and handle outliers. See [Forecast models] (/features/forecast/forecast-models/). - Bundles.app integration. Bundle sales feed component demand into the forecast, and purchase orders can be split into a bundle’s components. See [Integrations] (/features/settings/integrations/). - Custom document numbering. Set your own prefix and number format for purchase orders, transfer orders, and return orders. - Email any report on a schedule. A new email-report type sends a saved Reporting view as a CSV attachment on the cadence you choose. See [Report types] (/features/reports/report-types/). - Default email recipients per supplier. Save To and CC recipients on each supplier for pre-filled purchase-order emails. Transfer-order emails accept multiple recipients too. - Stocky imports keep receiving status. Purchase orders imported from Stocky land as Received or Partially Received to match their delivery state, with received quantities pre-filled. - Merging purchase orders now asks how to resolve differences. When two orders carry the same item at a different cost, delivery date or quantity, you choose which order’s values the combined line takes, or keep the lines separate. See [Merging POs] (/features/supply-orders/purchase-orders/lifecycle/#merging-pos). - Metafields on Printing Studio labels. A designer template bound to a product or variant metafield now fills with the live Shopify value when you print from Printing Studio, instead of needing a fixed value or a remap. See [Printing Studio → Field mapping] (/features/inventory/printing-studio/#field-mapping-for-designer-templates). - Barcodes that scan, on every page. Barcodes now use the full width of their field with proper quiet zones and an optional caption, older templates can be widened with one click, and a field hanging over the label edge is trimmed and flagged in the designer instead of silently disappearing from all but the last page. See [Label printing → Barcode fields] (/features/settings/label-printing/#barcode-fields). - Two-column thermal label rolls. A new Thermal 2-up page layout, a Retail thermal 1.25” x 1” size preset, and a ready-made matching designer template place both columns on the real 1.30” pitch, so the right-hand barcode lines up with the stock. See [Label printing → PDF page layout] (/features/settings/label-printing/#pdf-page-layout). - Print labels on office sheets. A new Multi-label sheet / roll layout lays labels out on A4, US Letter or a custom page, with margins, gaps, calibration offsets, and a start slot so you can finish a part-used sheet. Up to 20,000 labels per file. See [Label printing → PDF page layout] (/features/settings/label-printing/#pdf-page-layout). - Remove many transfer-order lines at once. On a Draft transfer order, tick the lines you don’t want (or the select-all box, which covers just the rows your filter shows) and delete them in one confirmed step. See [TO lifecycle] (/features/supply-orders/transfer-orders/lifecycle/#removing-several-lines-at-once). ## June 2026 - Multi-store order sync. Mirror a connected store’s orders into your main store so every store’s sales feed one shared forecast, with historical backfill and a sync log. See [Multi-store] (/features/settings/multi-store/). - Connect AI assistants. Give Claude, ChatGPT, or any compatible AI client secure access to read your data and operate purchase orders, transfer orders, stock takes, and returns on your behalf. See the [LLM / Agent Access overview] (/features/agent-access/overview/). - REST API in beta. Read purchase orders, transfer orders, and stock takes over HTTP with an API key. See the [REST API overview] (/developers/rest-api/overview/). - Order exclusion rules. Choose which orders count toward your forecast, filtering out test, provisional, or unpaid orders. Nothing is deleted, the orders simply stop feeding demand. See [Order exclusion] (/features/settings/order-exclusion/). - New ways to create transfer orders. Create a transfer order from your forecast, from sales over a period, or from selected sales orders. See [Creating transfer orders] (/features/supply-orders/transfer-orders/creating/). - Sync Shopify costs to supplier costs. Update supplier variant costs from Shopify’s current unit cost in one bulk action, with currency conversion where needed. - Bulk export for transfer orders and stock takes. Export a selection straight from the list, one row per line item or per order, with configurable templates. - Reopen cancelled purchase orders. Cancelling is no longer final. A cancelled order can be reopened to the status it was cancelled from, with line items and incoming quantities restored. - Match vendors to suppliers on import. The Stocky supplier import can fill suppliers with variants by matching your Shopify vendors by name, without a second file. See [Importing suppliers] (/features/suppliers/importing/). - More accurate reorder quantities. Target days of supply no longer over-orders when you already hold stock, and incoming quantities come from the same tracking the orders themselves use. - Label Checker session upgrades. Sessions can be created without an expiry, built from a saved view or started empty, and hold far larger item lists. ## May 2026 - Supplier stock releases. A new supply order type for stock a supplier holds on your behalf: create a release, send it, and receive the units into your own locations. See the [Supplier stock releases overview] (/features/supply-orders/supplier-stock-releases/overview/). - Cloud Platform beta with Label Checker. Turn any device with a camera into a label-checking station: create a session, share the link, and scan labels against your catalog. See the [Cloud Platform overview] (/features/cloud-platform/overview/). - Merge purchase orders. Combine several orders for the same supplier and location into one, with matching items added together instead of duplicated. - Purchase orders from Shopify orders. Pick Shopify orders and build purchase orders from what customers bought, with quantities spread across suppliers for you. See [Creating purchase orders] (/features/supply-orders/purchase-orders/creating/). - Rebuilt file imports. Every CSV and XLSX upload now uses one flow with column mapping, saved import templates, and downloadable sample files. See the [import guide] (/guides/import-data-csv-xlsx/). - Label printing on purchase orders. Print product labels straight from an order, in simple mode or with your own designed template. See [Label printing] (/features/settings/label-printing/). - Automatic cost updates on completion. When a purchase order completes, Logistified can push the new unit costs to Shopify and to your supplier prices. See [Purchase order settings] (/features/supply-orders/purchase-orders/settings/). - Sales figures on order lines. Purchase order line items show recent sales and stock for each item over the last 30, 60, and 90 days, so you can judge quantities without leaving the order. - Fix incoming quantity drift. A new tool compares the incoming quantities Shopify shows against your open purchase and transfer orders and corrects the difference. See [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). - Barcode scanning for stock takes. Scan items into a stock take with a scanner or your camera. See [Stock takes] (/features/inventory/stock-takes/). - Documentation site. This documentation site went live, covering every feature with guides and a glossary. ## April 2026 - Return orders. Send stock back to a supplier with a return order that has its own numbering, status flow, and activity log, started from scratch or from a Shopify order. See the [Return orders overview] (/features/supply-orders/return-orders/overview/). - Supplier credits. A return can issue a credit against the supplier, Logistified keeps a running balance, and credits can be applied to purchase orders. See [Supplier credits] (/features/suppliers/credits/). - Orders view in supply orders. A new view lists your Shopify orders and shows which purchase orders and returns are linked to each one, and lets you start either directly. - Custom items on purchase orders. Order items that do not exist in your Shopify catalog, and convert them into real products later without losing the order history. See [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/). - Split purchase orders by quantity. Orders can now be split by quantity, not only by supplier or component. - Nightly data checks. Products, orders, and inventory levels are compared against Shopify every night and corrected when they drift apart. - Label preview and label export. A test print tab previews the exact label layout, and label data can be exported as CSV or XLSX instead of printing. See [Label printing] (/features/settings/label-printing/). ## March 2026 - Stock takes. Count inventory against a saved view or a hand-picked list, upload counts from a spreadsheet, print count sheets, and push corrections back to Shopify. See [Stock takes] (/features/inventory/stock-takes/). - Payments and notes on purchase orders. Record payments in any currency, see what is outstanding, and keep a conversation thread on each order. See [Payments] (/features/supply-orders/purchase-orders/payments/). - Purchase order constraints and optimizer. Set ordering rules such as container fill, budget ceilings, and minimum order values, and let the optimizer adjust quantities to fit them. See the [Optimizer] (/features/supply-orders/purchase-orders/optimizer/). - Landed cost and exchange rates. Spread shipping, duties, and other charges across received units so each line shows its true landed cost, and fix the exchange rate per supplier. See [Additional costs] (/features/supply-orders/purchase-orders/additional-costs/). - Create orders from a spreadsheet. Build a purchase order or transfer order by uploading a CSV or XLSX file of SKUs and quantities. See the [import guide] (/guides/import-data-csv-xlsx/). - Stocky imports. Import purchase orders, suppliers, and min/max values from Stocky CSV exports. See [Importing suppliers] (/features/suppliers/importing/). - Undo receiving and reopen orders. Reverse a receipt and the inventory goes back the way it came, and completed orders can be reopened. - Reorder numbers explained. New forecast columns for reorder points and sales performance, and hovering a reorder number shows how it was calculated. See the [column reference] (/reference/forecast-column-reference/). - Custom product data fields. Define your own product and variant fields and use them across purchase orders and product settings. See [Data modeling] (/features/settings/data-modeling/). ## February 2026 - Transfer orders. Move stock between locations with a full flow from draft through sent, received, and completed, updating inventory at both ends. See the [Transfer orders overview] (/features/supply-orders/transfer-orders/overview/). - Min and max restocking. Set a reorder point and target level per variant, upload them in bulk, and turn everything below its reorder point into a purchase order in one step. - Create a purchase order from a forecast view. Turn a view straight into an order, setting supplier, location, and terms as you go. The order stays linked to its view. See [Create from forecast] (/features/forecast/create-po-from-forecast/). - Vendors as suppliers. Import Shopify vendors as suppliers in one step, or connect vendors to an existing supplier so their products become supplier items automatically. See [Vendor and collection groups] (/features/suppliers/vendor-and-collection-groups/). - Supply timeline in the forecast. A new display mode shows projected stock over weeks, months, or quarters, colour coded so shortages stand out. See the [view table] (/features/forecast/view-table/). - Growth amplifiers. Raise or lower forecast demand for a chosen period so promotions and seasonal peaks flow into your reorder numbers. See [Growth amplifiers] (/features/forecast/growth-amplifiers/). - Write purchase order data to Shopify. Fill product tags and metafields from order line items, such as ordered quantity or expected delivery date. See [Side effects] (/features/supply-orders/purchase-orders/side-effects/). - Incoming stock shown in Shopify. Purchase order quantities can be pushed to Shopify as incoming inventory and stay in step through every status. See [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). - Add line items by scan or file. Add items to a purchase order by scanning barcodes or uploading a file of SKUs and quantities. - Tax rates. Keep your own list of sales, purchase, and shipping tax rates and apply them to suppliers and purchase orders. See [Tax rates] (/features/settings/tax-rates/). ## January 2026 - Email purchase orders to suppliers. Send an order by email with the PDF, CSV, or XLSX attached, and see per order whether the message was delivered or bounced. See [Sending] (/features/supply-orders/purchase-orders/sending/). - Purchase order page rebuilt. The detail page moved to tabs with a progress bar, and each order now carries its own supplier, billing, and delivery addresses plus a shipping carrier. - Documents and tags on purchase orders. Upload invoices or delivery notes straight to an order and tag them. See [Documents] (/features/supply-orders/purchase-orders/documents/). - Barcode scanning when receiving. Scan barcodes or type SKUs to fill in received quantities instead of editing every line by hand. See [Receiving] (/features/supply-orders/purchase-orders/receiving/). - Label printing. Print product labels for a purchase order with presets for common DYMO and Zebra sizes or your own measurements. See [Label printing] (/features/settings/label-printing/). - Connect additional stores. A new multi-store settings page connects other Shopify stores and maps their locations onto yours. See [Multi-store] (/features/settings/multi-store/). - Import orders from other channels. Upload orders from Amazon, eBay, Etsy, or your own records as CSV or XLSX so they count toward the forecast. See [Data import] (/features/settings/data-import-and-templates/). - Exclude products from your data. Keep products with certain tags out of forecasting entirely. See [Data exclusion] (/features/settings/data-exclusion/). - Email and export templates. Save reusable email templates and choose which columns land in exported files and on the PDF. See [Export templates] (/features/settings/data-export-templates/). - Recalculate order quantities. Refresh the quantities on an existing purchase order against a forecast view, with a preview of every change before you apply it. ## December 2025 - Bulk supplier cost import and export. Download every variant linked to a supplier as a spreadsheet, edit costs, lead times, and more, then upload to apply the changes in one go. See [Supplier variant mapping] (/features/suppliers/supplier-variant-mapping/). - Location-aware forecast quantities. With a location filter set, stock on hand and incoming quantities now count only that location. See [Locations] (/features/forecast/locations/). - Edit delivery dates later. Requested and expected delivery dates can be changed while an order is in progress or partially received. - Faster Overview dashboard. The dashboard loads from a snapshot prepared in the background, so it opens quickly and shows consistent numbers. ## November 2025 - Correct currency on every amount. Prices and costs now show the currency they were entered in across the forecast, purchase orders, supplier pages, and PDFs. - Safer automatic forecast models. Trend and seasonal models are only picked when a variant has enough steady history. Erratic sellers fall back to simpler models. See [Forecast models] (/features/forecast/forecast-models/). - Raw materials on purchase orders. Shops connected to Assemblified can order raw materials alongside Shopify variants, with stock flowing back to the connected inventory. ## October 2025 - Scheduled report emails. Build a report once and have it emailed on a schedule: stock alerts, purchase orders, or a saved forecast view, at the frequency and time you choose. See the [Reports overview] (/features/reports/overview/). - Stock alert notifications. Get an email when an item runs out of stock, drops below a threshold, or nears its reorder point. See [Notifications] (/features/notifications/overview/). - Guided setup. Installing now walks you through a short setup, and a progress page shows each sync step live. See the [onboarding wizard] (/getting-started/onboarding-wizard/). - Essential and Enhanced plans. Two plans with a 14-day trial. Advanced forecast models and email alerts are part of Enhanced. See [Subscription plans] (/getting-started/subscription-plans/). ## September 2025 - New forecast model library. Forecasting now runs on eleven demand models covering flat sellers, trends, seasonality, and mixed patterns, fitted to your own sales history. See [Forecast models] (/features/forecast/forecast-models/). - Automatic model selection. Logistified scores every model against your history and picks the best fit per variant, refreshing in the background as new sales come in. See [Automatic model optimization] (/features/forecast/automatic-model-optimization/). - New variant detail page. Each variant has its own page with stock health, sales history and forecast charts, model rankings, and related purchase orders. See [Variant detail] (/features/forecast/variant-detail/). - Rebuilt views and filters. Views moved into their own section with a live preview and a guided wizard covering filters, columns, locations, lead time, and safety stock. See [Views and filters] (/features/forecast/views-and-filters/). - Smarter reorder suggestions. Reorder point and quantity now factor in lead time, safety stock, minimum order quantity, pack size, and out-of-stock periods, with a breakdown of every number. See [Reorder suggestions] (/features/forecast/reorder-suggestions/). ## August 2025 - New purchase orders section. Purchase orders got their own list and detail pages with search, filters, editable line items, order splitting, receiving that writes stock back to Shopify, and an activity log. See the [Purchase orders overview] (/features/supply-orders/purchase-orders/overview/). - New suppliers section. Keep a supplier directory with contact details, terms, lead times, and costs, and map variants to suppliers in bulk. See the [Suppliers overview] (/features/suppliers/overview/). - Supplier data in the forecast. The forecast shows the primary supplier, minimum order quantity, and quantity on order, and reorder settings can pull lead time and costs straight from the supplier. ## July 2025 - Custom purchase order exports. Choose which product fields go into the exported Excel file and in what order. See [Export templates] (/features/settings/data-export-templates/). - Assemblified connection. Raw materials consumed by your builds flow into Logistified as demand, so forecasts account for them. See [Integrations] (/features/settings/integrations/). ## June 2025 - Overview dashboard. The app home now shows inventory KPIs such as turnover, sell-through rate, and days on hand, plus ABC analysis, seasonal trends, and a data quality card. See the [Overview] (/features/overview/overview/). - Daily reorder email report. Logistified can email a daily report of items that are out of stock, overdue, or due to be reordered soon. - Minimum order quantity and pack size. Every variant can carry both, and purchase order quantities are checked against them. See [Constraints] (/features/supply-orders/purchase-orders/constraints/). - Plans and billing. Logistified moved to paid plans with a trial, managed from a new billing page. See [Billing] (/features/settings/billing/). Earlier months covered the initial development of the forecast, purchase orders, and the dashboard before Logistified was generally available. Last updated: 10 November 2026 --- Source: https://docs.logistified.app/features/overview/overview/ # The Overview page The home screen: a five-tab page that helps you launch into your day and read the health of your inventory and sales. The Overview page is what Logistified opens to when you click the app. It’s the launchpad for your day: a quick look at your saved Forecast Views, your open Purchase Orders, your inventory KPIs, and recent sales and seasonality patterns. ## On this page - The five tabs - The home tab - Customising - Where to next ## The five tabs Logistified’s Overview page has exactly five tabs across the top: [Overview] (/features/overview/overview/) The home tab: setup guide, your saved Forecast Views, and your active Purchase Orders. [KPIs] (/features/overview/kpis/) Seven headline inventory KPIs, a compact Inventory Health score, and the ABC + SKU Revenue charts. [Timelines] (/features/overview/timelines/) The past 30 days of daily orders, sales, units sold, and inventory movement. [Seasonal Analysis] (/features/overview/seasonal-analysis/) Shop-wide seasonality: orders and units by weekday and by month, compared year-over-year. [Data Quality] (/features/overview/data-quality/) A live inventory health score and four counters (missing SKUs, missing costs, out of stock, inactive items), each linking to the affected variants. There is no “Forecast widget”, no separate “Purchase orders tile”, and no general “drill-down” system on the Overview page. The KPIs tab keeps a compact Inventory Health score with a View Data Quality button; the detailed counters live on the Data Quality tab. The ABC chart (KPIs tab) and the Data Quality counters are the places that click through to a pre-filtered Forecast view. ## The home tab This page covers the home tab: what you land on when you click the “Overview” tab. The KPIs, Timelines, Seasonal Analysis, and Data Quality tabs have their own pages. The layout is the same at every stage: your saved Forecast Views and active Purchase Orders cards sit side by side (stacked on narrow screens). Until you dismiss it, a Setup guide banner sits above them. ### The Setup guide banner A collapsible banner that tracks four setup steps and shows how many you’ve completed (“2 of 4 completed”). The banner starts expanded; click its header to fold it up or open it again. Only one step’s details are open at a time, and the first unfinished step opens automatically. Each open step has a button that jumps straight to the right page: - Create your first forecast view: set up a custom view to analyze your inventory and forecasting data. Only views you create yourself count; the auto-generated ones don’t tick this off. - Add your first supplier: create a supplier and connect it to your variants, so lead time, MOQ, and pack size make reorder suggestions accurate. - Create your first purchase order: record what you’re buying from suppliers so incoming inventory shows up in your forecasts. Any purchase order counts, including completed ones. - Allow email notifications: grant email consent so stock alerts and scheduled reports can reach you. This checks the consent itself: setting up notification rules without granting email consent leaves the step open. Each step is checked off automatically from your actual data; there’s nothing to tick by hand, and finished steps can no longer be expanded. Once all four are done, the banner shrinks to a one-line “Setup complete” row with a Dismiss button. While the banner is expanded, its footer links to this documentation site (Documentation), a YouTube playlist (Video tutorials), a Give feedback form, and a Hide guide button for removing the banner before you finish the steps. Hide guide asks you to confirm; Dismiss (on the “Setup complete” row) doesn’t. Both are permanent and apply to everyone in your shop; the guide won’t reappear on this page. Collapsing the banner, by contrast, just folds it up in your current browser; it stays available and remembers whether you left it open. Note Dismissing or hiding the guide also removes the Give feedback form; it’s the only feedback entry point on this page. Support and documentation stay reachable from the help icon in the app’s header. ### Forecast Views and Purchase Orders - Forecast Views. Your saved views with three tabs: Starred (the default), Autogenerated, All. Each row links to that view at /app/forecast/{viewId} and carries a Starred / Auto-generated / Custom badge. A Create view row is pinned at the bottom of the list; if the selected tab has no views yet, the card shows an empty state with a Create view button instead. - Purchase Orders. Your active POs with six status tabs: All, Draft, Sent, Confirmed, In Progress, Received. The All tab hides completed POs. “Confirmed” also lists partially-confirmed POs; “Received” also lists partially-received POs. When the assigned supplier has a nonblank name, a gray dot and supplier name appear beside the order name or number. Click any row to open the PO detail page. If the filter is empty, you get a Create order button. The card is a recent-activity snapshot rather than a full list: it loads only your 10 newest purchase orders and then applies the tab filter to those, so a status tab can look empty even when older orders in that status exist. Click the Purchase Orders heading for the complete list. Both cards remember the tab you last picked, per browser. Note The home tab is a launchpad, not a KPI dashboard. Numbers and charts live on the KPIs, Timelines, and Seasonal Analysis tabs. ## Customising Two settings shape what you see on this page: - Settings → Dashboard. Pick a Forecast View to filter the data the KPIs, Timelines, and Seasonal Analysis tabs work from. The two Analytics Insights charts are the exception; ABC and SKU Revenue Distribution ignore that view filter entirely. Choose “No filter (show all data)” to include every variant. Changing this resets the calculation progress while the new view’s data is computed. The same page also has an Inventory value basis setting (cost or retail) that controls how the Avg. Inventory Value KPI, the Stock-to-Sales Ratio KPI, and the Inventory Value per Day chart value your stock; see the [KPI reference] (/reference/kpi-reference/#average-inventory-value). Unlike the view filter, changing the basis doesn’t reset anything; it just applies from the next nightly snapshot onward. - Settings → ABC Analysis. The lookback period (in days) used to classify variants into A, B, and C tiers. This affects the ABC chart and the SKU Revenue Distribution chart on the KPIs tab, plus the ABC column on the Forecast page; all three read the same variant-revenue table. It does not change the seven headline KPI tiles, which use a fixed 30-day window. Changes land on the next scheduled refresh, roughly every 24 hours. Tip If a card shows “no data” on a fresh install, there is simply nothing to show yet; Logistified keeps you on the data-loading progress screen until the initial Shopify sync finishes, so reaching this page means that sync is already done. Use the Setup guide banner to see which setup steps are still open. (Settings → Data Import is a different thing: it imports orders from other sales channels such as Amazon or eBay, not your Shopify sync.) ## Where to next - [Overview → KPIs] (/features/overview/kpis/): the seven headline inventory metrics, plus inventory health and ABC. - [Forecast → Overview] (/features/forecast/overview/): when you’re ready to dig into the data behind the KPIs. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/overview/kpis/ # KPIs The seven headline inventory KPIs, a compact Inventory Health score, and the ABC + SKU Revenue charts. The KPIs tab is the analytical view of Logistified’s Overview page. It has three sections, top to bottom: the headline KPI tiles, a compact Inventory Health score row, and a pair of analytics charts. ## On this page - Section 1: Key Performance Indicators - Section 2: Inventory Health - Section 3: Analytics Insights - The time window - Data freshness - See also [anchor: section-1--key-performance-indicators] ## Section 1: Key Performance Indicators Seven tiles arranged in two rows. Each tile shows one number, an info icon whose hover card explains the metric, and (when a comparison is available) a trend badge showing an up arrow, a down arrow, or a dash for no change, plus a percentage. The badge is deliberately neutral in colour: it shows direction only. Logistified does not decide whether that’s good or bad; that depends on the metric. The seven KPIs: - Inventory Turnover: how many times your inventory cycled in the period. Higher = leaner stock. - Sell-Through Rate: units sold in the period as a percentage of the stock that came in during the period. - Avg. Inventory Value: average value of inventory held during the period, at cost by default (variants without a unit cost contribute 0 and are counted in the tile’s tooltip). Settings → Dashboard can switch the basis to retail. - Days On Hand: how many days of sales your inventory covers, taken from the most recent snapshot day. Your [DOH] (/reference/glossary/#doh). - Stock-to-Sales Ratio: average inventory value divided by average sales value over the period. Higher = more days of cover. - Inventory Gap: percentage deviation from your target inventory levels. - Revenue Per Unit: average revenue per unit sold. A mix indicator. Note The KPI tiles are read-only; they don’t click through anywhere. Use the Forecast page to dig into the variants behind a number. [anchor: section-2--inventory-health] ## Section 2: Inventory Health A compact row showing your inventory health score (0–100), its label (Excellent / Good / Needs Attention / Poor), and a small score bar, with a View Data Quality button on the right. The four counters behind the score (missing SKUs, missing costs, out of stock, inactive items) live on the [Data Quality tab] (/features/overview/data-quality/), which is where you drill into and fix them. Tip The health score is a quick gut check, not a hard threshold: it counts issues; it doesn’t measure what share of your inventory is affected. Open the Data Quality tab and decide whether the counters actually matter for your shop. [anchor: section-3--analytics-insights] ## Section 3: Analytics Insights The bottom of the tab has two charts, stacked: - ABC Analysis: a donut chart of how many variants fall into each tier, with a legend underneath. Both the counts and the links come from the same capped sample of at most 500 variants per tier, so on a large catalog a slice can read 500 when the real tier is bigger. Each tier in the legend (A Items / B Items / C Items) links through to a Forecast view of those variants. - SKU Revenue Distribution: a donut chart plus a ranked list beside it, covering your top 100 variants by revenue rather than the whole catalog. Within those 100, the ones that together make up 95% of the charted revenue each get their own slice; the rest are pooled into a single “Other SKUs” slice but are still listed individually in the panel. Use it for a Pareto check. ## The time window The KPI tiles use a fixed 30-day window ending on the latest nightly snapshot date. The trend badge compares that window against the same 30-day window shifted back by one day, so it reads as a short-term nudge rather than a month-over-month change. Neither is configurable. Inventory Gap is the exception among the tiles: it is measured against your current stock levels, not against the window. The two Analytics Insights charts sit outside this window entirely; they use the ABC lookback described below. Both Analytics Insights charts use a separate lookback period that you can adjust at Settings → ABC Analysis (60 days by default; 1–730 allowed). The ABC tiers and the SKU revenue shares are computed together from the same table, so the setting moves both. It does not change the seven KPI numbers above, and a change only takes effect on the next scheduled refresh, roughly every 24 hours. The Inventory Health score (and the counters behind it on the Data Quality tab) reflects the current state, not a period average, so it doesn’t depend on the window. ## Data freshness Next to the “Key Performance Indicators” title you’ll see a caption reading “Last 30 days · Data as of ”, with an info icon. Hover it for the explanation: these numbers come from a nightly inventory snapshot, so they cover data up to the date shown, usually yesterday. The Forecast and Reporting pages read current data and can show more recent numbers. On a brand-new shop, the caption reads “No snapshot yet” until the first snapshot finishes overnight, after which the date appears here going forward. Note This freshness note is about the KPI tiles and Analytics Insights only. The Inventory Health score just above them and the counters on the Data Quality tab are computed live on every page load, not from the snapshot. ## See also - [Overview → Data Quality] (/features/overview/data-quality/): the four health counters and how to fix them. - [Reference → KPI reference] (/reference/kpi-reference/): formulas and interpretation for every KPI. - [Forecast → Overview] (/features/forecast/overview/): the main destination when you click through. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/overview/timelines/ # Timelines Five daily-aggregate charts of the past 30 days: orders, sales, units sold, and inventory movement. The Timelines tab of Logistified’s Overview page shows five charts of your shop’s activity over the past 30 days, one bar or area per day. It’s a quick read on cycles and unusual depletions, not a per-event log. ## On this page - Order Timelines - Inventory Timelines - What to look for - Data freshness - See also ## Order Timelines Three charts, grouped at the top of the tab: - Orders per Day: bar chart of the number of orders placed each day. - Sales Value per Day: area chart of total sales revenue each day, in your shop currency. - Variants Sold per Day: bar chart of how many distinct variants sold each day. ## Inventory Timelines Two charts at the bottom of the tab: - Inventory Change per Day: bar chart of net inventory movement each day. Green bars are net additions (stock in); purple bars are net depletions (stock out). - Inventory Value per Day: area chart of total inventory value at the end of each day, at cost by default (Settings → Dashboard can switch the basis to retail). Days recorded before a basis change keep their original valuation, so the chart shows a one-time level shift when the basis changes, including the August 2026 update, which changed the default from retail to cost. ## What to look for Use these charts for pattern-spotting at a glance: - A weekly rhythm in the orders chart (strong Mondays, quiet Sundays) confirms what your customers actually do. - A purple spike in the inventory change chart that doesn’t line up with high sales suggests a write-off, a stock take adjustment, or a transfer worth checking. - A gentle slope in inventory value while orders stay flat hints at slow-moving stock building up. Note The window is fixed at the past 30 days and there are no filters: no variant filter, no event-type filter, no date-range picker. For deeper or longer-range analysis, use the Forecast page or a custom Report. ## Data freshness Next to the “Order Timelines” title you’ll see a caption reading “Last 30 days · Data as of ”, with an info icon explaining that these charts come from a nightly inventory snapshot and can lag a day behind the Forecast and Reporting pages. See [KPIs → Data freshness] (/features/overview/kpis/#data-freshness) for the full explanation, including what the caption shows before your first snapshot exists. ## See also - [Overview → Seasonal Analysis] (/features/overview/seasonal-analysis/): the longer-cycle view (weekday, month, year-over-year). - [Reports → Overview] (/features/reports/overview/): schedule a report when you need history beyond 30 days. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/overview/seasonal-analysis/ # Seasonal Analysis Shop-wide seasonality: orders and units by weekday and by month, compared current year vs. previous year. The Seasonal Analysis tab of Logistified’s Overview page answers two questions about your shop as a whole: when in the week, and when in the year, do you sell more? It compares the current year against the previous year so you can see whether the pattern is repeating. ## On this page - Seasonal Orders Trends - Seasonal Unit Trends - What it doesn’t show - Data freshness - See also ## Seasonal Orders Trends Three charts at the top of the tab, all measuring order count: - Orders Per Weekday: radar chart with seven points, one per weekday. Two overlapping shapes: current year (solid) and previous year (dashed). - Orders per Month (Current Year): donut chart. The outer ring is one slice per month; the inner ring rolls those up into four quarters. - Orders per Month (Previous Year): the same donut for the prior year, side-by-side for comparison. ## Seasonal Unit Trends Three charts at the bottom of the tab, identical in shape but measuring units sold instead of order count: - Variants Sold Per Weekday: weekday radar, current vs. previous year. - Variants Sold per Month (Current Year): month + quarter donut. - Variants Sold per Month (Previous Year): month + quarter donut, prior year. ## What it doesn’t show This tab is intentionally a shop-wide view. It tells you whether your shop has weekly or monthly seasonality patterns, not which individual variants are seasonal. For variant-level seasonality, look at the Forecast page: variant detail charts show that variant’s sales history, and seasonal forecast models react to per-variant patterns when Auto chooses one. There is no per-variant “seasonality strength” score on this tab. Tip A radar shape that’s flatter this year than last suggests your weekday mix is evening out, common when you launch a wholesale channel or start running weekend ads. A quarter slice that’s grown noticeably year-over-year is worth checking against your marketing calendar. ## Data freshness Next to the “Seasonal Trends” title you’ll see a caption reading “Data as of ”, with an info icon explaining that this analysis comes from a nightly inventory snapshot and can lag a day behind the Forecast and Reporting pages. See [KPIs → Data freshness] (/features/overview/kpis/#data-freshness) for the full explanation, including what the caption shows before your first snapshot exists. ## See also - [Overview → Timelines] (/features/overview/timelines/): the short-cycle view (past 30 days). - [Forecast → Variant detail] (/features/forecast/variant-detail/): per-variant history when the shop-wide pattern doesn’t answer your question. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/overview/data-quality/ # Data Quality A live inventory health score and four counters (missing SKUs, missing costs, out of stock, inactive items), each linking to the affected variants. The Data Quality tab is where Logistified reports gaps in your catalog data that make forecasts and reorder suggestions less reliable. It shows a single health score and four counters, each with a link to the exact variants behind the number. ## On this page - The health score - The four counters - Fixing an issue - Data freshness - See also ## The health score The score in the tab’s header starts at 100 and goes down as issues accumulate. Each issue subtracts a weighted amount: Out of Stock counts 1.5, Missing Costs 1.0, Missing SKUs 0.5, and Inactive Items 0.5. The score never goes below 0 and is labelled by range: Excellent (90+), Good (75–89), Needs Attention (50–74), Poor (below 50). Hover the info icon next to the score to see this breakdown in-app. Because the score counts issues rather than measuring what share of your inventory is affected, large catalogs reach low scores faster than small ones. Treat it as a quick gut check, not a hard threshold. The same score also appears as a compact row on the [KPIs tab] (/features/overview/kpis/), with a View Data Quality button that brings you here. ## The four counters - Missing SKUs: variants without a SKU set in Shopify. Without a SKU, variants are hard to match in CSV imports and supplier mappings. - Missing Costs: variants without a unit cost (or with a cost of zero). Reorder math and profit metrics need a cost. - Out of Stock: variants whose total on-hand quantity is at or below zero. This is the heaviest-weighted issue, and the only one whose count turns red when non-zero; the other three turn amber. - Inactive Items: variants with no sales in the last 6 months. A high number isn’t necessarily a problem (long-tail catalogs have many slow movers), but inactive variants still count against the score. ## Fixing an issue When a counter is greater than zero, a View link appears on its card. It opens a Forecast view pre-filtered to exactly those variants, so you can work through them one by one. For very large issue lists the view covers the first 500 affected variants. Tip A non-zero counter isn’t automatically a problem. Open the View link and decide whether the variants actually matter for your shop; a big Inactive Items count on a long-tail catalog is normal. ## Data freshness Unlike the KPIs, Timelines, and Seasonal Analysis tabs (which read from a nightly snapshot), the Data Quality counters are computed live every time you open the tab, so they always reflect your current catalog. The Live data caption in the header reminds you of this. If the numbers can’t be loaded, the tab shows “Data quality is unavailable”; try again after data processing completes. ## See also - [Overview → KPIs] (/features/overview/kpis/): the headline KPI tiles and the compact health score row. - [Reference → KPI reference] (/reference/kpi-reference/): definitions for every counter. - [Forecast → Views & filters] (/features/forecast/views-and-filters/): how the drill-down views behave. Last updated: 24 August 2026 --- Source: https://docs.logistified.app/features/forecast/overview/ # Forecast Logistified's Forecast page answers one question per variant: how many do I need to buy, and when? Logistified’s Forecast page answers one question per variant: how many do I need to buy, and when? It’s the working surface most operators spend the most time on, the place where sales history becomes a daily decision about which suppliers to email today. A forecast here is not a sales report. Sales reports look backwards; the Forecast page looks forwards. The numbers in each row are projections: expected demand, the day you’ll need to reorder, the quantity to buy. ## On this page - What the Forecast page shows - When to use it - What you can do here - Beginner workflow - How it all fits together - Key concepts - Where to next ## What the Forecast page shows Each row in the table is one product variant. Each column is a fact, a metric, or a suggestion. The page comes with a small set of columns visible out of the box; you add the reorder columns yourself from the Columns popover. The view button in the toolbar shows the name of the open view. Click it to search and switch between your saved views: combinations of filters, columns, and sort orders. The toolbar at the top gives you search, filters, the columns picker, sort, the location picker, forecast settings (model + history period), the Amplifier button, and a “Create PO from selected” action. The bar underneath the table carries the page controls and an Export button; see [Exporting the forecast] (/features/forecast/export/). ## When to use it - Daily. Check which variants have an overdue or imminent [reorder date] (/reference/glossary/#reorder-date). Plan the orders you need to place today. - Weekly. Review reorder dates in the next 7–14 days; group by supplier; fire purchase orders in batches. - Drill-down. Open a saved view from the Overview page (or click the ABC chart on the KPIs tab), then click a row to see the full forecast for that variant. ## What you can do here [Forecast view table] (/features/forecast/view-table/) Every column on the table: what it shows, where it comes from, when it's empty. [Supply view] (/features/forecast/supply-view/) The forecast as a calendar of weeks, months, or quarters, with what to act on in each period. [Forecast models] (/features/forecast/forecast-models/) The 12 forecast models and when each one fits. [Automatic model optimization] (/features/forecast/automatic-model-optimization/) Let Logistified pick the best model per variant. [History period] (/features/forecast/history-period/) Auto vs. Manual history windows and which to start with. [Views & filters] (/features/forecast/views-and-filters/) Save your filter + column combination as a reusable view. [Variant constants] (/features/forecast/variant-constants/) Per-variant min / max / target / reorder-point overrides. [Reorder suggestions] (/features/forecast/reorder-suggestions/) The Reorder Forecast explained: how the suggestion is built. [Growth amplifiers] (/features/forecast/growth-amplifiers/) Nudge a forecast for a campaign or product launch. [Locations & multi-location math] (/features/forecast/locations/) How single-location vs. all-locations filters change the math. [Variant detail] (/features/forecast/variant-detail/) Per-variant forecast tuning and history drill-down. [Create a PO from the forecast] (/features/forecast/create-po-from-forecast/) Turn a row (or selected rows) into a purchase order. [Exporting the forecast] (/features/forecast/export/) Download a view as XLSX or CSV, or combine several saved views into one file. ## Beginner workflow The Forecast page can look complicated on day one: many columns, many filters, an Auto mode that quietly does its own thing. Here’s a way in: 1. Open the Forecast page. 2. Open the Forecast settings panel. Switch the Model to Average. 3. Switch the History period to Manual, then pick Last 90 days. 4. From the Columns popover, add Reorder Forecast, Reorder Date, and Days of Stock to the visible columns. 5. Sort by Reorder Date ascending. 6. Save as a view named “Beginner: Average 90 d.” Star it for quick access. Now look at the top rows. Do the suggested quantities and reorder dates roughly match your gut? If yes, you trust the inputs; switch the model back to Auto and let the system pick a better model per variant. If no, drill into a variant detail page; the History tab usually shows why. Tip The Average model with a fixed 90-day window has no hidden parameters. The reorder math is fully predictable. Once you trust it, switching to Auto will produce better suggestions for most variants, but starting transparent and switching to magic later builds your judgement faster than starting with magic. ## How it all fits together The Forecast page is the visible layer. Underneath, the math chains together: 1. Logistified watches your Shopify sales and aggregates them into a per-variant sales history. 2. A forecast model (picked automatically or chosen by you) projects demand forward. 3. Lead time, MOQ, pack size, and safety stock come from the variant’s [primary supplier] (/reference/glossary/#primary-supplier). 4. A simulation walks the forecast horizon forward day by day (draining on-hand at the predicted demand and crediting incoming POs and TOs on their expected arrival dates) to produce the reorder columns: [reorder point] (/reference/glossary/#reorder-point), [reorder date] (/reference/glossary/#reorder-date), [reorder quantity] (/reference/glossary/#reorder-quantity), and [days of stock] (/reference/glossary/#days-of-stock). The most common operator workflow then runs in the opposite direction: filter to “Reorder within 14 days,” select rows, click “Create PO from selected.” A draft purchase order appears, prefilled with the suggested quantities. ## Key concepts - [Reorder forecast] (/reference/glossary/#reorder-forecast): the combined “how many” and “when” view for one variant. - [Reorder point] (/reference/glossary/#reorder-point): the stock level at which to reorder. - [Reorder date] (/reference/glossary/#reorder-date): the day on-hand will hit the reorder point. - [Reorder quantity] (/reference/glossary/#reorder-quantity): the suggested order size after MOQ, pack size, and EOQ adjustments. - [History period] (/reference/glossary/#history-period): the window of past sales the model looks at. - [Growth amplifier] (/reference/glossary/#growth-amplifier): a manual nudge for a campaign or known event. - [View] (/reference/glossary/#view): a reusable saved filter + setup. Used by Forecast, Notifications, Reports, and PO creation; see [Views & filters] (/features/forecast/views-and-filters/) for the cross-app picture. ## Where to next - The [Forecast view table] (/features/forecast/view-table/) reference: every column documented. - The [Reorder suggestions] (/features/forecast/reorder-suggestions/) deep-dive: how the suggestion is built end to end. - The [Reference glossary] (/reference/glossary/): every forecast term defined. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/view-table/ # Forecast view table Every column on the Forecast view: what it shows, where it comes from, when it's empty. The Forecast view table is the heart of Logistified’s Forecast page. Each row is one product variant; each column is a fact, a metric, or a suggestion you can act on. This page is the reference: what each column shows, when it’s visible by default, when a cell is empty, and where the value comes from. If you’re looking up a single column quickly, jump to [Reference → Forecast column reference] (/reference/forecast-column-reference/), the same data flat-alphabetised. ## On this page - What you see by default - Core columns explained - All columns, by category - Scrolling - Paging - Show / hide columns - Empty-cell meaning - See also ## What you see by default A new view starts with a small set of columns: Column Plain-English meaning Image The variant image. Product/Variant Title The product title with the variant title (e.g. “Red / Medium”) and SKU beneath it. In Stock The variant’s inventory, with incoming stock beneath it when there is any. Reorder Date The day you should place the order. Days of Stock How many days your stock lasts at the forecast pace. Reorder Forecast How many units to order. Supplier The supplier’s name. A new view shows 10 rows per page; all locations are included; the default forecast settings are Average model with a fixed Last-90-days history window. For more reorder detail, add columns from the Reorder point metrics, Reorder quantity metrics, and Days of stock metrics groups below. ## Core columns explained These five are the ones you’ll look at every day. They get prose treatment because the math behind them isn’t obvious from the label. [anchor: inventory-quantity] ### In Stock How this column behaves depends on the location filter: - All locations (default): the variant’s on-hand across every location. This mirrors Shopify’s on-hand value. - One or more locations selected: switches to the sum of available quantity at those locations (Shopify’s available bucket: on-hand minus committed), not on-hand. The semantics change deliberately, because per-location planning works against what’s truly orderable from that location. Either way, the column updates within a minute or so of stock moving in Shopify. The cell can also show context beneath the quantity: - “+ X Incoming” when open incoming quantities exist. - “⚠ X overdue. Awaiting receipt” when part of that incoming stock is past its delivery date and still needs receiving. - “− X planned outflow” when inventory commitments or launch plans that feed the forecast still expect to take stock of this variant, counted from tomorrow on: a plan dated today counts 0. It’s the same figure the forecast deducts. See [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/#planned-outflow). - “In X Draft POs” when the variant already appears on one or more Draft POs. Hover the cell to see those Draft PO rows alongside incoming, on-hold, and disputed PO quantities. When plans take stock out, the hover card also has a Planned outflow tile with the total and how many plans contribute, and one row per plan with its plan number (a link to the plan), status, start date, and what it still takes from tomorrow on. The hover card also lists the variant’s available quantity per location, under a By location heading below the purchase-order rows, with a Total available figure alongside the heading. Worth knowing: - It always lists every location, even when the view is filtered to one, so the number in the cell can legitimately differ from the total in the hover card. - Locations are ordered by available quantity, highest first. A location where the variant isn’t stocked shows a dash; a location that stocks it but has none left shows 0. A location Logistified can’t name reads “Unknown location”, and on very large shops the list ends with +N more locations. - Where you’ve set per-location [variant constants] (/features/forecast/variant-constants/), the Min / Reorder / Target / Max values appear under that location’s name. In the [Supply view] (/features/forecast/supply-view/#the-in-stock-column), the column shows two plain lines instead: what’s available and what’s incoming. The hover card is the same. Worth distinguishing from related columns: - On Hand: exposes the on-hand value explicitly, regardless of location filter. - Committed: units reserved for orders you haven’t shipped yet. - Reserved: a separate Shopify reserve bucket, usually empty unless you’re using specific Shopify reserve flows. [anchor: actual-reorder-quantity] ### Reorder Forecast Logistified’s suggestion for: if I place a PO today, how many units do I need to stay safe through one more lead-time cycle until the stock arrives? It’s the recommended order quantity after MOQ, pack size, and economic order quantity adjustments. The cell shows several visual signals: - A green “EOQ” pill next to the number when economic order quantity beat the raw demand-based number. Logistified prefers EOQ because it minimises holding + ordering cost. - A MOQ progress bar underneath the number, colored: - Red if demand fills less than 70% of the supplier’s MOQ; you’re ordering mostly to satisfy the minimum. - Orange if demand fills 70–99% of MOQ. - Emerald if demand exceeds MOQ comfortably. - A sub-line appears in two cases: - “X Back Orders”: when your variant’s inventory policy is “Continue selling when out of stock,” and X customer orders accumulated while you were out. Their units are rolled into the next reorder. - “X Lost Sales due to missed ROP”: when your variant’s inventory policy is “Deny,” and X units of demand were lost while you were out. Counts toward reporting; not added to the reorder. Hover the cell for the full math breakdown; every input value used in the calculation appears in the hover card. ### Reorder Date The day Logistified expects your on-hand to drop to the reorder point. Color-coded: Color Meaning Red Overdue: you should have reordered already. Warning yellow Due today, or within the next 7 days. Muted Due in weeks or months. A dash (no date) No recent sales: the model lacks signal. –––––––– —————————————–– When the cell shows a dash / “No recent sales data”, treat it as “I can’t tell yet.” It’s not a bug; it’s the model refusing to guess. The forecast counts sales up to yesterday, so the day’s results don’t change with the time you look. An item whose only sales are from today says Today’s sales count from tomorrow instead, on its own page and in a view that shows Sold Today; the item’s Sales & margin tab already includes them. ### Days of Stock How many full days your stock lasts at the model’s predicted sales rate before you’d first miss sales. Incoming stock counts only if it arrives before that day; when you’d run out before a delivery lands, the cell warns Stock-out before incoming. The related Days of Stock with All Incoming column also counts deliveries that land after such a stockout, useful for “how long until I run out for good, with everything that’s already on the way?”. It’s never lower than Days of Stock. Both columns show a placeholder when the variant has no sales signal (or has so much stock the math overflows). ### Reorder Point The inventory level at which you should reorder. At a high level: the demand you expect during your lead time plus a safety stock cushion. The inputs: - Forecast model output → daily demand. - Lead time from the variant’s [primary supplier] (/reference/glossary/#primary-supplier). - Safety stock: automatic (95% service level by default) or a value you set. - Force majeure factor if you’ve enabled it. - Supplier reliability: buffers the cushion if the supplier’s on-time rate is lower than ideal. For the full breakdown of these inputs (base safety stock, supplier-reliability buffer, force-majeure factor, lead-time demand), open the variant detail page → Safety Stock Breakdown panel. That’s where the per-component numbers behind this cell live. ## All columns, by category Every column the table can show, grouped by topic. The Columns popover sorts the same columns into its own groups, alphabetically within each. ### Identity Column What it shows Variant ID The variant’s Shopify ID, with a copy button. Product ID The product’s Shopify ID, with a copy button. SKU Your stock-keeping unit. Barcode The variant’s barcode, with a copy button. Vendor The Shopify vendor name. Useful for filtering. Product Type The Shopify product type. Useful for filtering. Status The product’s Shopify status: Active, Draft, or Archived. ### Titles & descriptions Column What it shows Variant Title The variant title. Product Title The product title. Product/Variant Title The product title with the variant title and SKU beneath it. ### Images Column What it shows Image The variant image. ### Inventory quantities Column What it shows In Stock The variant’s inventory. Default visible. In Draft PO Whether the variant already appears on at least one Draft PO. Hidden by default; useful as a Yes/No filter before adding rows to another draft. On PO with Status Which purchase order statuses the variant currently sits on: Draft, Sent, Confirmed, and so on. Hidden by default; filter to a status, or exclude “Any open PO” to find items you haven’t already reordered on any status. On Hand Physically present units. Committed Units reserved for orders not yet shipped. Reserved A separate Shopify reserve bucket. Sellable Online Quantity Units available to the online storefront. Variant Tracked Whether Shopify tracks inventory for this variant. Location Counts Number of locations that stock this variant. Stock at Supplier Hidden by default. Your own stock physically held at suppliers. Not affected by a location filter. Hover a non-zero value for a per-supplier breakdown. See [Supplier-held stock] (/features/forecast/supplier-held-stock/). Stock at Supplier (Available) Hidden by default. The part of your supplier-held stock not reserved by an open release. Stock at Supplier (Reserved) Hidden by default. The part of your supplier-held stock reserved by an open release. ### Pricing Column What it shows Price The selling price. Shopify Unit Cost The variant’s unit cost (cost per item) from Shopify. Supplier Unit Cost The cost price you have on file for this row’s supplier, in that supplier’s currency. Unit Price Measurement Type For unit-priced products: type of measurement. Holding Cost/Year Annual cost to hold one unit, in your currency. Used in EOQ math. ### Categories & tags Column What it shows Category Name The product’s category. Tags Shopify tags. ### Shipping & origin Column What it shows Requires Shipping Whether this variant is shipped. ### Variant flags Column What it shows Is Gift Card Variant is a gift card. ### Measurements Column What it shows Measurement Weight The unit weight. ### Taxes Column What it shows Taxable Whether tax applies. Tax Code Shopify tax code. ### Supplier columns (from the primary supplier) Column What it shows Primary Supplier Whether the supplier shown on this row is the variant’s primary supplier. Useful when you filter by supplier. Supplier The supplier name. Default visible. Supplier SKU The SKU your supplier uses for this variant. MOQ Minimum order quantity. Pack Size The packaging increment the supplier ships in. ### Manufacturing (Assemblified) Column What it shows Buildable Now Units you could assemble right now from the component stock you have on hand, pooled across the locations you’ve selected (or all locations, if none are selected). Shown on Bill of Materials (BOM) items only, hidden by default. Buildable incl. Supplier Stock Same as Buildable Now, but also counts your own stock that’s physically held at suppliers. Limiting Component The single component currently capping Buildable Now, the one you’d need to restock first to build more units. Pre-Assembled Finished units already built and sitting on the shelf at the selected locations. In Pre-Assembled Stock For a raw material, how many units of it are already locked up inside pre-assembled parent items on the shelf. Shown on raw-material rows only. These five columns need the Assemblified app connected to your shop; install it from the Shopify App Store and Logistified detects the connection on its own; there’s nothing to configure here. If Assemblified isn’t connected, the cells show a short reason with a link to open Assemblified instead of a number. If it’s connected but the data can’t be reached, the cells show a Retry button instead. Hover a populated cell for the full breakdown behind it: for Buildable columns, which components go into the build and how much of each you have; for In Pre-Assembled Stock, which pre-assembled items are holding the material. Note These columns only appear in the default forecast layout, not in Supply or Sales performance mode, and, unlike every other column, they can’t be sorted, filtered, grouped, or included in an export. Hide them before exporting a view if you’d rather not see blank columns in the file. ### Variant overrides Column What it shows Min Inventory A per-variant minimum stock level you’ve set. Max Inventory A per-variant maximum stock level you’ve set. Static Reorder Point A fixed reorder point you’ve set yourself. Target Inventory A per-variant target stock level you’ve set. Note Variant overrides are for display and for the min/max replenishment workflow. They don’t change the forecast model’s reorder math; the simulation uses its own computed reorder point. These columns are read-only on the Forecast page; set values from Settings → Products → Variant Constants. See [Variant constants] (/features/forecast/variant-constants/). ### Sales metrics Column What it shows Daily Average Sales Average units sold per day over the last 30 days. Hover for the 60- and 90-day averages. Daily Avg Sales (30d), (60d), (90d) Average units sold per day over the fixed window. Monthly Average Sales Average units sold per month over up to the last 12 months. Monthly Avg Sales (3m), (6m), (12m) Average units sold per month over the fixed window, the current month included. Monthly Total Sales Units sold so far this calendar month. Monthly Total Sales (3m), (6m), (12m) Units sold over the fixed window, the current month included. Total Sales Units sold in the last 30 days. Hover for the 60- and 90-day totals. Total Sales (30d), (60d), (90d) Units sold over the fixed window. Sales Days/Month (3m), (6m), (12m) Average number of days per month with at least one sale, over the fixed window. A day counts once no matter how many orders it had; this isn’t an order count. Low values flag sporadic sellers. Sell-Through (30d) Share of the units you had that sold in the last 30 days: sold ÷ (sold + In Stock). Empty when there is nothing sold and nothing in stock. Sell-Through Change (30d) Percentage-point change of the 30-day sell-through compared with the 30 days before. Sales Velocity (weekly) Average units sold per week over the last 4 complete weeks (Monday to Sunday). Momentum (7d/28d), Momentum (14d/90d) Recent daily sales divided by the longer-term daily average. 1 = selling at the usual rate; above 1 the item is accelerating, below 1 it is slowing. Momentum Trend (7d/28d), (14d/90d) Up when the short-term rate is at least 20% above the long-term rate, Down when at least 20% below, Stable in between, Insufficient data when there isn’t enough history. Filterable. YoY Change (28d) Units sold in the last 28 days compared with the same 28 days one year earlier (52 weeks back, so weekdays line up), in %. Empty until the item has 13 months of history. Gross Profit at Risk Gross profit you would lose to a stockout that an order placed today can no longer prevent: daily gross profit × the days you’d run out before the supplier’s lead time, plus the commitment and launch-plan units you couldn’t ship in that time. 0 when stock covers the lead time. Sort by it to see what needs ordering first. Sold Today Units sold so far today (UTC). The forecast itself only uses complete days. Sold Today vs 30d Avg Today’s units compared with the average daily sales of the last 30 days, in %. Green from +10%, amber from −10%. ### Incoming & on-hold metrics Column What it shows Incoming Quantity Confirmed-and-not-yet-received units across open POs and TOs. On Hold Quantity Units on POs in “On Hold” status. Disputed Quantity Units on POs in “Disputed” status. Last Received Date Hidden by default. The date of the variant’s most recent purchase order receipt. Last Received Quantity Hidden by default. The total quantity received on that most-recent purchase order. Draft POs are shown as context only. They do not increase Incoming Quantity and do not change reorder quantity, days-of-stock, or incoming inventory math until the PO moves into an incoming-producing status. ### Reorder point metrics Column What it shows Reorder Point The inventory level you should reorder at. Safety Stock The calculated safety buffer (rounded up) built into the reorder point. Days Until Reorder Point Days from today until your stock falls to the reorder point. Reorder Date The calendar date you should fire the order. Color-coded. Reorder Point Overdue How many days past the reorder date you already are. ### Reorder quantity metrics Column What it shows Reorder Forecast The recommended order quantity after MOQ, pack size, and EOQ adjustments. EOQ Economic order quantity: the order size that minimises holding + ordering cost. Predicted Sales (horizon) Total units expected during the forecast horizon. Forecast Horizon How far forward the forecast looks, in days. ### Days of stock metrics Column What it shows Days of Stock Full days of stock left before you’d first miss sales at the forecast pace. Incoming counts if it arrives first. Out of Stock Date The first day your stock would hit zero. Incoming counts if it arrives before then. Days of Stock with All Incoming Days until your stock is finally used up, counting every open PO and TO, including late ones. Out of Stock Date (incl. all incoming) The day your stock is finally used up, with every incoming delivery counted. OOS With Reorder When you’d run out if you placed the suggested reorder now. ### ABC analysis Column What it shows ABC Analysis A / B / C tier, driven by revenue concentration over the ABC lookback period. ### Demand pattern Column What it shows Demand Pattern How regularly the item has sold, classified from the last 12 months of daily sales: Smooth, Intermittent, Lumpy, Erratic, or Insufficient data. Note Demand Pattern looks at how many days had at least one sale, not how many orders came in. Smooth sellers move in steady quantities on a predictable schedule. Intermittent sellers go long stretches with no sale but sell steady quantities when they do. Lumpy sellers combine both long gaps and wildly varying quantities, the hardest pattern to forecast accurately. Erratic sellers sell on most days but in wildly varying quantities. Insufficient data means fewer than two days with sales in the last 12 months. Filter to Intermittent or Lumpy to find your sporadic sellers. ### Sales Performance mode When a view uses the Sales Performance display mode, the table shows Product/Variant Title, In Stock, and these seven columns. They can’t be sorted; hover a header’s ⓘ to see how it’s calculated. Column What it shows Sales Velocity Units sold per week (average of the last 4 complete weeks) and in the last complete calendar month, each with its trend, plus a chart of the last 6 months. Sell-Through Units sold ÷ (units sold + In Stock) over the last 7 days (/wk) and 30 days (/mo), each with its change in percentage points. Gross Margin (Price − Shopify Unit Cost) ÷ price, in %. Needs both a price and a unit cost. Discount Margin Your gross margin at 15% and 25% off the current price, and how many percentage points you’d lose. Hover for 5% to 50% off. Weeks to Sell How many weeks your In Stock quantity lasts at the current weekly sales rate. Capital Tied Up The value of your stock at cost: In Stock × Shopify Unit Cost. Sold Today Units sold so far today (UTC), compared with the 30-day daily average. ## Scrolling As you scroll down through the table, the column headers stay at the top of the page so you can keep track of each value. You can still sort columns or select the page’s rows from the pinned header. This works in Standard, Supply, and Sales performance modes, including views grouped by product. For wide views, use the single horizontal scrollbar. It sits under the table when the bottom is visible and floats near the bottom of the page, above the Sidekick notch, while the table continues below the screen. Drag the scrollbar or focus it and use the arrow keys, Home, or End to move sideways. The headers stay aligned with the columns as you scroll. When you reach the end of the table, the header scrolls out of view with it; the toolbar and page controls scroll normally. ## Paging The bar under the table carries the page controls: Rows per page, first / previous / next / last buttons, and the Page X of Y indicator. The indicator is a control, not a label. Click it to open a page picker, or type a page number into Go to page… and pick Go to page N to jump straight there. On a view with very many pages the list shows the first page, the last page, and the ones around where you are, rather than all of them; typing narrows it to the matching numbers. Each view also remembers the page you were last on and reopens there. Anything that changes which rows are in the table (a filter, a sort, a different page size, switching between Variants and Products) sends you back to page 1, and a page number beyond the end of the results lands you on the last page rather than an empty table. ## Show / hide columns Click the Columns button in the toolbar. A popover opens with every available column listed. Toggle visibility per column; drag rows to reorder. Your changes are staged while the popover is open; click Apply (or simply close the popover) to refresh the table once with all of them, or Reset to discard the session’s edits. At least one column always stays visible. To persist your choice, click “Save view”; the column visibility and order get saved into the active view, alongside the filters, sort, location scope, and forecast settings. See [Views & filters] (/features/forecast/views-and-filters/) for the full picture. ## Empty-cell meaning A blank cell isn’t always “no data.” Different columns use different conventions. Column type Empty cell means Reorder Date No recent sales: the model can’t pick a date. Days of Stock Either no sales history, or plenty of stock (the math overflows). Days Until Reorder Point Same as Reorder Date: no signal. Supplier columns The variant has only the [Default supplier] (/reference/glossary/#default-supplier). Assign a real one to populate. Sales metrics No sales in the chosen window. Variant overrides You haven’t set one; defaults apply elsewhere. Image The variant doesn’t have one in Shopify. Manufacturing (Assemblified) columns Empty on a row that’s neither a Bill of Materials item nor a raw material. A dash with a link to open Assemblified means it isn’t connected; a dash with a Retry button means it’s connected but the data couldn’t be reached. Tip When a cell value surprises you, hover it. Most cells have a hover card with either the underlying numbers (reorder math, MOQ progress) or the formatted full value (long descriptions, multi-line addresses). Some column headers also carry a small ⓘ icon next to the name; hover that for a plain-language explainer of what the column measures. ## See also - [Group rows by product] (/features/forecast/product-view/): show one row per product instead of one row per variant. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): the math behind the reorder columns. - [Supplier-held stock] (/features/forecast/supplier-held-stock/): the Stock at Supplier columns, explained end to end. - [Variant constants] (/features/forecast/variant-constants/): how Min / Max / Target / Static Reorder Point work. - [Views & filters] (/features/forecast/views-and-filters/): saving the column choice plus filters as a view. - [Exporting the forecast] (/features/forecast/export/): downloading what the table shows, one view or several. - [Purchase orders → Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/#virtual-materials-assemblified): the other place Assemblified’s Bill of Materials data shows up. - [Reference → Forecast column reference] (/reference/forecast-column-reference/): flat alphabetical lookup of every column. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/product-view/ # Group rows by product Switch the Forecast table between one row per variant and one row per product, with roll-up totals, product-level selection, and paging by product. By default Logistified’s Forecast table shows one row per variant. Open the display-mode menu (the Standard button in the toolbar) and choose Rows → Products, and the table instead shows one row per product, with its variants (sizes/colors) nested underneath, useful when you think in products first and only care about individual sizes when something needs attention. ## On this page - Turning it on - What a product row shows - Expanding and collapsing sizes - Selecting variants from a product row - Paging by product - Products with a lot of sizes - See also ## Turning it on The Rows choice lives in the display-mode menu: click the Standard button in the toolbar and pick one of the two options under Rows: Variants (today’s table, unchanged) or Products. The button shows a small Products or Variants badge so you can see at a glance which one the table is using. The choice is offered in the Standard and [Supply] (/features/forecast/supply-view/#product-rows) display modes; Sales Performance always shows one row per variant. When a product is open, its variant rows are lightly shaded so you can see they belong to it. Your choice is saved into the active view, the same way column visibility and filters are; see [Views & filters] (/features/forecast/views-and-filters/). ## What a product row shows A product with several variants gets one row that looks exactly like a variant row (same height, same columns) but summarizes all of its variants: - Title and variant count: the product’s title, with a line underneath such as “8 variants · 3 recommended” (or “2/8 selected” once you’ve selected some). - Recommended quantity: the combined [Reorder Forecast] (/features/forecast/reorder-suggestions/) across every variant of the product, with a smaller “X needed → Y recommended” line underneath when Logistified raised the total (for example, to meet a supplier’s product-wide minimum order quantity; see [Product-level MOQ] (/features/forecast/reorder-suggestions/#product-level-moq)). A warning icon appears next to the total when part of the product is overstocked; hover it for the detail. - Minimum-order status per supplier: a short line per supplier the product’s variants use, such as “MOQ 60 met” or “short: 40 of 60.” Products split across more than one supplier show one line per supplier. - Reorder status: in the Reorder Date column: the earliest reorder date among the product’s variants and, underneath, how many of them are out of stock or overdue (in red), due within N days (in amber) or due later, for example “1 out of stock · 2 due within 14 days · 5 later.” A collapsed product so tells you whether anything needs ordering without opening it. Each variant counts once, under its most urgent state. A variant whose inventory isn’t tracked in Shopify never counts as out of stock. N is the number in the view’s Reorder Date filter Within N Days of Reorder Point, or 14 days when the view has no such filter. For a supplier with a [product-level MOQ] (/features/forecast/reorder-suggestions/#product-level-moq), the sizes that go into an order due within N days count as due too (they complete the minimum) and “Order now” or “Order in N days” follows, naming the size that triggers the order. - Other columns: every other visible column shows a sensible summary where one exists: stock, incoming and sales quantities are summed (a “partial” note appears when a size has no value), dates such as Out of Stock show the earliest one, prices and unit costs show a range, and columns like Supplier or Vendor show the shared value or “Mixed.” Columns without a meaningful product-level summary (SKU, reorder point, safety stock, pack size, and similar) stay blank on the product row. Variants that exist on the product but fall outside your current filters still show under “outside filter” in the count, so you always see the product’s full picture. If a product’s variants aren’t all in the same [clustering] (/features/forecast/views-and-filters/) group, a small Mixed badge appears next to the title; the product still keeps the position of its first matching variant. A product with only one variant is simply a normal variant row; there is no extra product row above it. ## Expanding and collapsing sizes Products start collapsed. Click the small arrow to the left of the product’s checkbox to open it; its variants appear indented underneath, ordered by recommended quantity so the sizes that need ordering come first. Click the arrow again to collapse. Where a product’s reorder quantity was affected by a shared supplier minimum, each visible size shows a short reason next to its quantity (Due, Ahead of reorder date, Pulled forward, For product minimum, Covered, or Fixed quantity) so you can see at a glance why a particular size’s number moved. Pulled forward means the size wasn’t due yet and was ordered early to help fill the product minimum; the window that allows it is the Order soon-due variants too setting; see [Order soon-due variants too] (/features/forecast/reorder-suggestions/#order-soon-due-variants-too). ## Selecting variants from a product row The checkbox on a product row selects every variant of the product; it shows a dash when only some of them are selected, and clicking it again clears the product’s selection. To take just Logistified’s recommendation, use the Select recommended (N) link under the product’s recommended quantity: it adds the variants with a positive recommendation and keeps anything you selected by hand. Once they are all selected the link reads Recommendations selected; if you deselect one of them it offers Select remaining recommended (N). The checkbox in the table header selects or clears every variant on the current page. Whatever you select still ends up as a normal variant selection under the hood, so “Create PO from selected” and every other selection-based action work exactly as they do in Variants mode. Your selection is remembered as you move between pages and switch between Products and Variants view. ## Paging by product In Products mode, the page-size control switches to Products per page with a choice of 10 or 25 products, and pagination counts products instead of variants. The page picker and remembered page work the same as in Variants mode; see [Paging] (/features/forecast/view-table/#paging). The summary line at the bottom of the table reads something like: Products 1–10 of 42 · 118 matching variants · 142 variants shown “Matching variants” is how many variants match your current filters; “variants shown” additionally counts the outside-filter sizes kept visible for context. Once you’ve selected variants, the line adds how many are selected and across how many products. Products are ordered by the position of their first matching variant in the current sort; inside a product, sizes are listed by recommended quantity, highest first. ## Products with a lot of sizes A product with more than 60 sizes shows its row with the total variant count but can’t be expanded. Use View variants next to the count to open a page scoped to just that product’s variants, in the regular flat layout. ## See also - [Forecast view table] (/features/forecast/view-table/): every column, in either row mode. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): how Reorder Forecast and product-level MOQ are calculated. - [Views & filters] (/features/forecast/views-and-filters/): saving your row-grouping choice as part of a view. - [Supply view] (/features/forecast/supply-view/#product-rows): what a product row shows in the calendar view. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/supply-view/ # Supply view See the forecast as a calendar. Each cell shows the stock at the end of a period and the one thing to act on; hover or click for the full story. Logistified’s Supply view shows the forecast as a calendar. There is one column per week, month, or quarter. Each cell tells you at a glance how much stock a variant has left at the end of that period and whether you need to do something. Hover a cell for a quick preview, or click it for a card with the full story and the actions. On the Elevate plan, a chart above the table compares your sales plans with the forecast. ## On this page - Turning it on - Reading a period cell - Show in cells - The preview and the card - Acting from the card - The period header and the column card - The In Stock column - The sales-plan chart - Why the chart and a plan’s Analytics tab can differ - The “Show sales plans” switch - Product rows - Weeks and days - See also ## Turning it on Click the display-mode button in the toolbar (it reads Standard by default) and choose Supply. Under Time Period Settings, pick Weeks, Months, or Quarters, and set the Number of periods: up to 104 weeks, 24 months, or 8 quarters, so the calendar reaches at most two years ahead. Picking another period length resets the number to its default: 12 weeks, 6 months, or 4 quarters. The first column is the current period. It starts today, not at the start of the week or month. Next to the page title, the Forecast horizon badge shows the last day the forecast projects stock for the products on this page. When you scroll sideways, the checkbox, product, and In Stock columns stay in place, so you always know which row you’re looking at. On a narrow screen such as a phone, where they would leave no room for a period beside them, they scroll with the table instead. To make room for more periods, drag the right edge of the product or In Stock column header to make it narrower or wider. Double-click the edge to go back to the default width; with the edge focused, the ← and → keys resize it too. The widths are kept in this browser, the same for every Supply view, and aren’t part of the view. ### What the view remembers The period settings, [Show in cells] (#show-in-cells), the [Show sales plans] (#the-show-sales-plans-switch) switch, the plans you [leave out of the chart] (#choosing-which-plans-count), a [folded chart] (#hiding-the-chart), and the Rows choice all belong to the view. Like any change to a view, they show as Unsaved changes on the view button until you save the view, and each view keeps its own: switch views and the other view’s settings apply. If a change to Show in cells, the plan list, or the folded chart can’t be stored, it’s undone and Supply settings not saved appears. ## Reading a period cell Every cell has the same height and up to three lines: 1. Stock at the end of the period, in red when the variant runs out (it can go below zero, for example −20: the demand the stock can’t serve). A – means the product hasn’t launched yet: its card says No stock and no demand yet. 2. One thing to act on or expect, if there is one. See [The second line] (#the-second-line). 3. A row of small icons for whatever you chose under [Show in cells] (#show-in-cells), for example a truck when something arrives. ### Colours and symbols The colour tells you how the period goes. Most cells have no colour at all: that means the stock is fine. Look Name What it means Red, circle with a cross Stocked out The variant runs out during the period, or ends it at zero or below. Amber, circle with an exclamation mark Below safety stock On the period’s lowest day, stock is under the variant’s [safety stock] (/reference/glossary/#safety-stock), even if an arrival lifts it again before the period ends. No colour Stock OK None of the others apply. Grey number, stacked layers Excess stock The remaining stock lasts more than twice as long as the lead time and the view’s target days of supply combined. Target days count only when the view uses a fixed number. When several periods in a row share a state, only the first one gets the symbol and the full colour. The following periods keep a faint tint, so a long stock-out reads as one stretch rather than a wall of red. Excess stock only shows once a variant has a lead time. It’s grey on purpose: with short lead times, many healthy cells are excess, and they shouldn’t shout. Falling under the [reorder point] (/reference/glossary/#reorder-point) doesn’t colour the cell. The order chip on the second line tells you when to order instead. ### The second line The second line shows at most one thing. When several apply, it picks the first of these: Line What it means A cart and a quantity, for example 40 (red chip) The reorder date has already passed: order now. Shown in the current period only. A cart and a quantity (amber chip) The variant reaches its reorder point in this period. The quantity is the recommended order, rounded to the supplier’s minimum order and pack size like the Standard view. See [Reorder suggestions] (/features/forecast/reorder-suggestions/). +N late (amber) A purchase order, transfer, or manufacturing order should already have arrived and hasn’t. +N day (blue) Stock arrives in this period: +40 Thu in week columns, +40 · 12 Nov in month columns, or +90 · 2 docs when more than one document arrives. No demand (grey) The stock is below zero, but nothing in the period asks for more: no demand, no planned outflow, no lost sales. The cell still counts as stocked out, because those units have to come in before you can sell one. ≈ $420 lost (red) The sales you lose while out of stock, at the variant’s selling price. From 1,000 the amount is rounded to thousands (≈ $16K lost), from a million to millions (≈ $1.2M lost). Without a price, it counts units instead: ≈ 12 units lost. A period column is too narrow for a whole order sentence, so the order chips show only the quantity (from 10,000 shortened, for example 12.5k). The [preview] (#hovering-a-quick-preview) spells it out, for example Order 40 by 12 Nov or Order 40 now · 5 d late, and screen readers hear the whole sentence. Arrivals are placed on the date you asked the supplier for, when there is one, otherwise on the expected date. A document whose date has passed counts from tomorrow and shows as late. A document without a date is placed one lead time from today. ## Show in cells The third line is up to you. Open the display-mode menu (the Supply button) and find Show in cells. For each item pick Off, Icon, or Value: Item Shows Default Arrivals (PO, transfer, MO) Something arrives in this period, with its units as a value (+40). Icon Planned outflow Stock promised through Inventory Planning leaves in this period, such as an inventory commitment or a launch allocation (−12). Only plans that feed the forecast count: Confirmed and Locked commitments, and launch plans with Feed into forecast on. Sales plans never do. Icon Demand forecast The forecast sales in the period (−38). Off Cover at period end How long the end stock lasts at the forecast rate (3.5 w). Not shown in a stocked-out period. Off Sales plan A sales plan covers this period. As a value: the forecast as a share of the target (92%). Off Product launch A new-product plan launches in this period. Icon Draft PO A draft purchase order already exists for the variant. Shown in the current period. As a value: the units on draft purchase orders. Icon Show everything shows every item, as a value where it has one (launches and draft POs stay icons); Reset to default goes back to the table above. The choice is saved with the view. The icon row never repeats the second line: if the second line already says +40 Thu, the arrival icon isn’t shown again. When more items apply than fit, the row ends with +2. How to read the cover: - A cover starting with >, for example > 56 d or > 8 w, means the stock lasts at least that long: no stock-out before the forecast ends. - > 26 w is the most the cell shows. - Week columns count in days up to 70 days, then in weeks. Month and quarter columns count in weeks. Anything under a week is in days. ## The preview and the card ### Hovering: a quick preview Rest the pointer on a cell for a moment and a small preview grows out of it. At the top: the variant, the period, the state, and Click for details. Below them: - One line on what to do, for example Order 40 by 12 Nov, Order 40 now · 5 d late, Below safety stock from 10 Nov · 3 at lowest, or Covered · 6 w at period end. - Up to seven small bars: the lowest stock of each day in a week, each week in a month, or each month in a quarter, red below zero and amber below safety stock, with the arrivals above them. - Two short lists: what comes in and goes out (incoming, demand, planned outflow), and any sales plans, launches, events, or growth amplifier. Moving quickly across the table opens nothing; once a preview is open, the next one follows as you move. The preview never gets in your way: you can click straight through it. On a touch screen there’s no preview; tap a cell to open its card. ### Clicking: the card Click a cell (or press Enter or Space on it) to open its card. The card sits just under the column headers and grows downward. Its header shows the product and variant, the state, the end stock, the period with its dates, the SKU, and the supplier. Under the chart, the card has two columns. On the left: Inventory movements, Inventory effects and Inventory documents. On the right: Plans & launches and Replenishment & risk. The buttons are at the bottom and stay in view while you scroll a tall card. On a narrow screen the two columns stack. #### The chart The chart shows the stock day by day. The line can go below zero: that’s demand the stock can’t serve, and that part is drawn in red. When nothing is forecast to sell in the period, the line stays flat and steps up on the day something arrives. “No daily projection for this period” means there’s nothing to draw at all. The chart is built in rows, so no label ever sits on top of another: - Effects, at the top. A blue bar with a ★ marks the days of a [promotional event] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast), for example ★ Cyber Week. A green bar with a ↗ marks the days of the view’s [growth amplifier] (/features/forecast/growth-amplifiers/), for example ↗ +30% amplifier. A bar that is too short for its name shows the start of the name, or only the ★ or ↗. The same days get a faint tint in the chart below. - Dashed lines for your stock levels. The [safety stock] (/reference/glossary/#safety-stock) and the [reorder point] (/reference/glossary/#reorder-point), labelled for example Safety stock 12 and Reorder point 30, plus the Min Inventory, Max Inventory, Target Inventory, and Static Reorder Point you set for the variant (see [Variant constants] (/features/forecast/variant-constants/)), labelled Min, Max, Target, and Reorder. Those four only show when they’re set above zero. Each label sits on its own line at the right end of the chart, so the chart uses its full width; levels with the same value share one label, for example Safety · Reorder 0. When space is tight, the names are shortened to SS, ROP, Min, Max, and Tgt. - Arrivals and outflows, under the chart. +120 in blue for stock arriving and −40 in orange for stock promised through Inventory Planning, under the day it happens. In month and quarter columns they’re added up per week. - The days, at the bottom. Weekday names in a week, dates in a month or quarter. Point at a day for a small tooltip: the date, the stock at the end of that day, what arrives and what goes out, the demand forecast, Out of stock when the stock runs out, and the events and amplifier active that day. The tooltip only opens with a mouse or trackpad pointer; screen readers get a short written summary of the chart instead. #### The Sales plan tab When a sales plan has a target in the period, two tabs sit above the chart: Inventory and Sales plan. Sales plan shows one bar group per day of the period: - the target as an outline, - what has sold, filled, for past days and today, - the forecast, lighter, for the days still to come. Above the bars: Target, Sold so far (only in the current period; later periods show a dash and (future week)), Forecast landing, and the share of the target. The current period’s days start on Monday (or the 1st of the month), so you also see what sold earlier in the week. Sold and forecast count only on the days a plan runs, the same as the [sales-plan chart] (#the-sales-plan-chart). The card remembers the tab while you step through periods; a period without a plan shows Inventory. With a tab focused, ← and → switch between the two tabs instead of stepping periods. #### Inventory movements Stock at start (the end of the previous period, or today’s stock for the current period), Incoming, Demand forecast (marked incl. events / amplifier when a promotional event or growth amplifier lifts it), Planned outflow, and Stock at end. Planned outflow names what it’s made of: (incl. commitments), (incl. launches), or (incl. commitments, launches). When these lines don’t add up to the end stock exactly, an Other changes line shows the difference. #### Plans & launches - Each sales plan covering the variant in this period, with what it expects this week (or month, or quarter) and a link to its Analytics tab. Plans you left out of this view are listed in grey as not counted in this view. - Target (this week), with · 2 plans when more than one plan counts, Sold so far (only in the current period; later periods show a dash and (future week)), and Forecast landing, with a bar and the share of the target. ⚠ stock and Sellable from stock appear when stock can’t serve the forecast, with a line such as Stock can’t serve about 10 units. - Launches from new-product plans that run in this period, with a link to the plan and its day (launched 12 Oct, launches today, launches 20 Oct). Before the launch: how many are expected this week. After it: sold 12 of 30 expected since launch, counted up to yesterday, or No sales expected yet while the plan expects none so far. One bar at the bottom of the section adds up all launches: Launches so far: sold 20 of 45 expected. With Global demand on, the sold units are your whole shop’s: sold 12 (shop-wide) of 30 expected since launch. A launch plan that no longer feeds the forecast shows no progress here. Forecast landing is what you’re expected to sell in the period. For the current period, that’s what has sold so far plus the forecast from tomorrow to the end of the period; the rest of today isn’t counted. For later periods, it’s the forecast. Target and landing cover only the days the plan runs. #### Inventory effects The [promotional events] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast) and the growth amplifier on this period, with their days: for example Cyber Week +30 % applied here · Thu–Sun or Growth amplifier +30% · all week. An event that doesn’t apply to this variant says not applied for this variant. The section is hidden when nothing applies. #### Replenishment & risk This part tells you whether to act. It opens with one verdict: Verdict When Act now An order is overdue or due in this period, the variant runs out while customers still want it, or it runs out before the next delivery arrives. Watch Stock falls below safety stock, a delivery is late, there is excess stock, the variant runs out again within its lead time after this period, or the stock is at or below zero with no demand asking for it. Fine Nothing to act on, for example Covered · 6 w at period end or Nothing to act on this week. Below the verdict, the signals that apply, most urgent first: - Reorder: why the verdict asks for the order, Reorder date passed 5 d ago or Reorder date 12 Nov (in 9 d); the quantity is in the verdict (Order 40 now, Order 40 by 12 Nov). Like the Standard view, the days since the reorder date stop counting at the variant’s lead time. - Stock-out: Out from 14 Nov, or Out since 10 Nov when the stock-out started in an earlier period, or Out now. Below it, the demand you can’t serve and on how many days (12 units of demand unmet on 3 days), the sales lost at the variant’s price, and the delivery it runs out before, for example before PO-1042 arrives 20 Nov. - Late incoming: PO-1042 late (expected 12 Nov) · 60 units, two documents at most, then +1 more. - Below safety stock: From 10 Nov · lowest 3. - Excess: Cover 20 w at period end, above the 80 d excess line. Point at it to see how the line is worked out. - Next stock-out: Runs out 3 Dec, when this period is fine but the stock runs out later. The last line lists Cover at end, Safety stock, Reorder point, Lead time, MOQ, and Pack. #### Inventory documents Folded by default, with a count: Inventory documents (3). Click it to see each purchase order, transfer, or manufacturing order arriving in the period, with its units, status, date, a late mark (late, expected 12 Nov), and a link, and each plan taking stock out, with its plan number (a link to the plan), its units in this period, its status (or, for example, Confirmed · 3 locations), and the day it starts. The card keeps it open while you step. The buttons come last, see [Acting from the card] (#acting-from-the-card). ### Stepping through weeks and rows With a card open, you can walk the table without closing it: - ‹ › at the top right, or the ← and → keys, move to the previous or next period. - ↑ ↓ at the top left, or the ↑ and ↓ keys, move to the row above or below, in the order the table shows them, including the variants of an open product. - The table scrolls under the card so the period you’re on stays in the middle and the row stays just below the headers. Its period header and row are highlighted. - ✕, the Esc key, a click outside the card, or a click on the same cell again closes it. Closing it with ✕ or Esc puts the keyboard focus back on the cell. You can also use the keyboard without a mouse: Tab into the table, move between cells with the arrow keys, and press Enter or Space to open a card. Tab also reaches the period headers: ← and → move along them, and Enter or Space opens the [column card] (#the-period-header-and-the-column-card). ## Acting from the card The bottom of a variant’s card has these buttons, with the variant’s supplier at the right (Supplier: name): - Create PO: opens the Create Purchase Order dialog with this variant. In a period that asks for an order, the button shows the quantity the card shows, for example Create PO for 40, and the dialog takes that quantity; otherwise it reads Create PO and uses the variant’s usual recommended quantity. See [Create a PO from the forecast] (/features/forecast/create-po-from-forecast/). - Add to draft PO: shown when a draft purchase order already contains the variant. With one draft it names it, for example Add to draft PO PO-1042, and opens the Add to Purchase Order dialog with that draft picked. With several drafts, pick one from the list, which shows each draft’s expected date. - Create transfer: opens Create Transfer Order from Forecast with this view already picked. This needs a saved view: while the view has unsaved changes, the button is greyed out with Save the view to create a transfer from it. See [The forecast creation flow] (/features/supply-orders/transfer-orders/creating/#the-forecast-creation-flow). Clicking a button closes the card. When you close the dialog, the keyboard focus goes back to the cell you started from. A purchase order you create this way records the view you started from, even if you switch to another view while the dialog is open. ## The period header and the column card The header of each period column shows its label and dates, for example KW42 with 12.10 - 18.10. A third row under the dates holds up to two badges: - A green ↗ +20% chip shows the view’s [growth amplifier] (/features/forecast/growth-amplifiers/) on this period. When amplifiers overlap, it shows the largest combined boost on any day of the period. - A blue ★ 2 badge counts the [promotional events] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast) that raise the forecast in this period; the header is also tinted blue, with a blue bar along its top. When none of the period’s events is applied in this view, a grey ☆ 1 badge counts them instead. Point at the badge to read the events, for example Black Friday +40 % applied here or Black Friday +40 % off in this view. Hover the rest of the header for a preview of the whole period: how many variants on this page are out, below safety stock, OK, or excess, the orders due, the arrivals, the sales plans, and the events. It ends with Click for the period’s details and Drag across weeks to apply a growth amplifier. Click a header (or press Enter or Space on it) to open the column card for that period. Its header reads, for example, All 24 variants on this page: it covers every variant on this page that matches your filters. - The top: the state counts as a bar, and the total stock of all variants day by day. - Inventory movements: the totals for the period, any unmet demand, each arriving document with its day and how many variants it brings, and each plan taking stock out. - Plans & launches: the counted sales plans as one total (Sold, Forecast, Plan), each plan with its target and number of variants, a note when variants are in more than one plan, launches, each event with its boost, days, and how many variants it lifts (for example Black Friday +40 % · Thu–Sun · lifts 10 of 12 variants), the growth amplifier, and a Growth amplifier for this period button. - Replenishment & risk: lists of the variants that need you: Order, Out of stock (with the lost sales), Below safety stock, and Runs out before an arrival. Click a variant to open its own card. Long lists show eight entries and Show all N. - Create POs for N variants opens the purchase order dialog with every variant that needs ordering, at its order quantity, split by supplier. Step through periods with ‹ › or ← and →, and close with ✕ or Esc. When you close a dialog you opened from the column card, the keyboard focus goes back to the period header. To set a growth amplifier for a stretch of time, press on a period header and drag across the periods you want. When you let go, the Apply Growth Amplifier dialog opens with those dates. Esc cancels the drag. ## The In Stock column In the Supply view, the In Stock column shows two plain lines: - N available: the stock you have now (below zero it reads, for example, −371 available). - +N incoming, with · N late when part of it is overdue, or nothing incoming. It doesn’t use colours, the bar, or the icons of the Standard view. Hover it for the same breakdown as in the Standard view. When plans take stock out, that breakdown has a Planned outflow tile with the total and how many plans contribute, and one row per plan with its plan number, its status (or, for example, Confirmed · 3 locations), its start date, and what it still takes from tomorrow on. A plan with nothing left to take, such as one dated today, isn’t listed. To see what a plan takes out in one period, open that period’s card: Inventory documents lists each plan with its units in the period. A product row shows the two lines added up over its variants, without a hover. ## The sales-plan chart On the Elevate plan, a chart titled Sales plans sits above the Supply table. Under each period column it shows three bars on one scale: - Sold (green): what has sold so far. Only the current period has it; later periods show –. - Forecast (hatched green): where the period is expected to land, sales so far plus the forecast for the remaining days. An amber tick across it marks how much of that your stock can actually serve. - Plan (violet): the target of the plans you count. Above the bars, a chip shows the forecast as a share of the plan, with ▲ or ▼ for above or below the target: - green at 90% or more, - amber from 70% to 89%, - red below 70%. low vol. instead means fewer than 10 units are expected in the period, too few to rate. ⚠ stock next to the chip means the forecast would get there, but stock can’t: what you can sell from stock lands the plan in a lower colour band. The numbers under the bars are the three values in units. no plan over a dashed line means no sales plan covers that period for the products on this page. The same colours are used in each plan’s [Analytics tab] (/features/inventory-planning/plan-analytics/). Hover the bars, or move to them with Tab, for the numbers: Plan target, Sold so far (current period), Remaining forecast, Forecast landing, and Sellable from stock with Stock can’t serve about N units. when stock falls short. The card also lists the promotional events and the plans in that period, each plan linked to its Analytics tab. A period no plan covers says No sales plan covers this period on this page. ### How plans are counted Click the ⓘ next to Sales plans for the rules: - Plan adds up the targets of every counted plan in the period. A product in two plans adds both targets. - Sold and Forecast count each product once, on the days any counted plan covers, however many plans it is in. - Only Confirmed and Locked plans, only the products on this page, and only the locations of this view count. Two plans for the same product, location and dates (for example a revised plan next to the old one) double the target and halve the percentage. Leave one of them out with the plan list below. The ⓘ also tells you when the chart’s numbers can differ from a plan’s Analytics tab, without changing any number: - Includes sales at locations without a plan: you’re looking at all locations and at least one plan on the page doesn’t cover every location. The chart counts sales and forecast at all locations, but a plan’s Analytics tab only counts its own locations. - Forecast and actuals are shop-wide; targets are for the selected locations: you picked locations and turned on Global demand in the location picker. See [Locations] (/features/forecast/locations/). ### Choosing which plans count The button next to Sales plans reads All 3 plans, or 2 of 3 plans (in violet) when you’ve left some out. Click it for Plans in the strip: each plan covering these periods, with how many variants it has on this page and a link to its Analytics tab. Untick a plan to leave it out; Select all counts them all again. The last ticked plan can’t be unticked. Leaving a plan out changes the chart, the column card’s plan total, and the totals in each card. A variant’s own card still lists every plan, with the ones left out in grey. The choice is saved with the view, and a plan you create later counts until you untick it. ### What the chart counts - Confirmed and Locked sales plans only. Draft, Completed, and Cancelled plans don’t appear. - The current page only. It adds up the variants on this page that have a target in the period. It follows your filters, the location you picked, and the page you’re on, so the next page shows different numbers. Variants shown only for context (marked “outside filter”) don’t count. - Units only. For revenue, open the plan’s Analytics tab. - Forward only. The chart starts at the current period. It doesn’t show how a plan has done so far. For that, use the plan’s [Analytics tab] (/features/inventory-planning/plan-analytics/). ### Hiding the chart The chart is open by default. Click the arrow next to Sales plans to fold it into one line. Click Show sales-plan chart to bring it back. The view remembers your choice. ### When the chart has nothing to show Message What it means “No confirmed sales plans cover the products on this page.” None of the variants on this page is in a Confirmed or Locked sales plan for the periods shown. The Sales Plans link opens your plans. “Sales plans are hidden in this view. Turn on Show sales plans in the Supply menu above the table.” The switch is off for this view. See [The “Show sales plans” switch] (#the-show-sales-plans-switch). “Loading sales plans…” You just turned the switch on, and the view is reloading. ## Why the chart and a plan’s Analytics tab can differ Both compare a plan with sales, but they answer different questions: - The chart asks: “Are we going to reach the plan?” It compares the target with sales so far plus the forecast for the remaining days. - The Analytics tab asks: “How far along is the plan today?” It compares the target with what has actually sold. Its On track for tile projects from recent sales, not from the forecast. So the numbers can differ, for these reasons: Sales-plan chart Plan’s Analytics tab Which plans Every Confirmed or Locked plan covering the page that you count, added together One plan Which products The variants on this forecast page All of the plan’s variants, or the ones you pick Which periods The current period and later From the plan’s start to today, and the whole plan What it compares with Sales so far + forecast Sales to date On All locations Sales at every location Sales at the plan’s locations only Units or revenue Units Units or revenue ## The “Show sales plans” switch Each Supply view can show or hide sales plans. Open the display-mode menu (the Supply button) and use the Show sales plans switch: “Shows the sales-plan chart above the table and plan totals in the cards”. - Off: the chart says sales plans are hidden, and the cards drop the plan totals. - On: the view reloads with the plan targets. The switch doesn’t change the forecast. Sales plans are goals, not demand, so no forecast or reorder number moves either way. The setting is saved with the view. The switch is part of the Elevate plan, like Sales Plans. See [Subscription plans] (/reference/subscription-plans/). ## Product rows The Supply view can also show one row per product. In the display-mode menu, choose Rows → Products. The button then reads Supply with a Products badge. Paging, expanding, and selecting work as described in [Group rows by product] (/features/forecast/product-view/). A product’s period cell sums up its sizes: - Stock: the total across sizes, with the symbol of the most urgent state any size has. The number only takes that state’s colour when every size shares it, so one empty size doesn’t turn a healthy total red. It turns red only when every size is out. - Second line: when a size is out or below safety stock, how many: 1/3 out or 2/5 low, out of all the product’s sizes (including sizes outside your filter). Otherwise the sizes’ order chip: a cart and the quantity the sizes add up to, red when an order is overdue. The preview says it in full, for example 2 of 5 variants reach their reorder point · order 80 units. - Icons: the same Show in cells choices, added up over the sizes. The cover is the first size to run out, for example S · 3 w, or first 3 w for longer size names. Click a product cell for the product card: the same chart (without the dashed stock levels and the Sales plan tab), Inventory movements, Plans & launches, Inventory effects, and Inventory documents, with the sizes added up. Its Replenishment & risk part has one line on what matters instead of a verdict (for example 2 of 5 variants out · M, L), how many sizes are in each state, First size to run out and Longest stock-out, the demand that can’t be served, and the sizes that need you (Order 40 · late, Out 7 d, Out now, Order 40, Below safety stock). The product card has no buttons: click a size to open its own card and order from there; a closed product opens for it. Products with many sizes. A product with more than 60 sizes shows blank period cells and too many to show · View variants. Click View variants to open just that product’s variants, one row each. These products are also left out of the sales-plan chart in Products mode. Switch to Rows → Variants to include them. A cell showing - couldn’t add up every size, so it shows no total rather than a partial one. ## Weeks and days - Weeks run Monday to Sunday and are labelled with their week number, for example KW42. Around New Year a week can be KW53. - Days change at midnight UTC, the same as in plan Analytics. In New York, for example, that is 8 pm in summer. - Planned outflow counts from tomorrow, the same as the forecast and the In Stock hover: a plan dated today counts 0. - The page keeps the same “today” until you reload it. If you leave it open overnight, reload to move on to the new day. ## See also - [Forecast view table] (/features/forecast/view-table/): the Standard view’s columns. - [Group rows by product] (/features/forecast/product-view/): product rows, paging, and selection. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): where the Order quantity comes from. - [Growth amplifiers] (/features/forecast/growth-amplifiers/): the boost behind the header’s ↗ +20% chip. - [Promotional events in the forecast] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast): the events behind the ★ badges and the event bars. - [Create a PO from the forecast] (/features/forecast/create-po-from-forecast/): the dialog behind Create PO. - [Locations & multi-location math] (/features/forecast/locations/): location scope and Global demand. - [Sales Plans] (/features/inventory-planning/sales-plans/overview/): the targets the sales-plan chart shows. - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): what each plan type adds to the forecast. - [Plan analytics] (/features/inventory-planning/plan-analytics/): how a sales plan has done so far. - [Exporting the forecast] (/features/forecast/export/): Supply views export their period columns. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/forecast-models/ # Forecast models The forecast models Logistified offers, how to start, and how model choice flows into reorder math. Logistified offers a handful of forecast models. New views start with Average, a simple, predictable model that’s easy to sanity-check. [Auto] (/reference/glossary/#auto-model-selection) is available when you want Logistified to pick the best model per variant automatically. This page lists the models, gives starter advice for choosing one, and explains what changes when you switch. ## On this page - The models at a glance - How to choose: start simple, then turn on Auto - No per-variant model picker - Tuning is automatic - Cold-start behavior - What changes when you switch - See also ## The models at a glance Model When it’s a good fit Plan [Auto] (/reference/glossary/#auto-model-selection) You don’t know; let Logistified pick the best model per variant. Essential [Average] (/reference/glossary/#average-model) Flat, predictable demand with no trend. Default. Essential [Moving average] (/reference/glossary/#moving-average-model) Smooth slow drifts; reduces random noise. Essential [Weighted recent] (/reference/glossary/#weighted-recent-model) Recent days dominate; recent change matters more. Essential [Exponential smoothing] (/reference/glossary/#exponential-smoothing-model) Weighted recent with a smoother decay curve. Essential [Holt (Double exponential smoothing)] (/reference/glossary/#holt-model) Smoothing plus a trend component. Manual pick only for now; Auto isn’t currently choosing it. Enhanced [Linear regression] (/reference/glossary/#linear-regression-model) Clear up- or down-trend. Essential [Seasonal] (/reference/glossary/#seasonal-model) Repeating short-cycle patterns, weekly or monthly. Manual pick only for now; Auto isn’t currently choosing it. Enhanced [Mixed] (/reference/glossary/#mixed-model) Blend of multiple models. Essential History replay Repeats the view’s history window as-is instead of fitting a curve; with a 365-day window, tomorrow is forecast as the same date last year; shorter windows keep the weekday alignment. Good for “next month should look like the same month last year.” Manual pick only; Auto never selects it. [Growth amplifiers] (/features/forecast/growth-amplifiers/) stack on top of it. Essential Caution Holt and Seasonal are temporarily out of automatic selection. While we retune them, Auto won’t choose either one; a variant already using one keeps it until its next re-check, and you can still select either by hand at the view level. See [Automatic model optimization] (/features/forecast/automatic-model-optimization/#what-auto-doesnt-do). [anchor: how-to-choose--start-simple-then-turn-on-auto] ## How to choose: start simple, then turn on Auto Don’t start with the most complicated model. Start with Average (or Moving average). Look at the suggestions for your top variants. Once they roughly match your gut on a chunk of the catalog, switch to Auto and watch how the demand forecast changes; Auto will usually do better than your manual pick, but you’ll trust it because you’ve already validated the simple case. The same advice for the history period: start with a fixed 90-day manual window. See [History period] (/features/forecast/history-period/). ## No per-variant model picker You won’t find a model dropdown on the variant detail page; that UI doesn’t exist. Auto already adapts the model per variant automatically based on each variant’s history shape. If you want different model behavior for a subset of variants, create a separate [view] (/features/forecast/views-and-filters/) scoped to those variants and set the model at the view level. Views are how model + history-period choices are scoped in Logistified. ## Tuning is automatic Smoothing factors, window lengths, seasonality cycle lengths are all tuned internally per variant. There are no operator-facing knobs. The variant detail page shows the ranked models with their internally-chosen parameters as a read-only diagnostic, not an editor. ## Cold-start behavior Variants with very little history fall back to [Average] (/reference/glossary/#average-model) until enough data accumulates. Specifically: - Empty history (no sales at all): the system uses Persistence as a “tomorrow looks like today” sentinel until the first sale lands. - Less than ~7 days of history: Average. - Less than ~30 days: Moving average or Average, depending on signal. Auto won’t pick a more sophisticated model until enough data is available, by design. Overriding at the view level on a thin-history variant tends to produce noisy suggestions. ## What changes when you switch Switching the model at the view level re-runs the day-by-day inventory simulation for the variants in that view. After the simulation: - The reorder point. - Days until reorder. - The reorder date. - The reorder quantity. - Days of stock. …all update. The recompute is fast, usually within a minute of saving the view. Tip Beginners often pick the most complicated model first. Resist. Start with Average and a fixed 90-day history; once the suggestions match your intuition, switch to Auto. Auto will usually do better, but you’ll trust it because you’ve already validated the simple case. ## See also - [Automatic model optimization] (/features/forecast/automatic-model-optimization/): what Auto does and when it runs. - [History period] (/features/forecast/history-period/): the second big lever in forecast settings. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): how the model’s output flows into the suggestion. - [Views & filters] (/features/forecast/views-and-filters/): how model + history-period choices are scoped. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/forecast/automatic-model-optimization/ # Automatic model optimization How Auto picks the best forecast model per variant, and when it runs. In Logistified, [Auto] (/reference/glossary/#auto-model-selection) picks the best forecast model per variant by comparing how well each model would have predicted the recent past, and refreshes that choice whenever new data shows up. ## On this page - What Auto does - When it runs - What Auto doesn’t do - Triggering manually - See also ## What Auto does For every variant, Auto: 1. Looks at the order-history shape: length, trend, seasonality, variance. 2. Runs every applicable model against the history. 3. Scores each model by how well it would have predicted the recent past (the held-out validation window). 4. Picks the winner and uses it for that variant’s forecast. The result is one model per variant, refreshed as new data arrives. ## When it runs Auto re-checks a variant whenever its inventory or orders change in a way that could shift the optimal model, typically within minutes of the event. New sales, received inventory, and PO updates all count. It also runs: - Once after the initial data sync on install. - On demand, when you re-trigger it manually from Settings → ABC Analysis. You don’t need to think about cadence; Auto follows the data. ## What Auto doesn’t do - It can’t see future events. Use [growth amplifiers] (/features/forecast/growth-amplifiers/) to tell the forecast about campaigns or launches that don’t appear in history. - It doesn’t expose per-variant tuning knobs. Smoothing factors, window lengths, seasonality lengths are all internal. See [Forecast models] (/features/forecast/forecast-models/#tuning-is-automatic). - It doesn’t replace your judgement on outliers. If you know a one-off spike (a viral moment, a press mention) won’t repeat, an amplifier or a manual exclusion is the right tool. - It doesn’t consider every model. Some models are manual-pick only; see the Aside below. Caution Auto is not currently choosing Holt or Seasonal. Both models are temporarily out of the automatic comparison while we retune them, so Auto will pick something else for a steady seller even if one of them would have scored well. A variant that Auto had already settled on Holt or Seasonal keeps using it until the next time that variant is re-checked, at which point it moves to the best of the remaining models. You can still pick either model by hand at the view level, and [History replay] (/features/forecast/forecast-models/) has always been manual-pick only. ## Triggering manually The only manual entry point: Settings → ABC Analysis → re-run model optimization. Useful after a long stretch where many variants have accumulated meaningful new history at once. Note If Auto disagrees with your intuition for many variants, look at the data before pushing back. Auto sees patterns in history you might not; a variant that looks flat to the eye can have a subtle weekly cycle the model picks up. ## See also - [Forecast models] (/features/forecast/forecast-models/): the models Auto chooses from. - [Variant detail] (/features/forecast/variant-detail/): where the model ranking is shown per variant (read-only). - [Views & filters] (/features/forecast/views-and-filters/): how model choice is scoped (at the view level, not per variant). Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/history-period/ # History period Auto vs. Manual history windows and which to start with as a beginner. The [history period] (/reference/glossary/#history-period) is the window of past sales the forecast looks at. It’s either Auto (Logistified picks the optimal window per variant) or Manual (you pick a fixed range). New views default to Manual + Last 90 days combined with the Average model, the best starting point for new operators because everything going into the forecast is visible and easy to sanity-check. ## On this page - Auto vs. Manual - Manual presets - Rolling (Past Year + Lead Time) - Rolling vs fixed window - Excluding stock-out periods - Why Average + Manual + 90 days is the default - The recommended starter setup - See also ## Auto vs. Manual Auto Manual Logistified picks the optimal window per variant. You pick a fixed range, applied to every variant in the view. The model gets the data it needs. The math is fully predictable; you see what’s going into it. Magic: hidden choice. Transparent: visible choice. Best once you trust the system. Best while you’re learning. ## Manual presets When you switch to Manual, you can pick from these presets or define a custom date range on the calendar: Preset What it does Last 7 days One-week window. Useful for fast-moving, high-volume variants. Last 30 days One-month window. Useful for monthly cycles. Last 60 days Two-month window. Last 90 days Three-month window. The recommended beginner default. Last 6 months Half-year window. Last year 365-day window. Useful when seasonality matters. Max Everything Logistified has on this variant. Rolling (Past Year + Lead Time) Past 365 days of history matched against the supplier’s lead-time window projected forward. The seasonal-planning preset. Beyond these presets you can also pick a custom start/end on the calendar. ## Rolling (Past Year + Lead Time) The one “smart” preset on the list. Its job is to align what you sold a year ago with the lead-time window you’re about to order for. Mechanics: - The history window is the past 365 days, ending today. - The forecast horizon is your supplier’s lead time projected forward from today. - As days pass, both windows roll forward together, so the comparison stays current. Pick this preset when seasonality matters and your supplier lead time is meaningful (weeks or longer). For shorter lead times or non-seasonal variants, a fixed window like Last 90 days is usually clearer. ## Rolling vs fixed window A rolling window slides forward each day. “Last 90 days” always means the 90 days ending today, recomputed daily. The alternative is a fixed date range with start and end pinned to calendar dates, never moving. Use a rolling window when you want a consistent recency. Use a fixed range when you want to lock the math to a specific period (for example, “compare to Q4 last year”). ## Excluding stock-out periods Days when an item had no stock make its sales look lower than real demand. Turn on Stock-out detection in the history settings to have Logistified remove those stretches from the history before forecasting. Consecutive zero-sales days sets the shortest stretch that can count as a stock-out. Once it’s on, Stretches to exclude chooses which stretches are removed: - Every long zero-sales stretch: the original rule. Every stretch of at least the set number of zero-sales days is removed, including the stretch before the first sale and after the last one. For slow sellers this can remove ordinary quiet periods. - Only stretches unusual for the item: a stretch between sales is removed only when it is unusually long for how often this item sells. A stretch running up to today is removed once the item has at least five past sales days, while it is out of stock everywhere in the view’s locations and cannot be back-ordered. New views use this rule. Existing views keep the original rule until you change it. The setting is in Forecast Settings and in the guided view wizard’s history step. ## Why Average + Manual + 90 days is the default Two reasons: - No hidden parameters. The Average model is “sum sales ÷ days.” That’s it. Nothing magical adjusts the result behind the scenes. - A meaningful window. 90 days usually covers more than one sales pattern (you’ll see the recency of last month plus the rolling history from the two before), but isn’t so old it includes obsolete trends. Once the suggestions match your intuition for 80% of variants, switch to Auto. Auto will do better than your manual picks on most variants, but you’ll trust it because you’ve already tested the simple case. ## The recommended starter setup 1. Open the Forecast page; the default view already uses Average + Last 90 days, so nothing to change. 2. Add reorder columns (Reorder Point, Reorder Date, Reorder Forecast) via the Columns popover. 3. Save as a view named “Beginner: Average 90 d.” 4. Once the suggestions feel right, switch Model to Auto to let Logistified optimize per variant. Tip Logistified shows a warning when you pick a very long history period combined with a large catalog; the math takes longer. If you see the warning, narrow the view first (for example, filter by vendor or supplier). ## See also - [Forecast models] (/features/forecast/forecast-models/): the other big lever in forecast settings. - [Automatic model optimization] (/features/forecast/automatic-model-optimization/): the Auto side of model picking. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): how history feeds reorder math. Last updated: 19 May 2026 --- Source: https://docs.logistified.app/features/forecast/locations/ # Locations & multi-location math How single-location vs. all-locations filters change the forecast math. When you have one location, Logistified’s forecast math is simple: one variant, one set of numbers. When you have multiple locations, the location picker in the toolbar changes how the simulation runs across two independent axes. This page explains both. ## On this page - The two axes: inventory scope and demand scope - Picking a single (or subset of) location(s) - The Global demand toggle - Variant overrides per location - What stays the same - See also [anchor: the-two-axes--inventory-scope-and-demand-scope] ## The two axes: inventory scope and demand scope The location picker has two settings that work together: - Inventory scope: which locations’ on-hand and incoming feed the simulation. Default: all locations. - Demand scope: which locations’ sales history feeds the forecast model. Default: matches inventory scope. By default, both axes move together. When you select one location, both inventory and demand are scoped to it. The Global demand toggle (below) decouples the two, useful for warehouse setups where one location physically holds stock for demand that originated elsewhere. ## Picking a single (or subset of) location(s) Use the location dropdown in the toolbar and check the location(s) you want. The page recomputes within a second or two. Things that change: - In Stock: sums the available quantity at the selected location(s) (Shopify’s available bucket: on-hand minus committed). When all locations are selected, the column reverts to the variant’s on-hand across everywhere. - Incoming columns: only count POs and TOs heading to the selected location(s). - Reorder Point, Reorder Date, Reorder Quantity: the simulation runs against the selected-location subset. - Days of Stock: same simulation, scoped to the selection. - Sales / demand: by default, also scoped to the selected location(s)’ order history. Flip Global demand on if you want demand to stay global. ## The Global demand toggle Inside the location picker (visible only when you’ve filtered to fewer than all locations), there’s a Global demand switch. - Off (default): both inventory and demand are scoped to the selected location(s). Forecasts are local to those locations’ sales history. - On: inventory stays scoped to the selected location(s), but demand and sales data are pulled from all locations. Useful when one warehouse fulfills orders generated across regions you logically share; the demand signal lives at the catalog level, not the warehouse level. ## Variant overrides per location Min / Max / Target / Static Reorder Point can be configured per location. With All locations selected, Logistified shows the smallest value across locations, useful for spotting the bottleneck. With a single location selected, it shows the value configured for that location specifically. To set per-location overrides, go to Settings → Products → Variant Constants. ## What stays the same Regardless of the location filter: - The choice of forecast model and the supplier-link inputs (lead time, MOQ, pack size, cost) don’t change per location. - Variant-constant cross-field validation rules (Min ≤ ROP ≤ Target ≤ Max) apply per location. What does change: which sales history feeds the model, unless you flip Global demand on, in which case demand stays global while inventory becomes per-location. Note Two operators looking at the same shop but different location filters can see different reorder suggestions for the same variant. That’s expected; they’re answering different planning questions (“what does each location need?” vs. “what does the shop need?”). ## See also - [Inventory → Locations] (/features/inventory/locations/): managing the location list and per-location overrides. - [Variant constants] (/features/forecast/variant-constants/): per-variant overrides. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): the math the location filter affects. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/views-and-filters/ # Views & filters Combine filters, columns, and sort into a reusable view. A [view] (/reference/glossary/#view) is a reusable, named saved state: columns, filters, sort, location scope, and forecast settings. Build as many as you like; switch between them with the view button in the forecast toolbar, which shows the open view’s name. Views are the single most important concept in Logistified to understand well; they shape what you see and what every other feature acts on. ## On this page - Why views matter across the app - What a view is - The default view - Building filters - Combining filters (AND / OR) - Sorting - Cloning, renaming, deleting, starring - Auto-generated views - Sharing across teammates - See also ## Why views matter across the app A view is the unit of reusable analysis in Logistified. The same filter + same forecast settings can be applied anywhere variants are listed, not just on the Forecast page. Views power four surfaces: - Forecast page: switch views to switch what you’re looking at (overdue reorders today, slow movers, single-supplier batches, …). - Notifications: pick a view to scope which variants a notification rule watches (“alert me on the variants in Overdue under $5k cost”). - Reports: view-report and custom stock notifications send the contents of a view by email on a schedule. - PO creation: when you create a PO from the Forecast page, the originating view is stamped on the PO for audit; you can also reuse an existing view to pre-populate the PO line items. Plan to build many views, one per real-world question you ask of your catalog. A short starter list: - “Reorder within 14 days”: the daily working view. - “Overdue reorders”: anything red. - “Single supplier: Acme Corp”: when you’re batching POs to one vendor. - “Slow movers”: variants with days-of-stock above some threshold. - “Stock-out risk in 30 days”: combine days-of-stock with the lead-time view. Each view answers one question well. Switching between them is faster than re-filtering the same view over and over. ## What a view is A view captures everything that defines your current Forecast page state: - Which columns are visible, in which order. - Every filter you’ve applied. - Sort order. - Location filter (and the Global demand toggle, if set). - Forecast settings (model, history period, growth amplifiers, safety stock). - The display mode (Standard, Supply, or Sales Performance), one row per variant or per product, and the [Supply view’s settings] (/features/forecast/supply-view/#what-the-view-remembers). Save it, name it, return to it any time. Views are shared across every shop user and consumed by Notifications, Reports, and PO creation in addition to the Forecast page. ## The default view Auto-created on install. Shows a small starter set of columns; see [Forecast view table] (/features/forecast/view-table/#what-you-see-by-default). It cannot be renamed, deleted, or saved over; the Save action is disabled on it, so use Save view as… to keep any changes you make while it is open. Settings → Dashboard is a different setting: it picks which view filters the Overview page’s data, not which view the Forecast page opens on. ## Building filters The toolbar’s filter button opens the filter panel. Seven filter types. Logistified picks the right one based on the column type: Type Operators Numeric equals, not equals, less than, greater than, less or equal, greater or equal, between. Text equals, not equals, contains, starts with, ends with, exclude contains, pattern. Include / exclude multi-value chooser (for tags, categories, suppliers). Boolean Yes / No, for columns such as “In Draft PO”. Date is, is not, is before, is after, is between, on or before, on or after. Threshold stock at / above / below / at-or-above / at-or-below a variant threshold (e.g., “below static reorder point”). Reorder within N days variants whose reorder date falls within the next N days, plus, for suppliers with a product-level MOQ, every size that carries a quantity in a product order due within N days (its own reorder date may be later). For draft-order cleanup, use In Draft PO = Yes to review rows already sitting on Draft POs, or In Draft PO = No before adding a forecast selection to another Draft PO. The On PO with Status filter covers every status, not just Draft. Include one or more statuses to see rows sitting on a Sent, Confirmed, or otherwise open PO, or exclude the built-in Any open PO option to find items you haven’t already reordered under any status. ### When filters take effect Multi-value choosers (Include / exclude, Boolean, and the threshold checkboxes) stage your ticks while the filter popover is open and refresh the table once; click Apply at the bottom of the popover, or just close it. Text, numeric, and date filters apply as soon as you pick the operator, and the popover closes. Removing a filter chip or flipping an AND/OR connector applies immediately. Adding a new filter never refreshes the table until it has at least one value. ## Combining filters (AND / OR) Two connectors are in play, and neither is chosen by column type: - Between values inside one column. Every value you add is joined with OR; any of them matches. Click the amber OR chip between two values to flip it to AND. - Between different columns. The first filter you add is AND. From the second onwards Logistified asks you to pick AND or OR as you add it, and the connector between two column filters stays clickable afterwards. Older views saved without an explicit connector fall back to AND, except include-lists and text “equals”, which fall back to OR. ## Sorting Click a sortable column header (a few columns have sorting disabled). The arrow indicates direction, and clicking again reverses it; the sort toggles between ascending and descending only; there is no third click that clears it. Sorting runs server-side and is written back into the view, so it survives a reload. ## Cloning, renaming, deleting, starring On the Views page, the list on the left carries the star; the rest live on the detail pane beside it: - Duplicate: opens a dialog where you name the copy ( (Copy) by default) and tick which parts to carry over: columns, filters, locations, clustering, forecast settings, reorder settings. The copy is saved straight away; it is not left in a “Modified” state. - Rename: click the view name in the detail pane’s header and edit it in place. - Delete: confirm dialog. - Star: the star button on each list entry; starred views sort to the top of the list. The Forecast page’s command palette (⌘K / Ctrl-K) offers the same Save, Save view as…, Rename and Delete actions for whichever view you currently have open. ## Auto-generated views Logistified creates some views for you: - A default view per shop. - Drill-down views behind the ABC chart’s tier legend on the KPIs tab and the View links on the Data Quality counters. - A snapshot view each time you start a purchase order, transfer order, or stock take from the Forecast page (ids beginning forecast-po-, forecast-to-, forecast-st-): it records what the Forecast page looked like when that document was created. Those drill-down views are ordinary auto-generated views; they are saved and survive a reload rather than vanishing. They are hidden from the Views page’s list by default, though: tick Show autogenerated in that page’s filter menu to see them. (They do appear without any extra step under the Autogenerated tab of the Overview page’s Forecast Views card.) But Logistified rewrites their contents every time it recomputes the Overview data, so don’t edit one expecting your changes to stick, and each one covers at most the first 500 matching variants. Duplicate it if you want a stable copy. The PO/TO/stock-take snapshot views can also crowd the Use Existing View picker in the Create-from-Forecast dialogs. Turn on Hide auto-generated views in the purchase order dialog at [Forecast Preferences] (/features/forecast/forecast-preferences/#hide-auto-generated-views) to limit that picker to views you created yourself. ## Sharing across teammates All views are shop-wide. Anyone with access to the shop sees every view in the sidebar. There’s no per-user privacy yet. Note The “Reorder within N days” filter doesn’t speed up the page load; every variant is fetched, then filtered after the model runs. On very large catalogs, expect a couple of seconds. Caution Long text values are no longer shortened for you; a filter matches the whole thing you typed. A very long contains, starts with, or ends with value takes a slower route than a short one, as does the pattern operator at any length. The result is exactly right either way; on a large catalog, expect a wait. ## See also - [Forecast view table] (/features/forecast/view-table/): what each column shows. - [Forecast → Overview] (/features/forecast/overview/): the page-level tour. - [Exporting the forecast] (/features/forecast/export/): download one view, or combine several saved views into one file. - [Guides → Create and save custom views] (/guides/create-and-save-custom-views/): a worked walkthrough. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/forecast/variant-constants/ # Variant constants Per-variant min / max / target / static-reorder-point overrides: what they do and what they don't. In Logistified, variant constants are four per-variant overrides: [Min Inventory] (/reference/glossary/#min-inventory), [Max Inventory] (/reference/glossary/#max-inventory), [Target Inventory] (/reference/glossary/#target-inventory), and [Static Reorder Point] (/reference/glossary/#static-reorder-point). Use them when a SKU should be constrained by your business rules: a product you never want below 50, or never above 500. ## On this page - What variant constants are - Where to set them - Cross-field validation - How they show on the Forecast page - What they do not do - Bulk import - See also ## What variant constants are Per-variant numeric overrides, one set per variant (or per variant × location). They tell Logistified your business limits for stock at a given location: - Min Inventory: the smallest stock level you want. - Max Inventory: the largest stock level you want. - Target Inventory: the level you refill to. - Static Reorder Point: a fixed reorder point you set yourself, instead of the model’s computed one. Optionally configurable per location too. ## Where to set them Variant constants live on a dedicated settings page: Settings → Products → Variant Constants. A grid where you can edit many rows at once, or import via CSV/XLSX through the unified import flow. The forecast page only displays the constants; the Min / Max / Target / Static Reorder Point columns are read-only there. You can’t edit a value by clicking the cell on the Forecast page; head to the settings page to make changes. ### Reading names in the table editor Product and variant names use up to two lines. Click or tap the chevron beside a name to expand it within the same row and read the full name; use it again to collapse the name. You can expand several rows independently. Hover over the name button or focus it with the keyboard to see the full name in a tooltip. With the button focused, press Enter or Space to expand or collapse it. For stores with one active location, the Location column is hidden when every row shown belongs to that location, giving names more room. The location filter remains available. Rows for another or inactive location keep the column visible, and filtering a store with several active locations down to one does not hide it. Expanding a name does not change your values or row selection. [Image: Variant constants table with a full product name expanded and numeric inventory values alongside it] (/_astro/10-variant-constants-table.DR9KnJb2_Zi4uQF.webp) Expand a name to read every detail while keeping your inventory values in the same row. ## Cross-field validation Logistified enforces three rules so the values stay internally consistent: - Min ≤ Max - Min ≤ Reorder Point ≤ Max - Reorder Point < Target ≤ Max If a rule is violated, the row turns red and the save is blocked until fixed. ## How they show on the Forecast page Once a variant has a Max Inventory, the In Stock cell shows a read-only fill bar under the number. The full width of the bar is your Max; the fill is your current stock, with thin markers at the Min, Static Reorder Point, and Target you’ve set. The fill color signals where current inventory sits: Color Meaning Red Below Min. Amber At or above Min, but below Static Reorder Point or Target. Green At or above Min, Static Reorder Point, and Target. Variants without a Max Inventory show no bar. Hover the cell for the breakdown: its Thresholds scale places your current stock against each constant you’ve set, labelled Min, Reorder, Target, and Max. The bar is part of the Standard view. In the [Supply view] (/features/forecast/supply-view/#the-in-stock-column), the In Stock cell shows only two lines of text (available and incoming stock) with no bar and no colours; hover it for the same breakdown. There, a variant’s period card also draws the constants you’ve set as dashed lines in its stock chart, labelled Min, Max, Target, and Reorder; see [The chart] (/features/forecast/supply-view/#the-chart). ## What they do not do Variant constants are display + alerting only for the forecast page. They don’t change the forecast model’s reorder math. - The reorder math (Reorder Point, Reorder Date, Reorder Quantity) uses the forecast model’s computed values plus the supplier link’s lead time, MOQ, and pack size. - Static Reorder Point is only used for threshold filters, the In Stock cell, and the dashed line in the Supply view’s card chart. The forecast still computes its own reorder point in parallel. - Min / Max / Target are consumed by the separate “Create PO from min/max” workflow on the Suppliers list, and by the “Create TO from min/max” workflow under Transfer Orders. Tip Don’t set Static Reorder Points unless you have a specific business reason. The model’s computed reorder point responds to demand shifts; a number you set once doesn’t. ## Bulk import For larger catalogs, use the import flow. Settings → Products → Variant Constants → Import. Map columns, preview, commit. See [Guides → Import data (CSV/XLSX)] (/guides/import-data-csv-xlsx/) for the full walkthrough. The optional Import action column controls each row: - Leave it blank or use UPDATE to save the supplied values. Blank value cells preserve existing constants. - Use DELETE to remove Min, Max, Static Reorder Point, and Target Inventory for that variant and location. The preview marks deletions and asks for confirmation before applying them. Rows are applied in file order. If the same variant and location appears more than once, the last successfully applied row determines the final state. Caution Deleting variant constants removes the item from Min/Max-based replenishment for that location, but it does not suppress forecast demand. For discontinued products, also apply a Shopify tag such as DISCONTINUED and exclude that tag in the saved forecast views used to create purchase orders. The bulk grid and the import flow are the only ways to edit variant constants; there’s no inline-editing path from the Forecast page. ## See also - [Forecast → Forecast view table] (/features/forecast/view-table/): where the variant overrides show up. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): the math that does not use these overrides. - [Guides → Import data (CSV/XLSX)] (/guides/import-data-csv-xlsx/): bulk import. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/reorder-suggestions/ # Reorder suggestions How the Reorder Forecast quantity and the Reorder Date are computed, end to end. In Logistified, a reorder suggestion answers two questions per variant: how many and when. The “how many” lives in the Reorder Forecast column. The “when” lives in the Reorder Date column. This page explains how each number is calculated, what it means, and how to act on it. ## On this page - What the suggestion means - The Reorder Forecast, end to end - All the inputs - What the colors mean - Product-level MOQ (and ordering soon-due sizes) - Back orders and lost sales - How to act on it - Edge cases worth knowing - See also ## What the suggestion means Two-bullet TL;DR before the math: - Reorder Forecast is Logistified’s answer to: if I place a PO today, how many units do I need to stay safe through one more lead-time cycle until this stock arrives? It’s the recommended order quantity after MOQ, pack size, and economic order quantity adjustments. When economic order quantity beats the raw demand-based number, you see a green “EOQ” pill in the cell. - Reorder Date is the calendar day your on-hand inventory is projected to drop to the [reorder point] (/reference/glossary/#reorder-point). Acting earlier is safe; acting later risks running out. When you create a PO from the Forecast page, the quantity starts from the displayed Reorder Forecast. If the cell shows an EOQ uplift, that uplift is included in the suggested PO quantity. ## The Reorder Forecast, end to end Think of it as running your inventory forward in time on autopilot. Starting from today’s on-hand, Logistified walks one day at a time across the forecast horizon, depleting stock by the forecast model’s daily demand and crediting incoming POs and TOs on their expected arrival dates. The reorder columns fall out of that simulation; they aren’t a separate arithmetic chain. Here’s the sequence in plain terms: 1. The forecast model produces a daily demand vector, one number per future day across the horizon. 2. Starting from today’s on-hand, the simulation walks each future day in turn. 3. Every day, on-hand drops by that day’s predicted demand. 4. On dates where an open PO or TO is expected to land, the simulation credits the incoming quantity to on-hand. 5. Safety stock (auto from service level and demand variability, plus the optional force-majeure factor and, if you’ve enabled it, a supplier-reliability buffer) defines the floor below which the simulation considers you at risk. 6. The first day the simulated on-hand crosses the lead-time-demand + safety-stock threshold is the reorder point crossing; that day’s date becomes Reorder Date. 7. The Reorder Forecast is sized so that, if you fire the PO today, the simulation lands you safely above the floor at the end of the next lead-time cycle when the stock arrives. 8. MOQ and pack size adjust the raw simulated quantity (round up to MOQ, round up to a pack-size multiple). EOQ may bump it up further when ordering more is cost-efficient (then you see the green EOQ pill). 9. Pending back orders, when applicable, are added on top. ### Worked example Say you sell 2 units per day of a widget. Your supplier needs 30 days to ship. You’ve set safety stock to auto (95% service level → about 10 units for this variant). You currently have 100 units on hand and nothing incoming. Simulating forward from today at 2 units/day: - Day 0: 100 on hand. - Day 15: 70 on hand. This crosses the reorder threshold (lead-time demand 60 + safety stock 10 = 70). Reorder Date = today + 15 days. - Day 30: 40 on hand. If you do nothing, you’re still above zero but inside the danger zone. So how many to order today? The simulation answers: enough to cover the next lead-time cycle from the moment the stock arrives. If you fire the PO today, it shows up in 30 days. On that day you’ll be at 40 on hand. Add the next 30 days of demand (60 units) plus safety stock (10); you need on-hand to land near 70 at delivery. That means an order of about 30 units. MOQ kicks in: your supplier’s minimum is 50, pack size 10. Round up: Reorder Forecast = 50, with the MOQ progress bar showing emerald (your demand comfortably covers the minimum). ## All the inputs Input Where set Default If blank Forecast model Variant detail page, or view settings Auto Auto picks History period View settings Auto (optimal per variant) Auto picks Lead time Supplier ↔ variant link 7 days at the supplier link; longer fallback for the Default supplier Default applies Safety stock View settings (forecast settings panel) Auto, 95% service level Auto applies MOQ Supplier ↔ variant link 1 Defaults to 1 Pack size Supplier ↔ variant link 1 Defaults to 1 Force majeure factor View settings Off Off Incoming quantity Open POs + TOs Sum of pending 0 Supplier-held stock View settings (forecast settings panel) Off: every existing view keeps today’s behaviour Ignored Supplier reliability Per supplier (manually set) Off: must be enabled in the view’s reorder settings, then set on the supplier Treated as 100% if unset Holding cost Per variant (Settings → Products) 0 EOQ not used Ordering cost Per supplier 0 EOQ not used ## What the colors mean Element Color Meaning Reorder Date Red Overdue. You should have reordered already. Reorder Date Warning yellow Due today, or within 7 days. Reorder Date Muted Due in weeks or months. MOQ progress bar Red Demand fills less than 70% of the supplier’s MOQ. MOQ progress bar Orange Demand fills 70–99% of MOQ. MOQ progress bar Emerald Demand fully covers MOQ. “EOQ” pill Green EOQ was bigger than the raw quantity; Logistified rounded up to the economic order size. ## Product-level MOQ Some suppliers set their MOQ once per product instead of once per variant; see [Suppliers → Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product) for where that’s configured. When a row’s supplier is set this way, the Reorder Forecast cell and its hover card change shape: - The MOQ progress bar and pill compare the product’s combined total to the product minimum, not this one row’s quantity to this row’s own MOQ. - A “Product MOQ” badge appears on every affected size once a minimum is set for the product. It’s neutral (gray) when the product already meets its minimum or the group can’t be fully evaluated, and amber only when Logistified actually lifted this product’s quantities to reach the minimum. - A product with more sizes than Logistified can evaluate at once shows “Product MOQ not applied (too many sizes)” instead; none of its rows get the minimum applied; treat those the way you’d treat a per-variant MOQ of 0. - The hover card shows the recommended total across every size, the product minimum, how much of that is to reach the minimum versus pack-size rounding, and the split across sizes (sizes on other pages are marked “(not on this page)”). Read the per-size Reorder Date / Days-until-reorder columns for when to reorder each size; the product minimum only changes how much. On a product-MOQ row the hover card names the parts that moved this size’s number, alongside the usual safety-stock and pack-size lines: Row What it means Product MOQ share Units added to this size so the product as a whole reaches its supplier’s minimum. Pulled forward This size wasn’t due yet, but it was ordered now because Order soon-due variants too is on; see below. Order limit Units taken back off because the size’s maximum order quantity capped what it could take. Creating a PO from the Forecast page carries the same product-adjusted quantities, so the PO you get already reflects the shared minimum; see [Purchase Orders → Line items & costs] (/features/supply-orders/purchase-orders/line-items/#constraint-badges) for how it’s checked afterward if quantities change. ### Order soon-due variants too When a product is short of its supplier’s product minimum, Logistified completes the minimum over the sizes that actually sell. Order soon-due variants too lets it also pull in sizes that aren’t due yet but will be shortly, so you place one order instead of two a few days apart. The control has two states: - Off (the default): only what is due gets ordered. The product minimum is still completed over the sizes that sell. - Up to N days: while the product is short of its minimum, any size that reaches its own reorder point within N days of the product’s order day is ordered now, at its regular quantity. N is a whole number of days from 1 to 90; switching the toggle on starts at 7. The trade-off: any window adds stock for the sizes it pulls forward, and longer windows add more. Leave it off unless you’d rather hold that stock early than send the same supplier a second order a few days later. Sizes that came in this way are labelled Pulled forward, next to the size’s quantity in [Products mode] (/features/forecast/product-view/#expanding-and-collapsing-sizes), and as a Pulled forward row in the hover card above. Where to set it. Open Forecast Settings (the toolbar popover) or the view editor’s Reorder tab, and look under Minimum order quantity (MOQ); the guided view wizard offers the same control on its MOQ step. Like every other forecast setting it is saved on the view, not on the supplier. It only appears when at least one of your suppliers has a product-level minimum in force and the view’s MOQ source is set to Supplier; otherwise it stays hidden and keeps whatever value you last gave it. ## Back orders and lost sales The Reorder Forecast cell’s sub-line gives context based on your variant’s inventory policy: - “X Back Orders”: when the policy is Continue selling when out of stock. The X customer orders that came in while you were out get rolled into the next reorder. Their units are added to Reorder Forecast. - “X Lost Sales due to missed ROP”: when the policy is Deny. Missed demand was lost, with no back orders kept. Informational; counts toward stock-out reporting. ## Demand variability warning A small triangle next to the Reorder Forecast warns when the item’s demand over the period one order covers has ranged widely and comes in runs, gaps or surges rather than ordinary day-to-day ups and downs (amber, or red when high). It is a prompt to check the expected demand before ordering; it does not change the quantity. Open the hover card to see the typical range over that period (the lead time plus the view’s target days of supply), how much history was used, and how the safety stock was sized. When there’s too little history to judge, the card says so instead of showing a level. The same triangle also appears when most of the history was excluded as stock-outs (see [History period] (/features/forecast/history-period/#excluding-stock-out-periods)), since the forecast then rests on few days. ## How to act on it Three paths, in order of frequency: 1. From a single row. Click “Create PO” on the row’s action menu. A dialog opens prefilled with the suggested quantity. 2. Bulk from the toolbar. Select rows, then “Create PO from selected.” The dialog starts with the suggested quantities and asks you to choose one supplier or split by supplier. 3. Add to existing PO. When you have a draft PO open, “Add to existing PO” appends the selected lines. ## Edge cases worth knowing - The reorder date can show a dash / no recent sales: a placeholder you can interpret as “no signal.” - Variants with only the [Default supplier] (/reference/glossary/#default-supplier) attached still get a suggestion, but it uses fallback values. Assign a real supplier first. - A pack size of 0 is treated as 1 (a safety net for operator errors). - A negative “days until reorder” is clamped to 0, meaning “reorder now.” - The force majeure factor stacks on top of the auto-computed safety stock; it doesn’t replace it. Tip When the suggestion doesn’t match your intuition, hover the Reorder Forecast cell. The hover card shows every input value used in the math; usually one of them is the surprise. ## See also - [Forecast view table] (/features/forecast/view-table/): every column documented. - [Exporting the forecast] (/features/forecast/export/): download a view, or several views at once. - [Group rows by product] (/features/forecast/product-view/): see product-level MOQ status and totals summarized per product. - [Supplier-held stock] (/features/forecast/supplier-held-stock/): counting stock parked at a supplier as incoming. - [Forecast models] (/features/forecast/forecast-models/): what produces the daily-demand number. - [Variant constants] (/features/forecast/variant-constants/): what they do (and don’t) affect here. - [Suppliers → Lead times & MOQ] (/features/suppliers/lead-times-and-moq/): set MOQ per variant or per whole product. - [Guides → Configure reorder parameters] (/guides/configure-reorder-parameters/): setting up the inputs. - [Guides → Set up your first forecast] (/guides/set-up-your-first-forecast/): the beginner walkthrough. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/growth-amplifiers/ # Growth amplifiers Nudge a forecast up for a campaign, launch, or known event the model hasn't seen yet. In Logistified, a [growth amplifier] (/reference/glossary/#growth-amplifier) multiplies the forecast by (1 + boost) over a date range. A 30% boost means “expect 30% more sales than the model would predict, every day inside this range.” Useful when something the model can’t see in history is about to drive demand: campaigns, launches, known events. The same popover also shows your shop’s [promotional events] (/features/inventory-planning/promotional-events/): holidays and sales that come back every year and lift every view’s forecast once you switch them on. ## On this page - What an amplifier does - When to use one - Setting one up - Setting one from the Supply view - Status badges - Stacking - What it doesn’t change - Removing one - Promotional events in the forecast - When an event is not applied - When an event may count twice - Per-product uplift - See also ## What an amplifier does The amplifier multiplies the forecast model’s daily prediction by (1 + boost) for each day inside the range. The boost is a percentage; 30% means 1.30x; 100% means 2x. Because the forecast feeds the reorder math, an amplifier shifts everything downstream: the reorder point gets larger, the reorder date moves earlier, the reorder quantity goes up. ## When to use one - A one-time marketing campaign. For a holiday or sale that repeats every year, such as Black Friday, add a [promotional event] (/features/inventory-planning/promotional-events/) instead: you set it up once for every view and every year. - A product launch (new collection drop, influencer collaboration). - A seasonal push the historical data doesn’t reflect: your first ever Christmas in business, or a major one-off promotion. - A known one-off (a TV mention, a viral moment you can plan around). Not useful when the forecast model can already see the pattern in history. Recurring seasonality (yearly cycle, weekend uplift) is the model’s job, not yours. ## Setting one up Click the Amplifiers button in the Forecast toolbar. The button turns green when amplifiers or promotional events are in effect, and its number counts them. When a promotional event lifts the forecast, the button also gets a soft green glow and a ★ before the number. Under This view’s amplifiers, click Add period and set: - Boost % (15% to start with, at most 100%). - Start date. - End date. A new period starts today and runs for two weeks until you change its dates. Click Apply. The forecast reloads with the boost, and the view shows Unsaved changes until you save it. ## Setting one from the Supply view In the [Supply view] (/features/forecast/supply-view/#the-period-header-and-the-column-card), you can set an amplifier straight from the period headers: - Drag across the headers. Press on a period header and drag across the periods you want. When you let go, the Apply Growth Amplifier dialog opens with those dates. Set the Amplifier and click Apply Amplifier. Esc cancels the drag. - From one period’s card. A plain click on a header opens that period’s column card instead. Its Growth amplifier for this period button opens the same dialog for just that period. Periods with an amplifier show a green chip in their header, for example +20%. When amplifiers overlap, the chip shows the largest combined boost on any day of the period. The column card repeats it as Growth amplifier +20% · set on this view, and a cell’s card names the days it covers, for example Growth amplifier +20% · Fri–Sun (or all week). ## Status badges Each amplifier shows one of three states: - active: today is between start and end. - upcoming: start is in the future. - past: end is behind today. Past amplifiers stay on the list; they’re history. Delete them when you’ve collected enough data to know whether the campaign worked. ## Stacking Two amplifiers covering the same day add up. Two +15% amplifiers means +30% for that day. Promotional events add up the same way, with each other and with the view’s amplifiers. Useful when you want to compose effects (“baseline launch boost” + “extra Black Friday boost”). Amplifiers also stack on top of whichever model the view uses, including [History replay] (/features/forecast/forecast-models/), so “replay last year, plus 10%” is a single, readable setup: pick History replay for the model and add a +10% amplifier over the range you want lifted. ## What it doesn’t change - Historical data: amplifiers only affect the forward forecast. - The forecast model itself: Auto still uses your sales history to pick the model. The amplifier rides on top. - The simulation steps: the day-by-day inventory simulation just runs against the amplified daily-demand vector, so all downstream reorder columns shift accordingly. ## Removing one In the popover, click the bin icon on the amplifier’s row, then Apply. Save the view to keep the change. Note Amplifiers are stored on the view. Two operators looking at the same shop but different views might see different reorder suggestions if their views have different amplifiers configured. ## Promotional events in the forecast Above the view’s own amplifiers, the popover lists every switched-on [promotional event] (/features/inventory-planning/promotional-events/) under Promotional events (marked shop-wide), also the ones that change nothing in this view. Each row shows the event’s dates within the forecast horizon (the next two years) with their uplift, for example Nov 27, 2026 +40 % · Nov 26, 2027 +40 %, the first two and how many more. An event measured per product shows no percent there, as each product gets its own. A tag on each row says what the event does here: - Applied: the event lifts this view’s forecast. - Applied, outside this view’s date range (Supply view): the event’s next dates come after the view’s last column. Reorder dates and quantities further out still include it. - Off in this view: you switched it off for this view. - Would double-count, not applied: see [When an event is not applied] (#when-an-event-is-not-applied). - No upcoming dates: the event has no dates within the forecast horizon. - No uplift: the event’s uplift is 0 % on every date, so it lifts nothing. This happens when Fixed % is left empty, or when From past years has not been analyzed and has no fallback uplift, or measured no increase. Set an uplift on the event. - No past dates to measure (measured per product, No uplift for products without sales history): there is no past occurrence to measure each product’s uplift at yet, so no product is lifted. - Sales history still being prepared (measured per product, No uplift for products without sales history): your products’ sales history is still loading, so no product can be measured yet and none is lifted. - No sales data for the comparison period (measured per product, No uplift for products without sales history): no product on this page has sales for the whole comparison period before the last occurrence, so none on this page is lifted. A note on the row says so, for example No product on this page has sales for the whole comparison period before Black Friday 2025, so none of them gets an uplift. With Use the shop-wide uplift, the event stays Applied and the note names the uplift every product uses instead. - Needs the Enhanced plan: promotional events lift forecasts on the Enhanced and Elevate plans only. The events are listed, but the forecast does not use them, and their switches are locked. The popover links to Plans and billing. - Plan update pending: your shop is on a plan that includes promotional events, but forecasts still see your previous plan, so the events do not change the forecast yet. Contact support if this does not clear. To leave an event out of one view, switch off the switch on its row. To leave every event out, switch off Apply promotional events in this view. Then click Apply and save the view. This only changes this view: other views keep the event, and the event stays switched on. The view keeps leaving the event out even while the event is switched off or archived, so it doesn’t come back here when you switch it on again. An event you add later applies to every view until you switch it off there. Click an event’s name to open it. In the supply view, the column headers of periods with an applied event are tinted blue with a ★ 1 badge below the dates (the number counts the applied events). Point at the badge for the event’s name, for example Black Friday +40 % applied here, or Black Friday applied here, uplift per product for an event measured per product. A grey ☆ 1 badge marks events that are listed but not applied, for example Black Friday +40 % off in this view, Black Friday +40 % not applied: would double-count or Black Friday not applied: uplift is 0 %. A cell’s card names the event and the days it covers, for example Black Friday +40 % applied here · Fri. The column card also counts the products it lifts, for example Black Friday +40 % · Fri · lifts 10 of 12 variants, and names the ones it doesn’t. ## When an event is not applied Some views already repeat last year’s sales. Adding the event on top would count last year’s spike twice, so the event is left out there: - A view whose history period is Rolling (Past Year + Lead Time) applies no events. The popover says: Not applied: this view already repeats last year’s sales, so applying an event would double-count. - A product forecast with [History replay] (/features/forecast/forecast-models/) over a whole year (365 days, give or take a week, or a whole number of years) gets no events either. The popover counts them, for example Not applied to 12 variants on this page: History Replay already repeats last year’s sales for them., and the product’s reorder date hover says Not applied to this variant: History Replay already repeats last year’s sales. ## When an event may count twice The forecast learns from the view’s history period. If that period contains last year’s event, the base forecast may already include part of its spike, and the event adds its uplift on top. In that case the event is still applied, and the popover warns you, for example: Your history window (last 90 days) contains Black Friday 2025. The base forecast may already include that spike, so applying events on top may double-count. When the view picks a history window per variant, the warning counts the variants instead, for example The history window of 12 variants on this page contains Black Friday 2025. The warning shows only on rows tagged Applied or Applied, outside this view’s date range. If the warning matters for this view, lower the event’s uplift, switch the event off for this view, or pick a history period that doesn’t include the event. ## Per-product uplift An event whose uplift is measured for Each product variant (shown as Per product variant) measures each product’s own uplift at the event’s most recent past occurrence. A product’s own measurement counts in proportion to how much it normally sells in that period. A product that sells only a few units leans mostly on the event’s shop-wide uplift or its fallback (or on 0% if products without sales history get No uplift). A steady seller keeps nearly all of its own measured lift. The popover explains it per event, for example Per product variant: uplift measured from each product’s own sales at Black Friday 2025; products without enough sales use +40 %. Before the event has run once, it says so instead: Per product variant: there is no past Black Friday to measure from yet, so every product uses +40 %. A row tagged Would double-count, not applied has no such line, as nothing applies there. A product’s reorder date hover shows its own result under Promotional events, for example Black Friday: measured +233 % (4 vs 1.2 expected at Black Friday 2025), weight 29 % → +95 %: 4 units sold against 1.2 expected, a measurement that counts 29 %, and the uplift the forecast uses. A product that couldn’t be measured says why, for example Black Friday: no sales history before Black Friday 2025 → +40 %. See [One uplift or one per product] (/features/inventory-planning/promotional-events/#one-uplift-or-one-per-product). ## See also - [Promotional events] (/features/inventory-planning/promotional-events/): the yearly calendar of holidays and sales. - [Forecast models] (/features/forecast/forecast-models/): what the amplifier rides on top of. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): where amplifier effects land. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/supplier-held-stock/ # Supplier-held stock Count stock you already own but that's still sitting at a supplier as supply, so the forecast doesn't suggest reordering it a second time. Stock you already bought (or shipped out on a transfer order) can end up parked at a supplier instead of on your shelf, waiting for a release, a consolidated shipment, or a repack. Until it’s counted somewhere, Logistified’s forecast has no way to know it exists, and can end up suggesting you buy it again. Supplier-held stock closes that gap: the quantities always show on the Forecast page, and, if you turn the setting on, they count in the reorder math too. ## On this page - Two separate pieces: columns and math - The Stock at Supplier columns - Turning on the reorder math - Where it shows up once it’s counted - Release lead time - Interactions and edge cases - See also ## Two separate pieces: columns and math Supplier-held stock ships as two independent pieces: - The columns always display. Stock at Supplier and its Available/Reserved breakdown are visible (once added to your view) whether or not you’ve turned anything on. - The reorder math is opt-in per view, and defaults to Off; every view you already have keeps behaving exactly as it did before this existed. Turn it on deliberately once you’re ready to let it influence reorder suggestions. ## The Stock at Supplier columns Three columns, grouped under Inventory & Stock in the Columns picker, hidden by default: Column What it shows Stock at Supplier Your own stock physically held at suppliers, the total across every active position. Stock at Supplier (Available) The part of that stock not reserved by an open release. Stock at Supplier (Reserved) The part of that stock reserved by an open release. A cell showing 0 is plain text with no hover card; most variants have nothing held, so nothing loads for them. A cell above 0 opens a hover card on mouseover with a per-supplier breakdown: quantity held, available vs. reserved, and, when known, the purchase order or transfer order the stock originally shipped on. Click a supplier’s name or a source document number to jump straight there. Note These columns ignore your location filter. A held position isn’t sitting at any of your locations, so narrowing the Forecast page to one location doesn’t change the numbers. ## Turning on the reorder math Open Forecast Settings (the toolbar popover) or the view editor’s Reorder tab and find Include supplier-held stock. Three states: - Off (default): held stock is ignored by reorder math entirely. This is how every view behaved before this setting existed, and it’s still the default for every new view. - Available now: held stock is counted as if it were already reachable, starting today. - After release lead time: held stock is counted as arriving on a future date, based on the supplier’s [release lead time] (#release-lead-time). Turning this on affects the same downstream numbers as any other incoming quantity: [reorder point] (/reference/glossary/#reorder-point) crossing, [days of stock with all incoming] (/reference/glossary/#days-of-stock-with-all-incoming), the order-up-to horizon, and the Incoming column and its hover card. ## Where it shows up once it’s counted With the setting on, each held position appears as its own row wherever incoming quantities are listed: - The Incoming column’s hover card, and the Incoming Quantity it feeds into. - The variant detail page’s incoming table. These rows are labelled “At supplier” instead of a PO or TO number, and carry the status At supplier. Clicking the row takes you to that supplier’s My stock at supplier sub-view (see [Supplier directory → Supplier detail page] (/features/suppliers/directory/#supplier-detail-page)) rather than a purchase order or transfer order, because the stock isn’t tied to either. Note Supplier-held stock rows never count toward the overdue badge on incoming quantities. Held stock isn’t “awaiting receipt” in the same sense as an open PO or TO, and its date is an estimate of when it’ll be released (not a delivery promise), so it’s excluded from that check. ## Release lead time After release lead time needs to know how long it takes stock to travel from the supplier to a warehouse once it’s released. Set this on the supplier: Suppliers → Create/Edit supplier → Supplier-Held Stock → Release lead time (days). Leave it blank and Logistified falls back through the item’s own transit and lead-time settings, then the supplier’s default lead time, before finally using the shop-wide default. A release lead time of exactly 0 days is treated as a real answer (immediate arrival), not as “unset.” Tip Release lead time is its own field, separate from the ordering lead time on a supplier–variant link (see [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/)). Changing it never triggers the “apply to all items” prompt you see for ordering defaults, because it isn’t one. ## Interactions and edge cases - Requires “Include incoming quantity.” If that setting is off, the view plans warehouse-only stock and supplier-held stock can’t contribute either; the control is disabled with an explanation until you turn incoming quantity back on. - Location filters don’t affect the totals. Held positions carry no location, so filtering the Forecast page to specific locations doesn’t narrow or hide them. - Existing views are unaffected. A view saved before this setting existed has it at Off, byte-for-byte the same reorder math as before. ## See also - [Forecast view table] (/features/forecast/view-table/): the Stock at Supplier columns among every other column. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): how incoming quantities (supplier-held stock included) feed reorder point and quantity. - [Suppliers → Lead times & MOQ] (/features/suppliers/lead-times-and-moq/): the per-supplier-variant lead time this feature’s release lead time is separate from. - [Suppliers → Supplier directory] (/features/suppliers/directory/): the “My stock at supplier” sub-view held-stock rows link to. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/variant-detail/ # Variant detail The drill-down page for one variant: Overview, Models, and Purchase Orders tabs. In Logistified, the variant detail page is the drill-down for one variant: current stock, the reorder math breakdown, the model ranking Auto computed for this variant, and the PO history. Reach it by clicking any variant title on the Forecast page. ## On this page - How to reach it - What you see - Overview tab - Models tab - Purchase Orders tab - See also ## How to reach it Click any variant title on the Forecast page. The page opens with a back-link that preserves your originating view’s filter state, so when you’re done, you return to exactly where you were. You can also reach the variant detail page from purchase orders, stock takes, and other places where a variant link appears. ## What you see - A header with the variant image, SKU, variant title, primary supplier, and key metadata. - Three tabs: Overview, Models, Purchase Orders. ## Overview tab The default tab and the most-used. Three sections: 1. Stat cards: In Stock (with an out-of-stock date if relevant), Days of Stock (with all incoming), and Selling Price. 2. Supply Chain Management → Reorder Planning: the reorder columns laid out clearly: Reorder Point, Days Until Reorder Point, Days Overdue, Reorder Date (hover for the math), Reorder timing, Actual Reorder Quantity (hover for the math), EOQ, plus Back Orders / Lost Sales if applicable. 3. Safety Stock Breakdown: the per-component math behind the reorder point: Base safety stock, Force-majeure SS (if enabled), Supplier SS, and Supplier reliability. This is the home for the full Reorder Point breakdown. 4. Supply & Timeline: Lead time, MOQ, Pack Size, primary supplier name. Useful for: investigating a surprising reorder suggestion and seeing the safety-stock numbers behind the reorder point. ## Models tab A read-only model-ranking table. For each forecast model Logistified evaluated against this variant’s history, you see the model’s score and the internally-chosen parameters. Auto picks the top-ranked model. There’s no model picker or parameter editor here; model choice is set at the view level (see [Forecast models] (/features/forecast/forecast-models/)), and tuning is automatic. The Models tab is a diagnostic: why did Auto pick what it picked? ## Purchase Orders tab Every PO line item featuring this variant. Click a row to open the PO. Useful for tracing “where did the supply come from?” and “what’s still on the way?” Tip When a reorder suggestion looks weird, open the variant detail and look at the Safety Stock Breakdown first. Most surprising numbers are explained by an unusually high supplier-reliability buffer or a force-majeure factor. ## See also - [Forecast view table] (/features/forecast/view-table/): the parent page. - [Forecast models] (/features/forecast/forecast-models/): the models Auto chooses from. - [Variant constants] (/features/forecast/variant-constants/): where to edit Min / Max / Target / Static Reorder Point (Settings → Products → Variant Constants). Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/create-po-from-forecast/ # Creating a PO from the forecast Turn a row (or selected rows) on the Forecast page into a purchase order. Logistified’s Forecast page is the most common origin point for a purchase order. This page covers the three paths from “row I want to act on” to “draft PO ready to send.” For the rest of the PO flow, see [Purchase Orders] (/features/supply-orders/purchase-orders/overview/). ## On this page - Three creation paths - What gets prefilled - Multi-supplier selection - Avoid duplicate draft lines - Currency - See also ## Three creation paths Path Where it starts When to use Create PO Check one or more rows → Actions → Create PO in the toolbar. One urgent variant, or a batch you’re ordering together. Split by supplier Same dialog: leave the supplier field empty and submit Split & Create. A selection whose rows point at different suppliers. Add to PO Same toolbar, when you want selected rows to join an open draft or be distributed by supplier. Appending to existing Draft POs, or creating supplier-specific Draft POs from the same selection. In the Supply view you can also start from a card, without checking rows: - A cell’s card. Click a cell, then Create PO in its card opens the same Create Purchase Order dialog for that variant. In a period that asks for an order the button names the quantity, for example Create PO for 40, and the dialog takes it; otherwise it uses the variant’s usual recommended quantity. Add to draft PO (for example Add to draft PO PO-1042) opens the Add to Purchase Order dialog with a draft that already holds the variant picked. - A period’s card. Click a week, month, or quarter header, then Create POs for N variants opens the dialog for every variant with an order due or overdue in that period, each at its order quantity, with no supplier chosen so you can split by supplier. The purchase order records the view you started from, even if you switch views while the dialog is open. See [Acting from the card] (/features/forecast/supply-view/#acting-from-the-card). ## What gets prefilled Whichever path you pick, the new PO comes prefilled with: - Supplier: not automatically chosen from the selected rows. Choose one supplier for a single PO, or leave the supplier field empty to review supplier groups and split. - Quantities: the displayed suggested [reorder quantity] (/reference/glossary/#reorder-quantity) per variant, including EOQ uplift where it applies. - Unit cost: the supplier’s cost on the variant link when available. - Lead time, MOQ, pack size: informational when available; the suggested quantity is already adjusted. - [Originating forecast view] (/reference/glossary/#originating-forecast-view): the view you came from, stamped on the PO for audit. Since views are reusable across the app (see [Views & filters] (/features/forecast/views-and-filters/#why-views-matter-across-the-app)), the stamp tells you which question this PO was answering. You can edit any of these before sending. ## Multi-supplier selection When your selected rows span multiple primary suppliers, the dialog shows a prompt: - Choose one supplier: creates a single PO using that supplier and its defaults. This is not a strict guarantee that every off-supplier row is excluded, so review the lines before sending. - Split: Logistified creates one PO per supplier in one operation. Use this when you need supplier-specific POs. Each gets the originating-view stamp. When you choose Add to PO and leave the PO field empty, Logistified distributes the selected rows by supplier. Each supplier group can be sent to an existing Draft PO or set to Create new PO. If any group creates a new PO, choose the location those new POs should use before submitting. ## Avoid duplicate draft lines The Forecast table can show when a variant is already included on a Draft PO. In the Inventory quantity cell, look for “In X Draft POs” and hover to see the matching draft orders and quantities. You can also add the hidden In Draft PO column or filter In Draft PO = No before using Add to PO. To avoid re-ordering something that’s already on a Sent, Confirmed, or otherwise open PO (not just a Draft), add the hidden On PO with Status column, or filter it to exclude Any open PO. Draft PO membership is visual/filtering context only. It does not count as incoming inventory and does not change the suggested reorder quantity until the PO moves out of Draft. ## Currency The PO inherits the chosen supplier’s currency. To order in a different supplier currency, change the supplier before sending. Caution Supplier and location can only be edited while the PO is in Draft. If you picked the wrong supplier on a PO you’ve already sent, use Actions → Revert to Draft, change it, and send again; you don’t have to cancel or recreate the order. ## See also - [Purchase Orders → Overview] (/features/supply-orders/purchase-orders/overview/): what happens next. - [Purchase Orders → Creating a PO] (/features/supply-orders/purchase-orders/creating/): the canonical PO creation page. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): what’s in the prefilled quantities. - [Manufacturing orders] (/features/supply-orders/manufacturing-orders/overview/#what-you-can-do-here): the same selection can also open Create Manufacturing Order, prefilled the same way. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/export/ # Exporting the forecast Download a forecast view as XLSX or CSV: one view, or several saved views combined into one file. The Export button sits in the bar underneath Logistified’s Forecast table, next to the page controls. It downloads what the table shows: your visible columns, in your column order, with the numbers formatted the way you see them on screen. You can export the view you’re looking at, or combine it with other saved views in one file. ## On this page - Exporting the current view - Product summary rows - Which columns come out - Combining several views - Separate sheets vs. combined rows - File names and progress - See also ## Exporting the current view Click Export. A dialog opens with two choices: - Rows to export: Current page (the rows in front of you) or All pages (everything the view’s filters match). Some places that open this dialog also offer Selected rows. - Format: Excel Spreadsheet (.xlsx) or CSV File (.csv). Confirm with Export XLSX / Export CSV. The file downloads when it’s ready; large views take a moment while the remaining pages are fetched. ## Product summary rows When a Standard view [groups rows by product] (/features/forecast/product-view/), the dialog also shows Include product summary rows (on by default). A [Supply view] (/features/forecast/supply-view/#product-rows) grouped by product doesn’t offer it: its file always has one row per variant. With the option on, the file looks like the table: - A Row Type column comes first, saying Product or Variant. If the view shows no title column, a Product column follows it with the product name (and, on variant rows, the variant name), as in the table. - Each product with more than one exported variant gets a Product row above its variants: the product title, the total reorder quantity, the earliest reorder date, and the same summaries the product row shows on screen (summed stock, the range of prices, a shared vendor or “Mixed”). The totals cover exactly the variant rows beneath it in the file. - A Reorder Status column right after Reorder Date shows the product’s status (for example “1 out of stock · 2 due within 14 days”) and each variant’s own (Out of stock, Overdue, Due within 14 days, Later). - A product with a single variant stays one Variant row, so filtering the file to Variant rows always gives you every variant exactly once. Switch the option off for a plain list with one row per variant, for example, when you want to re-import the file elsewhere. Combined exports of several views always write one row per variant. ## Which columns come out The export follows the view, not a fixed template: whatever columns are visible, in the order you arranged them, is what the file contains. Three things never export: - The selection checkbox and the row-actions column. - The inventory burndown chart. - The Manufacturing (Assemblified) planning columns: those are calculated for the rows on screen only, so there’s nothing to write for rows the export walks past. Supply and Sales Performance views export their period columns with the same headings the table shows. ## Combining several views If you have more than one saved view, the dialog also shows Combine with other views. Your current view sits at the top, ticked and locked (it’s always included, and is marked “(current)” or “(current, edited)” if you have unsaved changes to it). Underneath, every other saved view is listed, starred ones first. Tick as many as you want. Note As soon as you tick a second view, Rows to export switches to All rows of each selected view and can’t be changed; a combined file always contains each view in full. ## Separate sheets vs. combined rows With more than one view selected, a Layout choice appears: Separate sheets: one per view. Each view keeps its own table, exactly as it would export on its own. - In XLSX you get one workbook with one worksheet per view, named after the view. Long or duplicate view names are shortened and numbered so every tab stays unique. - In CSV you get one file, with each view as its own section: a title row with the view name, that view’s header row, its data rows, then a blank line before the next view. Combined rows, sorted by SKU. One flat table for all the selected views, with an extra View column in front telling you which view each row came from. - A SKU that appears in three of the selected views produces three consecutive rows, in the order you picked the views. - The columns are the union of the selected views’ visible columns: the current view’s columns first, then any column a later view adds. - A cell is left blank when that row’s own view doesn’t show that column. Blank means “not part of this view”, not “zero”. - Rows are grouped by SKU and sorted naturally ascending; rows without a SKU follow at the end, sorted by product and variant title. Caution Supply and Sales Performance views can only go into the Separate sheets layout; their period columns don’t line up row-by-row with a standard view. If you switch the layout to combined, any such view already ticked is removed from the selection and named underneath so you can see which one went. If the view you started from is a Supply or Sales Performance view, the combined layout isn’t available at all. ## File names and progress A single-view export is named after the view and its location scope, with a timestamp, for example bestsellers-all-locations-2026-09-14-08-30-00.xlsx. A combined export is named for how many views went into it: forecast-multi-3-views-2026-09-14-08-30-00.xlsx. While a combined export runs, the dialog shows which view it’s on (Fetching “Bestsellers” (2/4)…) and stays open until it finishes. Views are fetched one at a time, so a four-view export takes roughly four times as long as one view. If any view fails to load, the whole export stops and the dialog tells you which view it was; nothing is downloaded. That’s deliberate; a half-complete file is worse than no file. Try again, or untick the view that failed. A view that simply matches no rows is not a failure: it contributes its headers and no data rows. ## See also - [Forecast view table] (/features/forecast/view-table/): the columns an export carries, and the paging controls next to the Export button. - [Views & filters] (/features/forecast/views-and-filters/): saving the filter, column, and sort combination you’re exporting. - [Group rows by product] (/features/forecast/product-view/): the product rows and reorder status that the [product summary rows] (#product-summary-rows) mirror. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/forecast/forecast-preferences/ # Forecast Preferences Shop-wide settings that control how Logistified calculates sales averages and forecasts, and what shows in the Create-PO-from-Forecast view picker. Forecast Preferences are shop-wide settings that change how Logistified computes averages and forecasts, and what appears in the view picker when you create a purchase order from the Forecast page. They live at Settings → Forecast Preferences and affect every forecast view, variant page, and report that runs after you save; existing saved views are not reset. ## On this page - History Window Divisor - Hide auto-generated views - When changes take effect - See also ## History Window Divisor When you ask for “the last 90 days” of sales but a product only has 70 days of data, something has to fill the remaining 20 days. The History Window Divisor controls what the average is divided by. It affects: - Forecast models that use a sales rate (Average, Trend, and most others). - [Days of stock] (/reference/glossary/#days-of-stock) and [DOH] (/reference/glossary/#doh) calculations. - Average daily and monthly sales columns. - Reorder point and suggested order quantity math. ### Match available history (default) Divide by the number of days the product actually has data for. A product with 70 days of history is averaged over 70 days even when you asked for 90. Use this when: you want forecasts for new or recently-listed products to reflect their actual selling rate, not an artificially low one caused by days with no data. You ask for Product has Divisor used 90 days 90 days 90 90 days 70 days 70 90 days 10 days 10 ### Use the exact requested window (strict) Always divide by the full requested window, treating days before the product had data as zero-sales days. Use this when: you want every product benchmarked against the same denominator, so a new product’s rate is naturally lower than an established product’s rate over the same window. You ask for Product has Divisor used 90 days 90 days 90 90 days 70 days 90 90 days 10 days 90 Note Neither mode is universally “correct”; the right choice depends on how you think about new-product rates in your business. Default (match available history) keeps new products from looking artificially slow. Strict keeps the denominator consistent across your catalog. ## Hide auto-generated views Creating a purchase order from the Forecast page automatically saves a snapshot of the [view] (/features/forecast/views-and-filters/#auto-generated-views) used, named after the resulting document (for example “PO-2026-0042”), so the document’s forecast stays reproducible later. Over time these snapshots can crowd out your own saved views. Turn on Hide auto-generated views in the purchase order dialog and the Use Existing View picker in the Create Purchase Order → Create from Forecast dialog will only offer views you created yourself. It doesn’t delete or hide the snapshot views anywhere else; they still appear on the Views page (under Show autogenerated) and the Overview page’s Autogenerated tab; this setting only narrows the one picker. ## When changes take effect Changes apply immediately; there is no need to reload or re-save views. The History Window Divisor mode does not change the history window you selected, only the divisor used in the average, and only affects computations that run after you save. Hide auto-generated views only changes what the Create-PO-from-Forecast dialog offers; it does not touch any existing view or PO. ## See also - [History period] (/features/forecast/history-period/): choosing the window itself (how far back to look). - [Forecast models] (/features/forecast/forecast-models/): which models use the sales-rate average. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): how the average feeds suggested order quantities. - [Views and filters → Auto-generated views] (/features/forecast/views-and-filters/#auto-generated-views): what auto-generated views are and where else they show up. Last updated: 26 August 2026 --- Source: https://docs.logistified.app/features/inventory/overview/ # Inventory Manage stock levels, locations, and reconciliation across your Shopify store. “Inventory” in Logistified is a topic, not a single section of the app. The features grouped here live across the app: Shopify’s quantity buckets (on hand, available, committed, reserved and incoming) can be added as columns on the Forecast page (the remaining three, damaged, safety stock and quality control, are mirrored and exportable but have no Forecast column); Locations, Stock takes & adjustments settings, and Data exclusion are in Settings; Incoming reconciliation is a tab inside Settings → Variant Settings; Stock takes, Stock adjustments, and Printing Studio have their own pages under Inventory Management in the top nav. Shopify is the source of truth for every quantity. Logistified mirrors Shopify via webhook and only pushes one value back: the incoming quantity, driven by purchase-order and transfer-order state changes. Operator adjustments (PO receipt, TO shipment, stock take, stock adjustment) go to Shopify first via inventoryAdjustQuantities, then come back to Logistified through the same webhook. A periodic background check (roughly every 10 hours) catches anything the webhooks miss. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Inventory levels] (/features/inventory/inventory-levels/) The eight Shopify quantity buckets Logistified mirrors: what each one means, where it comes from, and which show on the Forecast page. [Locations] (/features/inventory/locations/) The Shopify location mirror plus app-side overrides for PDFs and labels (Settings → Locations). [Incoming reconciliation] (/features/inventory/incoming-reconciliation/) Catch drift between Logistified's expected incoming and Shopify's (Settings → Variant Settings). [Stock takes] (/features/inventory/stock-takes/) Count what you physically have and let Logistified reconcile it against the system. [Stock adjustments] (/features/inventory/stock-adjustments/) Add or remove stock by an amount, with an operator, a reason and a one-click revert. [Printing Studio] (/features/inventory/printing-studio/) Scan or pick items, set copies, and generate labels from your templates, with no purchase order required. [Data exclusion] (/features/inventory/data-exclusion/) Hide noise products from analytics, or remove them entirely (Settings → Data exclusion). ## Key concepts - [On hand] (/reference/glossary/#on-hand-quantity), [available] (/reference/glossary/#available-quantity),[incoming] (/reference/glossary/#incoming-quantity) , [committed] (/reference/glossary/#committed-quantity),[reserved] (/reference/glossary/#reserved-quantity), [damaged] (/reference/glossary/#damaged-quantity),[safety stock] (/reference/glossary/#safety-stock-quantity), [quality control] (/reference/glossary/#quality-control-quantity): the eight quantity buckets. - [Location] (/reference/glossary/#location): a Shopify location Logistified mirrors. - [Location override] (/reference/glossary/#location-override): app-side address shown on PDFs and labels. - [Incoming reconciliation] (/reference/glossary/#incoming-reconciliation): drift detection between Logistified and Shopify. - [Stock take] (/reference/glossary/#stock-take): a physical count that updates Shopify. - Stock adjustment: a signed movement (add 12, remove 3) recorded against a location, attributed to an operator and reversible in one click. - [Data exclusion rule] (/reference/glossary/#data-exclusion-rule): hides a subset of products from analytics. ## Where to next - [Guides → Run a stock take] (/guides/run-a-stock-take/): end-to-end walkthrough. - [Guides → Print product labels] (/guides/print-product-labels/): scan or pick items and print labels, no purchase order required. - [Guides → Make a stock adjustment] (/guides/make-a-stock-adjustment/): the fast add/remove path. - [Guides → Reconcile incoming inventory drift] (/guides/reconcile-incoming-inventory-drift/): fixing mismatches. - [Forecast → Locations & multi-location math] (/features/forecast/locations/): how the location filter changes the forecast. Last updated: 24 August 2026 --- Source: https://docs.logistified.app/features/inventory/inventory-levels/ # Inventory levels The eight Shopify quantity columns Logistified mirrors per variant per location. For every variant × location combination, Shopify holds eight quantity values. Logistified mirrors all eight, surfaces them on the Forecast page, and pushes one of them (incoming) back to Shopify when POs and TOs change state. This page explains what each column means, where you see it, and how the sync works. ## On this page - The eight quantity columns - Where you see these columns - How updates propagate - See also ## The eight quantity columns All eight values come from Shopify. Logistified does not hold a private copy of any of them; when you see a number here, it’s the same number Shopify has. Column What it shows Source [On hand] (/reference/glossary/#on-hand-quantity) Physically present units. Shopify [Available] (/reference/glossary/#available-quantity) Units you can still commit to new orders. Shopify (computed as on-hand minus committed minus reserved). [Incoming] (/reference/glossary/#incoming-quantity) Units on the way: open POs and TOs. Shopify. Logistified pushes deltas as POs/TOs change state; Shopify echoes the new total back. [Committed] (/reference/glossary/#committed-quantity) Reserved for orders not yet shipped. Shopify. [Reserved] (/reference/glossary/#reserved-quantity) A separate Shopify reserve bucket. Shopify. [Damaged] (/reference/glossary/#damaged-quantity) Units recorded as unsellable. Shopify. [Safety stock] (/reference/glossary/#safety-stock-quantity) Units flagged as off-limits to sales. Shopify. [Quality control] (/reference/glossary/#quality-control-quantity) Units held back for inspection. Shopify. Note There is no Logistified-only column. To change damaged, safety stock, or quality control, edit them in Shopify Admin; Logistified will pick the change up via webhook. ## Where you see these columns - Forecast page. This is the primary surface. The Forecast view’s columns can be configured to show on hand, available, committed, reserved and incoming; damaged, safety stock and quality control are mirrored and exportable but have no Forecast column. The “All locations” filter aggregates across locations. - Stock takes. When you add a line, the on-hand value is captured as the “current quantity” snapshot. - There is no dedicated “inventory ledger” page inside Logistified; the data lives on the Forecast page. Each (variant, location) pair has its own set of eight values. A variant stocked at three locations has three sets of numbers. ## How updates propagate Shopify → Logistified. Shopify fires INVENTORY_LEVELS_UPDATE webhooks for every change. Logistified usually has the new value within seconds. Logistified → Shopify. The only quantity Logistified actively writes back is incoming, and only when a PO or TO crosses a state boundary (confirmed, shipped, received). The push goes to Shopify first via inventoryAdjustQuantities; Shopify then echoes the new total back via the same webhook. So even Logistified-driven changes flow Shopify → Logistified at the end. The safety net. A periodic background check (roughly every 10 hours) compares Logistified’s mirror against a fresh read from Shopify and re-syncs anything the webhooks missed. Most drift resolves on its own within a day. When you want to inspect or fix incoming-quantity drift right now, use [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). For on-hand drift, run a [stock take] (/features/inventory/stock-takes/). ## See also - [Locations] (/features/inventory/locations/): Shopify location mirror. - [Incoming reconciliation] (/features/inventory/incoming-reconciliation/): drift detection. - [Forecast → Locations & multi-location math] (/features/forecast/locations/): how the location filter changes the math. Last updated: 19 May 2026 --- Source: https://docs.logistified.app/features/inventory/locations/ # Locations Shopify location mirror plus app-side render-time overrides for PDFs and labels. A [location] (/reference/glossary/#location) in Logistified is a Shopify location: a warehouse, a retail store, a fulfilment hub. Logistified mirrors every active Shopify location and uses them throughout the app. You can also configure app-side render-time overrides for PDFs and labels. Locations are managed in Settings → Locations; there is no Inventory page in the app. ## On this page - Location attributes - Location overrides - Setting an override - Refresh location information - See also ## Location attributes Each location has: - Name - Address line 1 and 2 - City, country, postal code - Phone - Active flag - Fulfilment-service flag These mirror Shopify. Logistified never edits the upstream Shopify location; it is read-only on the Shopify side. ## Location overrides A [location override] (/reference/glossary/#location-override) lets you change how a location appears on PDFs and labels without touching Shopify. Render-time only. Useful when: - The address on your shipping label needs to be different from your shop’s billing address. - You want a friendlier display name on supplier-facing documents. - A location is a warehouse with no public phone; use a different number for outgoing POs. ## Setting an override Settings → Locations → click a location → fill in override fields → save. The Shopify location stays untouched; the override applies when Logistified renders a PDF or label for that location. ## Refresh location information Click Refresh location information in Settings → Locations to pull the latest list. Useful after you’ve added or renamed a location in Shopify. Note Location overrides are app-only. If your finance team uses Shopify’s location list, they won’t see your overrides. Caution Refresh-from-Shopify can be slow on stores with many locations. Click once and wait. ## See also - [Inventory levels] (/features/inventory/inventory-levels/): the per-location Shopify quantity mirror. - [Forecast → Locations & multi-location math] (/features/forecast/locations/): how the location picker changes the forecast. - [Settings → Locations & overrides] (/features/settings/locations-and-overrides/): the settings page itself. Last updated: 19 May 2026 --- Source: https://docs.logistified.app/features/inventory/incoming-reconciliation/ # Incoming reconciliation Catch and fix drift between Logistified's expected incoming inventory and Shopify's. [Incoming reconciliation] (/reference/glossary/#incoming-reconciliation) compares what Logistified expects to be on the way with what Shopify currently shows as incoming. When the two disagree, the wizard lets you review the difference and apply selected corrections. ## On this page - Why drift happens - Where to find it - Pair categories - Running a reconciliation - When to use this manually - What reconciliation does not touch - See also ## Why drift happens Shopify’s incoming counter changes when a PO becomes incoming or a TO is in transit. Logistified also keeps an expected incoming value from open POs and TOs. If a Shopify update fails, is delayed, or another tool changes incoming, the two values can diverge. Background checks refresh Logistified’s inventory copy and can flag drift, but they do not automatically correct every mismatch. Use this page when you want to inspect the differences and choose what Shopify should show. ## Where to find it Open Settings → Variant Settings. The page heading is Product & Variant Settings; choose the Incoming Reconciliation tab and click Start reconciliation run. There is no “Inventory” page in the app; reconciliation lives under settings because it’s an admin task, not a daily workflow. ## Pair categories Each disagreement is categorised: Category What it means Typical cause Over Logistified expects more than Shopify shows. A previous sync didn’t take. Under Logistified expects less. An out-of-app Shopify change. Negative Shopify shows less than zero. Rare, usually a Shopify bug or a manual entry mistake. ## Running a reconciliation The flow is a wizard, not a per-row action list: 1. Click Start reconciliation run to open the wizard. Choose whether to include Over, Under, and Negative cases, then click Start. 2. The wizard loads Logistified’s expected incoming from your open POs and TOs, then runs a fresh Shopify query for each (variant, location) pair before you can apply anything. 3. You see a table with one row per mismatched pair: SKU, product/variant, location, Shopify value, Logistified expected value, Target, and the resulting delta. Filter by Over / Under / Negative if you want to focus. 4. Edit the Target column to choose what value should end up in Shopify. It defaults to Logistified’s expected value, but you can type any number, including zero if you want to clear a negative. Use Remove selected to drop rows you don’t want to push, or Reset targets to revert all targets to defaults. 5. Click Apply selected. Logistified updates Shopify so each selected pair lands on its Target value, then records that value as its latest inventory copy. After a run finishes, a Run again button appears in case more pairs surfaced while you were applying. ## When to use this manually Open this tab when: - A pair has been drifting for longer than a typical background check cycle and needs review. - You’re about to send a PO or hand off counts to a stocktaker, and want the numbers reconciled now. - A negative Shopify value is blocking another workflow and needs a deliberate human decision before being pushed up. - Another app or manual Shopify change may have touched incoming, and you want to choose the correct Target before applying. ## What reconciliation does not touch A run only changes selected incoming values in Shopify and Logistified’s inventory copy. It does not update PO or TO line items. So: - If a PO line was wrong upstream, pushing Logistified’s expected value to Shopify won’t correct the underlying PO; fix the PO directly, then run reconciliation again. - If you set a Target that does not match the underlying PO/TO plan, the same pair may appear again on a later run. Caution Pushing a Target value overwrites Shopify’s incoming number for that variant and location. If Shopify was right and Logistified’s expected value was wrong, you’ll move Shopify away from the truth. When in doubt, verify the physical count (a [stock take] (/features/inventory/stock-takes/) is the cleanest way) before applying. ## See also - [Inventory levels] (/features/inventory/inventory-levels/): the quantity values reconciliation compares. - [Purchase Orders → Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): the Shopify push that drift comes from. - [Purchase Orders → Preferences] (/features/supply-orders/purchase-orders/preferences/#incoming-inventory-tracking): the incoming-tracking toggle that controls whether POs write incoming. - [Guides → Reconcile incoming inventory drift] (/guides/reconcile-incoming-inventory-drift/): worked walkthrough. Last updated: 7 June 2026 --- Source: https://docs.logistified.app/features/inventory/stock-takes/ # Stock takes Physical inventory counts that reconcile what you have against what the system shows. A [stock take] (/reference/glossary/#stock-take) is a physical count of inventory at a location. You count what you have, enter the numbers, review the discrepancies, and apply the corrected on-hand, with the count labelled by a reason your team chose. Shopify products are updated in Shopify; virtual materials are updated in Logistified and sent to Assemblified instead. Use it whenever you need to write down what you actually have and explain why it changed: a periodic count, an audit, a shelf that never matches the system. The reason field is a free-text combobox that lets you create reasons on the fly, so every count is labelled for later auditing and reporting. If you already know what changed (4 damaged, a carton of 24 found), reach for a [stock adjustment] (/features/inventory/stock-adjustments/) instead: it records the movement itself, in a single quick dialog, and can be undone in one click. Both update inventory and share one reason list. ## On this page - The four-status lifecycle - Starting a stock take - Adding variants - Per-line columns - Filtering and status dots - Value-delta aggregates - Completing the take - Re-opening and editing - Floormode count reports - Finding past stock takes - AI search - Exporting stock takes - See also ## The four-status lifecycle Status What it means Draft Set up, nothing counted yet. Adding the first line moves the take to In Progress on its own. In Progress You’re actively counting. Can be sent back with Actions → Revert to Draft. Completed Counts saved and the take closed. Completing does not push to Shopify; Apply to Shopify does. Can be re-opened. Cancelled Abandoned. Fully terminal: no status change of any kind is possible afterwards. ## Starting a stock take The stock-takes page lives under Inventory Management in the top nav, and is also linked from the Procurement (PO&TO) page. New Stock Take is a dropdown with three ways to start: - Blank / Upload: set up an empty take, or seed it straight from a CSV / XLSX file. - From View: pick a saved view to decide which products the take includes. - From Quick Scan: scan items first, then turn the scan queue into a stock take. Blank / Upload opens the setup form: - Location. Where the count happens. - Reason. Pick from your saved reasons, or type a new one; when no existing reason matches, a Create [text] option appears in the dropdown. New reasons are saved to your library (managed in the app at Settings → Stock takes & adjustments, the same list stock adjustments use) and get an auto-assigned colour, so the next stock take can re-use them. - Name, Created by, Contact info and Notes. All optional: created-by and contact info are pre-filled from your user. Location is the only required field. Create empty saves a blank take, which sits in Draft; Next: Upload file takes you on to the CSV / XLSX step, and as soon as the file’s rows land the take promotes itself to In Progress; any take stops being a Draft the moment it has a line. (An empty Draft can also be started by hand from Actions → Start Counting; Complete only appears once the take is In Progress.) ## Adding variants Three input modes: mix freely within one take. On the take they live under Add Items: - Browse & Pick: search the products stocked at this take’s location, select variants, and type the counts. This includes virtual materials already stocked there. Search can match the product and variant together, so a phrase such as a product name followed by its colour or size finds the combined title. - Upload File: CSV / XLSX via the unified import flow, with a column-mapping step. Each row needs a SKU or Barcode plus either a Counted Qty or a Delta column; a delta is a signed adjustment to the current on-hand, so negative values record shrinkage. A Delta column only works when uploading into an existing take; the create-from-file path takes Counted Qty only and asks you to remap if it finds a delta. - Scan Barcode / SKU: swaps the search box for a scan field: fire a barcode at it with a handheld scanner (or type an SKU and press Enter) and each hit is added to the take. Capitalization does not matter; if the same code is one item’s SKU and another item’s barcode, the SKU wins. It reads keyboard input, so any USB or Bluetooth scanner works; the admin app has no camera scanner (camera scanning for stock takes lives in the [Shopify POS app] (/features/pos/overview/)). Picking Scan Barcode / SKU drops the cursor straight into the scan field as the menu closes, so back-to-back scans don’t need a click in between. Useful on the warehouse floor. Next to the scan field a small Count +1 | Confirm current switch decides what a scan records. Count +1 (the default) adds one to the line’s count on every scan, the classic tally. Confirm current records the line’s current on-hand as the count instead, so scanning a product means “the shelf matches the system” and only a discrepancy needs a typed quantity. The browser remembers your choice for the next take. Next to Add Items, an open take also carries Change View / Filters. Point the take at a different saved forecast view (or an ad-hoc filter set) and Logistified re-populates it: variants that match are added, lines that no longer match are dropped, but any line you have already counted is kept, whatever the new filters say. Note When you apply the take, Shopify products are sent to Shopify. Virtual materials have no Shopify stock to update: Logistified updates their quantity at the take’s location and sends the same movement to Assemblified. Caution Assemblified sub-assemblies (SKUs starting with ASM-) can be counted too. Applying the take sends each counted sub-assembly to Assemblified as the quantity you counted, even when it matches, and its quantity here updates when Assemblified confirms it. Count sub-assemblies after open orders are fulfilled, or adjust afterwards: the Review Changes dialog reminds you when the take contains any. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#stock-takes-and-adjustments). ### The upload preview Uploading always shows a preview before anything is imported, whether you upload into an existing take (Add Items → Upload File) or create one from a file (New Stock Take → Blank / Upload). Rows that resolve cleanly are marked to be added; on an existing take a row matching a line already there is marked as an update instead. Rows that can’t go through are flagged and left out: - Not stocked: the SKU/barcode matched a variant, but that variant has no inventory tracked at this take’s location. Hover the badge and it names the location. - N/A (or Barcode N/A): the SKU or barcode didn’t match anything in your Shopify store. Flagged rows stay visible in the preview but are never imported; the valid rows go through on their own. Clear them all in one click with Remove all not-found, or remove rows individually. If no valid rows are left, the import button stays disabled. Note “Not stocked” means the variant has no inventory level at all at the take’s location; a variant stocked there with 0 on hand imports fine. To count a flagged variant, stock it at that location in Shopify first, then re-upload. If the file contains variants already on the take, the preview asks whether the uploaded values should replace the existing counted quantities or be merged (added) into them. Rows with neither a SKU nor a barcode are skipped, with a notice telling you how many. ## Per-line columns Column What it shows Product / Variant Product title with the variant underneath, plus a Synced or Re-sync badge once the line has been applied. SKU / Barcode The identifiers captured on the line. Cost Unit cost snapshot, used for the value figures. Current The on-hand baseline the count is compared against. Captured when the line is added; a file upload re-bases it from fresh on-hand, and Refresh On-Hand (in the take’s Actions menu) updates the baseline and recalculates deltas for counted lines. Committed Units committed to open Shopify orders at this location. Delta Counted minus current. Positive = surplus; negative = shortage. Editable: type a delta here or a count in New Qty and the other follows. New Qty What you actually count. Value Change Delta × unit cost. ## Sorting the lines Click the Product / Variant, SKU or Barcode header to sort the lines; click it again to flip between ascending and descending. A take opens sorted by product, A to Z. Sorting ignores capitalization and accents and reads numbers naturally (Size 2 comes before Size 10), and lines with a blank SKU or barcode always stay at the bottom. When lines are grouped by vendor, they are sorted within each group. Hiding the sorted column returns the table to product order, the choice isn’t remembered the next time you open the take, and exports and the PDF keep their own order. Stock adjustments sort the same way. ## Filtering and status dots Above the line-item table, three controls (All, Counted, and Uncounted) switch between every line, the ones counted so far, and the ones still outstanding. Counted and Uncounted each carry a live number that includes edits you haven’t saved yet and doesn’t move when you search, so you can see at a glance how much of the take is left. Search and the group-by selector work alongside any of the three. A line becomes Counted the moment a quantity is recorded, including a plain 0, which is a real “nothing on the shelf” result and takes the line off the Uncounted list. Leave the quantity blank and the line stays Uncounted. Working straight down the Uncounted list behaves the way you’d want on the floor: the row you’re typing into stays where it is until you move focus, so a multi-digit count doesn’t make the row vanish mid-keystroke, and pressing Enter jumps to the next quantity cell. When a line’s shelf count simply matches the system figure, click the tick at the end of the row (Mark as counted) instead of typing the number. It records the current quantity as the count (delta 0, the grey “no difference” dot), the line leaves the Uncounted list, and focus lands on the next line’s tick so you can keep going. Nothing is ever pre-filled: a line only becomes counted when you type a quantity, scan it, or mark it. The tick shows only on uncounted lines of an open take, and like every other count edit it is saved with Save. Note Stock adjustments have the same strip with All and Adjusted only; there’s no Uncounted control, because an adjustment lists just the lines you put on it. Each counted line also shows a status dot: Dot Meaning Grey Counted, quantity matched, no discrepancy. Green Counted with a surplus, or successfully synced. Red Counted with a shortage. Yellow Synced once, then re-counted: needs a re-sync. ## Value-delta aggregates Every stock take carries three money figures, each line’s discrepancy priced at its unit cost: - Total value increase (surplus units × unit cost). - Total value decrease (shortage units × unit cost). - Net value change. The list shows the net per take in its Value Change column and totals all three for the current filter under the table; the PDF report prints them in its summary. On an open take, the bar under the title shows only the increase and decrease that have not been applied yet. Useful for finance teams to quantify the impact of a count. ## Completing the take 1. Save your edits; Complete stays disabled while anything is unsaved (“Save changes before completing”). 2. Review the discrepancies. 3. Apply them: Apply to Shopify opens a Review Changes dialog, and confirming writes the corrected on-hand for every changed line. The button keeps this name even when the take also contains Assemblified virtual materials. 4. A sync that applies every line completes the take for you, and the completion date is stamped. If anything is left (a line failed, or you chose not to apply yet), click Complete. Completing does not apply anything on its own; the inventory write happens through Apply to Shopify, and only lines whose change has not landed yet are sent. Shopify products go to Shopify; virtual materials update in Logistified and sync to Assemblified. A line that fails keeps its unsynced state and stays in the Apply count, so running Apply to Shopify again retries it. Note If any counted line hasn’t synced its change to Shopify yet when you click “Complete,” Logistified shows an Unsynced quantities warning instead of completing right away. You can Sync now (closes the warning and opens the Review Changes dialog so you can push the pending lines; a sync that applies them all completes the take, otherwise click Complete again), Complete anyway (finishes the take with those lines left unsynced), or Cancel. This is a heads-up, not a hard block; you can always complete. The warning never shows when nothing is left to sync. ## Re-opening and editing You can re-open a Completed stock take with Actions → Revert to In Progress; that clears the completion date so you can adjust. Useful when you realise a line was miscounted. The Actions menu also carries Start Counting (on a Draft), Revert to Draft (on an In Progress take), Clean Up (removes every line you haven’t counted), Refresh On-Hand, and Cancel Stock Take. Caution A Cancelled stock take is fully terminal; no status change is possible afterwards, not to Draft and not back to In Progress. Don’t cancel unless you really mean it. Note A completed stock take can’t be deleted. The history is preserved. ## Floormode count reports If your warehouse team counts inventory in Floormode, our companion warehouse app, an approved count arrives here automatically as a completed stock take; you don’t create or upload anything yourself. These reports are read-only. The detail page shows Approved in Floormode, with the count’s reference number and a note that valuation uses Logistified’s unit costs as of the moment the report arrived. There’s no Edit button, and the Actions menu doesn’t offer Revert to In Progress or Apply to Shopify; the correction already happened in Floormode, so there’s nothing left here to push or change. If you need a further correction, make it in Floormode; it shows up here as a new report. Everything else works the same as any other stock take: it appears in the stock-takes list, counts toward filters and value-delta totals, and exports and prints like any other report. ## Finding past stock takes The stock-takes list has a search box, an Add filter popover, and a preset switcher, with a removable chip for each active filter. Filters available: status, location, reason, vendor, Created by, and a date range; the date filter has its own column picker, so you can point it at the created, started, completed, or cancelled date. Its quick choices are Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month; Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. Created by lists the people who have actually raised a take, so you can narrow the list to one colleague’s counts. The list also carries a Created by column showing who raised each take, alongside a matching line under the title on the take itself. The search box matches the take’s number, name or creator as well as the product title, variant title, SKU or barcode of any line inside it. Useful when you have a long history of counts and need to surface a specific one for review. Save a filter set (including the search term) as a named preset shared by the whole shop; every operator sees the same saved presets, not a per-browser default. Star one preset to make it the shop default, applied automatically the next time anyone opens the list with a plain, unfiltered link. Clear all drops every filter, the search term, and the active preset in one step. ## AI search You can also describe the stock takes you want. Click into the search box and press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English and press Enter. A preview shows the filters it understood (status, location, reason, vendor (the brand of the products counted), created by, tags, and a date period on the created, started, completed or cancelled date), and nothing changes until you click Apply. For example: - “completed year-end counts at the Berlin warehouse” - “in-progress stock takes for Fjord Living” If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/) for the full walkthrough. ## Exporting stock takes Stock takes export to CSV / XLSX, in bulk from the list, or one at a time from a single take. The column set comes from a template you control (see [Settings → Stock takes & adjustments → Export templates] (/features/settings/data-export-templates/)). ### Bulk export from the list On the stock-takes list, tick rows (or the header checkbox for the whole page) and click Export. The selection persists across pages and filters; Clear selection resets it. The dialog walks four steps: scope (selected / all on this page / all filtered) → export type → format + template (CSV or XLSX) → progress. There are three export types: Type One row per Use it for Stock take level stock take A summary: status, location, reason, value change, totals, and dates. Confirmation overview (movements) line item An audit of what changed: counted quantity, delta, unit cost, and value change per line. Counting template line item A blank count sheet: the counted, delta, and value columns are exported empty, to print and fill in by hand. The Confirmation overview type adds a line-handling choice: All lines (one row per line item from every selected take), or Merged per location & SKU (combine the same SKU at the same location into one row, summing the movements, while different locations stay separate). ### Exporting a single take From an individual stock take, the Actions menu offers two spreadsheet exports (alongside a Print PDF report): - Quick export: an immediate XLSX download of either the counting template or the confirmation overview. - Export with template: the full template-driven dialog (the same three types and CSV / XLSX choice as the bulk export), scoped to that one take. ### The PDF report Actions → Print PDF produces a report of the counted lines that changed, with totals for value gained, value lost and the net change. When some lines were never counted but the system showed stock on hand for them, the report also ends with a Not counted, stock on hand section and the summary gains a matching count. It lists each such item with its on-hand quantity, unit cost and Value at risk, plus a Value at risk if missing total, the write-down you would take if that stock turned out to be gone. These items are not included in the report’s totals and nothing is adjusted for them, so re-count them before completing the take. The section lists up to 500 items; if there are more, the report says how many are not shown and points you to the Uncounted filter or the CSV / XLSX export for the full list. A fully counted take, and any stock adjustment, prints exactly as before. ### Templates Stock take export templates are configured at Settings → Stock takes & adjustments → Export templates. Because stock takes have no supplier, these are global templates with no per-supplier assignment. The counting-template export reuses the line-item template’s columns; it just exports the counted / delta / value columns blank. Sensible defaults ship for each type. The Available columns list on CSV / XLSX templates is searchable and grouped by source, with collapsible groups and a per-group Select all / Clear toggle. The line-item catalog has grown well beyond the stock-take fields: lines can now also carry full product and variant details, live inventory at each line’s own location and summed across all locations, planning constants (blank when not configured, not 0), and ABC / revenue metrics, all read from your Logistified data at export time. None of the new columns are selected by default. Because they aren’t count-derived, they aren’t blanked on the counting-template export; a printed count sheet can show live availability next to the empty count column. Line-item templates can also carry the take’s own header fields (name, status, created by, dates, notes, and totals) repeated on every line, so a single sheet can be filtered or pivoted in a spreadsheet without a second export. ## See also - [Stock adjustments] (/features/inventory/stock-adjustments/): state what changed instead of counting what’s there. - [Inventory levels] (/features/inventory/inventory-levels/): what the stock take updates. - [Settings → Data export templates] (/features/settings/data-export-templates/): column presets for the stock take exports. - [Printing Studio] (/features/inventory/printing-studio/): print product labels for any items, from the same Inventory Management page. - [Shopify POS] (/features/pos/overview/): create and count a stock take on the till, with the camera or a POS barcode scanner. - [Guides → Run a stock take] (/guides/run-a-stock-take/): end-to-end walkthrough. - [Guides → Find orders with AI search] (/guides/search-with-ai/): describe the stock takes you want instead of picking filters. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/inventory/stock-adjustments/ # Stock adjustments Add or remove stock in a few taps, with a reason, an operator, and a one-click undo. A stock adjustment moves stock by an amount: add 12, remove 3. You never type what the shelf holds, only what changed. Logistified applies exactly that movement, records who made it, and keeps the document so you can undo it later with one click. Shopify products are updated in Shopify; virtual materials are updated in Logistified and sent to Assemblified instead. It is the fast lane next to [stock takes] (/features/inventory/stock-takes/): open the dialog, pick your location, scan or add your items, hit Adjust now. Done in under a minute, with a barcode scanner, without touching the mouse. ## On this page - When to use an adjustment vs. a stock take - Creating one (the quick path) - Choosing the location - Adding items: scan, pick, upload - Adding vs. removing - Who made the adjustment - The lifecycle, if you don’t finish in one go - Reverting - Document numbers - Finding past adjustments - AI search - Exports and printing - See also ## When to use an adjustment vs. a stock take Use a stock adjustment when… Use a stock take when… You know exactly what changed: 4 units damaged, a carton of 24 found, 2 given away as samples. You don’t know what you have and need to count it. You want a fast, traceable record of a movement. You want the system to reconcile counted vs. expected and show you the discrepancies. You may need to undo it cleanly later. You’re doing a periodic or cycle count. Both update inventory and carry a reason from the same shared list; they differ in what you type. An adjustment asks how much changed; a stock take asks how much is there. Shopify products are sent to Shopify, while Assemblified virtual materials follow their material record instead. Note An adjustment can never drive a location below zero. If you try to remove more than the location holds, Logistified refuses the line and tells you how much is on hand; that situation is a counting problem, so run a stock take instead. ## Creating one (the quick path) Inventory Management → Stock Adjustments → New adjustment. The dialog opens straight onto the item list: location at the top, the scan box ready, your items underneath. 1. Pick your location. See below: one click, or nothing at all if your store has a single location. 2. Add your items and set the amounts. Scan, pick or upload them (see below), then set how much each one moved. Every row shows what’s on hand at that location and what the adjustment leaves behind, so a mistake is visible before you commit. 3. Finish. Either: - Adjust now: creates the adjustment and applies it immediately. You land on the document with everything already applied. - Save as draft: creates the document with your lines and sends nothing. Come back later, edit it, and apply when you’re ready. Everything optional (reason, a name, notes, and Adjusted by) sits behind the Details button, one click away. It never stands between you and the finish: Save as draft and Adjust now are on both screens, and Adjusted by is already filled in with your Shopify staff name. ## Choosing the location Each of your locations is a button in the middle of the empty dialog, so starting an adjustment is a single click. The location you used last is highlighted in blue and comes first. A store with one location never sees the question; it’s already chosen. If you have more than eight locations, the first eight are shown as buttons and the rest are a search away in the Location box at the top. Note On-hand is counted per location, which is why the location comes first. If you change it after adding items, Logistified asks you to confirm and then clears the list; those quantities belonged to the location you just left. [anchor: adding-items--scan-pick-upload] ## Adding items: scan, pick, upload Three ways, mix them freely in one adjustment. In the dialog all three are on the toolbar above the list: the scan box is always live (just scan, no clicking first) with Pick items and Upload beside it. Pick items opens a choice between Pick Product and Pick Virtual Material. On the saved document, the same virtual-material choice lives under Add items. Way What it’s for Pick items Use Pick Product for Shopify products or Pick Virtual Material for Assemblified materials. Search by product, variant or SKU and select several at once. Scan items Scan barcodes or SKUs. Capitalization does not matter; if the same code is one item’s SKU and another item’s barcode, the SKU wins. Every scan moves that row by one; scan the same box five times and the row reads 5. In the dialog the scan box already has your cursor, so a scanner works the moment it opens. Upload A CSV / XLSX with a SKU (or barcode) column and a signed adjustment column. Same import flow as everywhere else in Logistified, including the column-mapping step. Adding the same item twice never creates a second row. Picking an item starts its adjustment at 0; scan it twice in Add mode and that row becomes +2. Uploading a file over items already on the document is the one place you choose: the import step asks whether the uploaded amounts should replace or be added to what’s already there. Virtual materials must already be stocked at the adjustment’s location. A material with 0 on hand is valid; one with no stock record at that location is refused. If the check or save fails, the picker stays open with your selection intact so you can correct it or retry. Items that were already added during a partial attempt are skipped on the retry. Note Applying an adjustment sends Shopify products to Shopify. Virtual materials have no Shopify stock to update: Logistified updates their quantity at the chosen location and sends the same movement to Assemblified. Assemblified sub-assemblies (SKUs starting with ASM-, listed in the same picker) send the amount you add or remove to Assemblified, and their quantity here updates when Assemblified confirms it. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/). [Image: New stock adjustment Pick items menu showing Pick Product and Pick Virtual Material] (/_astro/10-stock-adjustment-virtual-material-menu.DWYGCowL_Z1aiLeb.webp) Choose Pick Virtual Material for Assemblified materials. [Image: Grafclean Matt Pastel 1L on a stock adjustment with eight units at the selected location] (/_astro/11-stock-adjustment-virtual-material-line.DO0Nb4ON_gjkII.webp) The adjustment uses stock at the selected location. ## Adding vs. removing In the dialog, every row ends with its own Add | Remove switch, and the amount you type is a plain number; the switch decides the direction. Type 5 on a row set to Remove and it becomes −5; the number turns green when stock is coming in and red when it’s going out, so a wrong direction is visible down the whole list. Flip the switch and the number flips with it, which is the one-click fix for a row you set the wrong way round. Typing a minus yourself still works and simply flips the switch for you. Scanning has its own Add / Remove toggle next to the scan box: leave it on Add to count rows up, flip it to Remove to count them down, and every scan moves the row it matches by one. It also sets the direction new rows start with, so for a batch of write-offs, flip it to Remove once, pick your ten items, and type ten plain numbers. On the document itself the amount is a plain signed number: 12 adds twelve, −3 removes three. ## Who made the adjustment Every adjustment records an operator: the Adjusted by field, prefilled from your Shopify staff account and editable before you save. It appears in the list, on the document, in the PDF and in exports, so “who removed those 40 units?” always has an answer. Adjustments made by a connected AI assistant or an API key record that connection’s name instead (for example Claude Desktop), so automated changes are as attributable as manual ones. ## The lifecycle, if you don’t finish in one go A saved draft follows the same path as a stock take: Status What it means Draft Created, no items yet. In Progress Has items; not fully applied yet. Completed Every movement was applied. Cancelled Abandoned. Terminal. Adjust now walks it to Completed for you. If a line cannot be applied (for example, a deleted variant or an item not stocked at that location), the document stays In Progress with the reason on the row, and applying again only retries what didn’t land. Nothing is ever applied twice. Lines you’ve applied are marked Synced. If you change the amount on an applied line, it flips to Re-sync and the next apply sends only the difference. ## Reverting An adjustment can be undone in one action: Actions → Revert stock adjustment. Reverting does not erase anything. It creates a new adjustment that is the exact opposite of what actually reached inventory, links the two documents together, and (if you leave Apply immediately on) applies it straight away. Your history keeps both records: what happened, and what undid it. - The two documents link both ways: the original shows Reverted by SA-…, the new one shows Reverts SA-…. - If you delete the revert before applying it, the original becomes revertible again. - A revert can itself be reverted. Revert is unavailable (with the reason in a tooltip) when there is nothing to undo: the adjustment was never applied, it still has unpushed lines (apply or clear them first), it’s cancelled, or it has already been reverted. Caution Deleting an applied adjustment does not put the stock back; it only removes the record. Use Revert to undo the movement. ## Document numbers Adjustments get their own running number, separate from stock takes. Until you choose a format they look like SA-20260817-4821. Turn on a clean sequence (SA-000001, SA-000002, …) at Settings → Document numbering → Stock adjustments; a note bar on the list links you there until you do. ## Finding past adjustments The adjustments list has a search box, an Add filter popover, and a preset switcher, with a removable chip for each active filter. Filters available: status, location, reason, vendor, Created by, and a date range; the date filter has its own column picker, so you can point it at the created, completed, cancelled, or applied date. Its quick choices are Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month; Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. The search box matches the adjustment’s number, name, operator, product, or SKU. Created by is its own thing, separate from Adjusted by: the creator is the Shopify staff account that raised the document, while Adjusted by is the free-text operator name you can edit. Both have their own column on the list, and the creator also appears as a line under the title on the adjustment itself. Save a filter set (including the search term) as a named preset shared by the whole shop; every operator sees the same saved presets, not a per-browser default. Star one preset to make it the shop default, applied automatically the next time anyone opens the list with a plain, unfiltered link. Clear all drops every filter, the search term, and the active preset in one step (the Adjusted by operator, when it’s set on the URL, isn’t part of this and isn’t cleared by it; see [Who made the adjustment] (#who-made-the-adjustment)). Note Filtering by the applied date now correctly matches when the adjustment was pushed to Shopify. A saved link or bookmark you made before this fix that looked like an applied-date filter was quietly matching the creation date instead; if your applied-date results look different than before, this is why. ## AI search You can also describe the adjustments you want. Click into the search box and press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English and press Enter. A preview shows the filters it understood (status, location, reason, vendor (the brand of the products adjusted), Created by, tags, and a date period on the created, completed, cancelled or applied date), and nothing changes until you click Apply. For example: - “adjustments for damaged goods at the Munich outlet” - “adjustments applied this month” If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/) for the full walkthrough. ## Exports and printing - Export (from the list or a single adjustment) offers Movements (one row per line with the amount, unit cost and value change) and Adjustment level (one row per adjustment with its totals, reason, operator, net quantity change and both revert links). CSV or XLSX, columns from a template you control. - Print PDF produces a Stock Adjustment Report with the operator, reason and every movement. ## See also - [Stock takes] (/features/inventory/stock-takes/): count what you have instead of stating what changed. - [Inventory levels] (/features/inventory/inventory-levels/): what an adjustment updates. - [Settings → Data export templates] (/features/settings/data-export-templates/): column presets used by the exports. - [Guides → Make a stock adjustment] (/guides/make-a-stock-adjustment/): the short walkthrough. - [Guides → Find orders with AI search] (/guides/search-with-ai/): describe the adjustments you want instead of picking filters. Last updated: 16 October 2026 --- Source: https://docs.logistified.app/features/inventory/printing-studio/ # Printing Studio Scan or pick items, set copies per item, and generate labels from your templates, saving them to a re-downloadable print run. Printing Studio is Logistified’s self-service label-printing workspace, reached from Inventory Management in the top nav and available on every plan. Scan or pick the items you want labels for, set how many copies of each, pick a template (or your shop’s default look), and generate; no purchase order is required. The generated file is saved on the run so you can find and re-download it later. ## On this page - Quick create vs. a saved print run - Quick create - Starting a print run - Adding items - Copies - Label settings - Field mapping for designer templates - Preview - Generating labels - Finding past print runs - Edge cases - See also ## Quick create vs. a saved print run There are two ways to print: - Quick create: the fast path. Scan or pick a handful of items, set copies, and print right away. Nothing is kept in your history unless you choose to save it. - A saved print run: open a run, add items from any of four sources, adjust settings, and generate. The run and every file you generate from it stay in your print history for later re-download. Both use the same rendering pipeline, so the labels look identical either way. ## Quick create Click Quick create on the Printing Studio page. 1. Add items: scan or type a barcode/SKU in the scan bar, click Pick from Shopify, or Upload CSV/XLSX. Re-scanning an item you already added adds one more copy instead of a duplicate row. 2. Set copies: edit the number on each row, or tick rows and use Set selected copies → Apply to set them all at once (newly added items come pre-selected; Set selected to 1 resets them). 3. Choose a template (or leave it on Simple mode, your shop’s default look), an output format, and optionally a currency override. 4. Click Print to generate and open the file without keeping any record, or Save & Print to also create a print run you can find again later. ## Starting a print run Click New print run on the Printing Studio page. It opens straight into an empty run so you can start adding items. Runs are numbered automatically (PR-00001, PR-00002, …). ## Adding items A run’s Add items menu offers four sources; mix and match freely. Re-adding an item you’ve already added, from any source, increases its copies rather than creating a duplicate row: - Pick from Shopify: browse and select products or variants. - Scan Items: scan or type a barcode/SKU, one at a time. Each scan adds one copy. - Upload CSV/XLSX: a CSV, XLS, or XLSX file (up to 20 MB) with a SKU or barcode column (SKU wins when a row has both) and an optional copies column (defaults to 1 when left out). Long files are fine; the upload is committed in batches automatically, with a progress readout while it runs. Rows whose SKU or barcode doesn’t match anything in your store are flagged before you commit and are skipped. - Virtual Materials: for Assemblified virtual materials, if you use them. The items table shows each row’s product, SKU, barcode, and copies, with its own search box for long runs. ## Copies Each row’s Copies field is how many labels print for that item, a whole number from 1 to 20,000. Three ways to set it: - Edit the number directly in the row. - Tick rows, type a number into Set copies, and click Apply to set many at once. - Re-add the same item from any source; copies accumulate. ## Label settings From the run’s Label settings panel: - Name (optional): to tell runs apart in your history. - Template: Simple mode (shop defaults) or one of your saved designer templates. - Output format: PDF (labels), CSV (spreadsheet), or XLSX (spreadsheet). - Price currency override (optional): force every label on this run to one currency. - Notes (optional). Click Save settings to persist your changes to the run. (Generating always saves your current settings first, so the file matches what’s on screen.) Note CSV and XLSX always export a fixed spreadsheet column set; the template you pick only affects PDF labels. Tip Designer templates and the Simple-mode toggles are configured at [Settings → Label printing] (/features/settings/label-printing/). Printing Studio uses whatever you’ve set up there (including the PDF page layout on that page’s Preferences tab) plus whichever saved template you pick per run. ## Field mapping for designer templates A designer template can reference fields that normally come from a purchase order: supplier, location, and similar. A scanned or picked item only carries product and variant information, so if your chosen template references one of those fields, a Field mapping panel appears letting you decide, per field: - Leave blank: the field prints empty. - Fixed value: type a value to use for every label in this run. - Map to column: substitute a product/variant field instead (for example, use SKU where the template expects a supplier reference). The preview reflects the mapping immediately; it’s saved with the run when you click Save settings (generating saves it too). Metafield fields are not in this panel. A designer field bound to a Shopify product or variant metafield fills itself with the live value from Shopify at print time (on Quick Print, Save & Print, and when you regenerate a saved run), so there’s nothing to map. If Shopify has no value for an item, a fallback you saved on the run in an earlier version is still used where one exists; anything left over prints blank. The warning after printing says which of the two happened, so “blank label” and “fell back to the old value” are never confused. ## Preview For PDF runs, a live preview shows what a single label looks like with your current settings and field mapping, updating as you change them. It always renders one sample item rather than a row from the run; it’s there to check the layout, not the data. CSV/XLSX runs don’t show a preview since there’s no label to render. ## Generating labels Click Generate labels (the run needs at least one item). Logistified renders the file and saves it to the run. A PDF opens in a new tab ready to print; CSV/XLSX downloads immediately. You can generate again any time (for example after adding more items), and every file you’ve generated stays listed under Generated files for that run, named after the run number (e.g. PR-00007-labels-60pcs.pdf). Note A PDF is capped at 20,000 labels. Past that, the Generate button is blocked with “Reduce the run to 20,000 labels or choose CSV/XLSX.” Lower the copies, split the run, or switch the output format to CSV/XLSX. ## Finding past print runs The Printing Studio list shows every run with its status, item and label counts, output format, generated files, and when it was last updated; the list is sortable by run number, status, items, labels, and last-updated. Search by run number, name, SKU, barcode, or product, and filter by status. Each row’s Download link grabs the run’s most recent file without opening the run (it reads Download (2), and so on, when a run has more than one file). ### Statuses Status What it means Draft Created; items may or may not be added yet. Generating A file is being produced. Completed At least one file has been generated. If a generation fails, the run returns to the status it had before; a completed run stays Completed. (The status filter also offers Cancelled. No screen in Logistified sets that status; only an assistant connected through [AI / Agent access] (/features/agent-access/overview/) with write access can.) ## Edge cases - Deleting a print run removes it from your list. Files you already generated stay in storage, but you can no longer reach them from Logistified once the run is deleted; this can’t be undone. - A file you’ve already generated is fixed; later changes in Shopify don’t rewrite it. But every new generation fetches each item’s current price, cost, and barcode from Shopify, the same live-data rule as [Settings → Label printing] (/features/settings/label-printing/). If Shopify can’t be reached, the labels fall back to the values stored when the item was added, and you’ll see a warning. - If an item is later deleted from Shopify, its row stays on the run and files you already generated are unaffected. ## See also - [Settings → Label printing] (/features/settings/label-printing/): configure the Simple-mode defaults, designer templates, and PDF page layout Printing Studio uses. - [Stock takes] (/features/inventory/stock-takes/) and [Stock adjustments] (/features/inventory/stock-adjustments/): the other tools on the Inventory Management page. - [Guides → Print product labels] (/guides/print-product-labels/): end-to-end walkthrough. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory/data-exclusion/ # Data exclusion Hide noise products from analytics: advisory rules and a destructive deletion option. Data exclusion lets you hide certain products from Logistified’s analytics, for example, archived items that would clutter the forecast. There are two flavors: advisory rules (filters that hide items) and a destructive deletion option (which actually removes products). They look similar but behave very differently. Both live in Settings → Data exclusion; there is no Inventory page in the app. ## On this page - The always-on filter - Advisory rules - Where rules take effect - Adding a rule - Destructive data deletion - See also ## The always-on filter By default, Logistified hides products whose Shopify status is archived or draft. You can’t opt out of this; these products would distort every metric. ## Advisory rules You can add custom [data exclusion rules] (/reference/glossary/#data-exclusion-rule) that hide products matching: - A tag - A vendor - A product type - A category Rules are advisory; every page that reads them applies them. If a page forgets, the rule doesn’t take effect there. Removing a tag (or otherwise making a product no longer match a rule) restores it automatically the next time Shopify sends an update, even for a product that was previously removed with the deletion option below. A product that matches a rule and was never synced in the first place isn’t stored at all, so it won’t show up in any counts on the settings page. ## Where rules take effect Surface Applies exclusion rules Forecast Yes Reports Yes Notifications Yes Purchase Orders No Stock takes No ## Adding a rule Settings → Data exclusion → “Add rule” → pick column + value(s). Save. ## Destructive data deletion The settings page also exposes a more drastic action: delete matching products from Logistified entirely. What it does: - Physically removes products matching your rule from Logistified. - Skips variants that appear on a PO line item: those get marked as deleted instead, preserving the audit trail. What it does not do: - Does not touch Shopify. The products stay in Shopify. Danger Deletion is irreversible. The only way to bring deleted data back is to re-sync from Shopify (Settings → Data Import → “Re-sync”), which loses any Logistified-side changes you’ve made (forecast tuning, supplier links, custom fields). Note Most operators only use the advisory rules. Deletion is for rare cleanup needs, for example, “we accidentally synced 50,000 archived test products at install.” ## See also - [Settings → Data exclusion] (/features/settings/data-exclusion/): the actual settings page. - [Order exclusion] (/features/settings/order-exclusion/): the sibling Orders tab; filters orders (not products) out of the forecast without deleting them. - [Forecast → Overview] (/features/forecast/overview/): where exclusion rules show their effect. Last updated: 27 July 2026 --- Source: https://docs.logistified.app/features/inventory-planning/overview/ # Inventory Planning Plan demand you know is coming, launch new products, set sales goals and mark yearly events, all in one place. [Enhanced plan] (/reference/subscription-plans/) Inventory Planning is where you tell Logistified about the future. Your forecast learns from what you sold in the past, but some things it can’t see coming: a customer who has promised a big order, a product you haven’t launched yet, a sales goal for next season, or Black Friday. Inventory Planning lets you write those down, and the forecast and your reorder suggestions take them into account. New Product Planning and Promotional Events come with the Enhanced plan. Inventory Commitments and Sales Plans need Elevate. See [Plan requirements] (#plan-requirements). ## On this page - What Inventory Planning is - The three plan types - Promotional Events - The hub - Which plan should I use? - What you can do here - Where to find it - Plan requirements - See also ## What Inventory Planning is A plan is a list of products with quantities and dates. You create it as a Draft, check it, and Confirm it when you’re sure. From then on it does its job: depending on its type, it adds expected demand to the forecast or shows a goal to measure your sales against. When it has played out, you Complete it. Every plan type shares the same statuses, described in [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). Each plan gets a plan number: IC-… for an inventory commitment, SP-… for a sales plan, NP-… for a new product plan. ## The three plan types Inventory Commitments Sales Plans New Product Planning What it’s for Demand you expect on top of normal sales: a wholesale order, a contract, a promotion, a tender A sales goal per product for a period, such as next season A product you haven’t sold yet, forecast from the launch of similar products Feeds the forecast? Yes, while Confirmed or Locked Never. Its targets are shown next to the forecast for comparison Yes, while Confirmed or Locked and Feed into forecast is on Locations Each item has its own location, or none One or more locations, each with its own targets One or more launch locations, each with its own curve Orders it can create Purchase order, transfer order, Shopify draft order None. Orders follow the forecast Purchase order Analytics No An Analytics tab: plan vs actual sales An Analytics tab: plan vs actual sales Plan needed Elevate Elevate Enhanced or Elevate Details: [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/) explains exactly what each type does to your forecast, and [Order stock for a plan] (/guides/order-stock-for-a-plan/) explains how each type leads to orders. ## Promotional Events Promotional Events sit next to the three plan types but aren’t plans. A promotional event is a holiday or sale that comes back every year, such as Black Friday or Christmas. You give it an expected uplift, switch it on, and every forecast expects that much more demand on its dates. It has no statuses and no products to add. See [Promotional events] (/features/inventory-planning/promotional-events/). ## The hub Click Inventory Planning in the top navigation to open the hub. - Four tiles: Inventory Commitments, New Product Planning, Sales Plans and Promotional Events. Each tile opens its list and shows how many are active. For the plan tiles, active means Draft, Confirmed or Locked. For Promotional Events, it means events that aren’t archived. - Recent plans: below the tiles, the ten plans you changed most recently, of all three types. Each row shows a Type chip (IC, NP or SP), the plan number and name, a short Info line, the Status and when it was Updated. Click a row to open the plan. On a commitment the Info line counts items and ends with the target date (for a date range, its last day), for example “3 items · 120 est. units · Target Jul 1, 2026”. On a sales plan or launch plan it counts products instead, for example “1 product · 1 est. unit”. - Search all plans…: type a name, plan number, SKU or product title to search every plan, whatever its type. The recent plans are replaced by the ten most recently changed plans that match, for as long as the box has text in it. - View All Commitments, View All Launch Plans, View All Sales Plans: shortcuts to the three lists, next to the search. Promotional events don’t appear in the recent plans or the hub search. Open them from their tile. When your shop has no plans yet, the recent plans are replaced by four buttons: Create an Inventory Commitment, Create a Launch Plan, Create a Sales Plan and Add a Promotional Event. ## Which plan should I use? - A customer has told you about a large order before placing it, or you’ve signed a contract, won a tender or planned a promotion for specific products: use an [inventory commitment] (/features/inventory-planning/commitments/overview/). It adds the expected units to your forecast, so you reorder in time. - You want to set a goal for how much each product should sell next season, and see whether you’re on track: use a [sales plan] (/features/inventory-planning/sales-plans/overview/). It never changes the forecast, so it can’t make you overbuy. - You’re launching a product with no sales history: use [New Product Planning] (/features/inventory-planning/new-product-planning/overview/). It borrows the launch of similar products you already sell, so the new product gets a forecast from day one. - The extra sales come back every year on the same holiday: use a [promotional event] (/features/inventory-planning/promotional-events/) instead of a new commitment each year. Tip Not sure whether to use a commitment or a sales plan? Ask yourself whether you’d buy stock for it. If yes, it’s a commitment: the forecast should count it. If it’s a target you hope to reach, it’s a sales plan. ## What you can do here [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/) Draft, Confirmed, Locked, Completed and Cancelled, and how to move a plan between them. [Search, filters & saved views] (/features/inventory-planning/search-and-filters/) Find plans and events on the lists, filter them and save filter sets for the whole team. [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/) What each plan type does to your forecast and reorder suggestions. [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/) Export plans as PDF or spreadsheet, attach files and follow every change. [Adding products to a plan] (/features/inventory-planning/adding-products/) The ways to add products, and why each product can be in a plan only once. [Plans at several locations] (/features/inventory-planning/locations/) Plan sales and launches per location, and edit all locations at once. [Plan analytics] (/features/inventory-planning/plan-analytics/) Compare a sales plan or launch plan with what actually sold. [Inventory Commitments] (/features/inventory-planning/commitments/overview/) Expected demand from big orders, contracts and promotions. [Creating a commitment] (/features/inventory-planning/commitments/creating/) Create one by hand, or several at once from a spreadsheet. [Items, dates & probability] (/features/inventory-planning/commitments/items/) Add products to a commitment and set their quantities, locations, dates and likelihood. [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/) Turn a commitment into purchase orders, a transfer order or a Shopify draft order. [Sales Plans] (/features/inventory-planning/sales-plans/overview/) Sales goals per product and location, measured against what sells. [Creating a sales plan] (/features/inventory-planning/sales-plans/creating/) The step-by-step setup: plan window, locations, growth and products. [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/) How targets are built from last year and how to change them. [The plan grid] (/features/inventory-planning/sales-plans/plan-grid/) Edit a sales plan week by week or month by month. [New Product Planning] (/features/inventory-planning/new-product-planning/overview/) Forecast a product you haven't sold yet. [Creating a launch plan] (/features/inventory-planning/new-product-planning/creating/) Pick the new products, the similar products and the launch date. [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/) How the launch curve is built and how to shape it. [Size groups] (/features/inventory-planning/size-groups/) Plan the sizes of one product together with a size split. [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/) Create the purchase order that covers the launch. [Promotional events] (/features/inventory-planning/promotional-events/) A yearly calendar of holidays and sales that lifts the forecast. [Settings] (/features/inventory-planning/settings/) Demand types, reason codes, sources, export templates and plan numbers. For step-by-step help with a whole job, see the guides: - [Plan for a large order with an inventory commitment] (/guides/plan-for-a-large-order/) - [Build a sales plan for next season] (/guides/build-a-sales-plan/) - [Plan a product launch] (/guides/plan-a-product-launch/) - [Plan sizes together with a size group] (/guides/plan-sizes-with-a-size-group/) - [Check how a plan is doing] (/guides/check-how-a-plan-is-doing/) - [Order stock for a plan] (/guides/order-stock-for-a-plan/) - [Set up promotional events] (/guides/set-up-promotional-events/) ## Where to find it Inventory Planning is in the top navigation of Logistified. Its settings are under Settings › Inventory Planning, see [Inventory Planning settings] (/features/inventory-planning/settings/). ## Plan requirements Which subscription plan you need depends on the feature: Feature Plan New Product Planning (launch plans) [Enhanced] (/reference/glossary/#enhanced-plan) or [Elevate] (/reference/glossary/#elevate-plan) Promotional Events Enhanced or Elevate Inventory Commitments Elevate Sales Plans Elevate Inventory Planning settings Every plan On the hub, a tile your plan doesn’t include shows the plan it needs: Enhanced or Elevate. The tile still opens its list. If your plan doesn’t include a feature, for example after a downgrade: - You can still open and review its plans or events. Plans also open from Recent plans and Search all plans… on the hub. - You can’t create, edit or delete them, or change a plan’s status. Create buttons are greyed out; pointing at one says, for example, “New Product Planning is available on the Enhanced Plan”. A plan’s status buttons are hidden, and a banner names the plan you need (“Sales Plans is part of the Elevate Plan and isn’t available on lower plans”), says what stays locked and links to Upgrade plan. - You can still export and download plans. Attaching the printout to the plan’s documents needs the feature’s plan. - The forecast leaves them out. Commitments feed the forecast only on Elevate. Launch plans feed it, and promotional events lift it, only on Enhanced or Elevate. Sales plans never change the forecast, and their targets in the Supply view need Elevate. Nothing is deleted. Once you upgrade, your plans and events work as before, in the forecast too. See [Subscription plans] (/reference/subscription-plans/). ## See also - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): what each plan type does to your forecast. - [Supply view] (/features/forecast/supply-view/): see planned demand and sales plan targets period by period. - [Subscription plans] (/reference/subscription-plans/): which plan includes each feature. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/inventory-planning/lifecycle/ # Plan statuses & lifecycle The five statuses every inventory commitment, sales plan and launch plan goes through, and what changes at each one. [Enhanced plan] (/reference/subscription-plans/) In Logistified, inventory commitments, sales plans and launch plans all move through the same five statuses. The status decides whether you can still edit the plan, and whether it counts in your forecast. This page is the reference for all three plan types; where a type behaves differently, it says so. Launch plans come with the Enhanced plan. Inventory commitments and sales plans need Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - The five statuses - Moving a plan along - What you can edit in each status - Which statuses feed the forecast - A target date is needed to confirm - Window elapsed - Completing early - Completed vs Cancelled - Deleting a plan - Leaving a plan with unsaved changes - Notes - See also ## The five statuses Status What it means Draft You’re still working on the plan. Edit it freely. It doesn’t count anywhere yet. Confirmed The plan is live. A commitment adds its demand to the forecast, and so does a launch plan while Feed into forecast is on; a sales plan shows its targets next to the forecast. You can still edit it. Locked Nothing can be edited any more, but the plan stays live exactly like a Confirmed plan. Use it when the numbers are final and nobody should change them by accident. Completed The plan played out. It’s closed and no longer counts in the forecast. You can reopen it. Cancelled The plan didn’t happen. It’s closed for good and can’t be reopened. Each status has its own coloured badge on the lists and on the plan page. At the top right of every plan page, a status stepper shows the four steps Draft, Confirmed, Locked and Completed, with the current one highlighted. Point at a step to see what it means for this plan. A cancelled plan has no highlighted step: its Cancelled badge shows the status instead. ## Moving a plan along On a plan page, the buttons sit on the same row as the tabs. While the plan can be edited, an Edit details button sits next to them. - The next-step button is the prominent one. It always offers the natural next step: Current status Button Moves the plan to Draft Confirm Confirmed Confirmed Lock Locked Locked Complete Completed Completed Reopen Confirmed - The Actions menu holds every other move the plan allows, plus editing, ordering, exporting and Delete. All moves between statuses: From You can move it to Draft Confirmed (Confirm), Cancelled (Cancel) Confirmed Locked (Lock), Completed (Complete), Draft (Back to Draft), Cancelled (Cancel) Locked Confirmed (Release), Completed (Complete), Cancelled (Cancel) Completed Confirmed (Reopen) Cancelled Nothing Three moves go backwards, and each does something different: - Release moves a Locked plan back to Confirmed, so it can be edited again. It stays live the whole time. - Back to Draft moves a Confirmed plan back to Draft. A commitment, or a launch plan that feeds the forecast, stops counting until you confirm it again. - Reopen moves a Completed plan back to Confirmed, and it counts again. Each menu entry has a one-line description that says what the move does to this plan, so check it before you click. Logistified confirms each move with a message such as “Status changed to Confirmed”. Cancel always asks first, because a cancelled plan can’t be brought back. The “Cancel this plan?” dialog says “A cancelled plan cannot be reopened.” (and, while the plan feeds the forecast, that its planned demand leaves the forecast). Click Cancel plan to go ahead, or Keep plan. Changing a plan’s status never changes the orders you already created from it. They stay as they are. ### Confirm a plan A plan needs a date before you can confirm it: a Target date on a commitment, a Plan window on a sales plan, or a Default launch date on a launch plan. 1. Open the plan from its list or from the hub. The status stepper shows Draft. 2. Click Confirm. If the button is greyed out, point at it to see why. Once confirmed, the stepper moves to Confirmed and the next-step button becomes Lock. 3. Optional: once the numbers are final, click Lock so nobody changes them by accident. The stepper moves to Locked. ## What you can edit in each status You can edit a plan only while it’s Draft or Confirmed: its details, its products and quantities, its dates and its documents. In the other statuses the plan is read-only. On commitments and sales plans, a “Read-only” banner under the tabs says why: - Locked: “This plan is Locked. Release it to make changes.” Release moves it back to Confirmed. - Completed: “This plan is Completed and is read-only. Reopen it to make changes.” - Cancelled: “This plan is Cancelled and can no longer be changed.” Some actions still work on a read-only plan: exporting, opening linked orders, and moving the plan to another status. A commitment can create orders in any status, including Completed and Cancelled. A launch plan can create a purchase order while it’s Draft, Confirmed or Locked. On a commitment, Exclude from forecast also works while it’s Locked. ## Which statuses feed the forecast Only Confirmed and Locked plans count. Draft, Completed and Cancelled plans never do. What “count” means depends on the plan type: - Inventory commitments add their expected quantities to the forecast as future demand, unless you excluded the commitment from the forecast. - Launch plans add their launch curve to the forecast, as long as Feed into forecast is on. - Sales plans never add demand. Their targets are only shown next to the forecast, so you can compare. [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/) explains each case in detail. ## A target date is needed to confirm A plan can only be confirmed when it has a date of its own. If it has none, Confirm (and Reopen on a Completed plan) is greyed out with the reason: “Set a target date on this plan first. Items with no date of their own can’t be placed on the forecast timeline.” On a commitment, the Details card also shows “Required before this plan can be confirmed” under Target date. Why: an item without its own date uses the plan’s date. Without either, the forecast wouldn’t know when the demand happens, and the plan would look confirmed while counting for nothing. For the same reason, you can’t remove the last date from a plan while it’s Confirmed or Locked. Move it back to Draft first. A plan also needs something in it. On an empty Draft, Confirm is greyed out with a reason such as “This sales plan has no products. Add at least one product before confirming.” A commitment needs at least one item, a sales plan or launch plan at least one product. This only applies to confirming a Draft: a plan that was emptied later can still be released or reopened. ## Window elapsed When the dates of a Draft, Confirmed or Locked plan have all passed, the list shows an amber Window elapsed badge next to its status. It’s a reminder only: nothing changes on its own. Point at the badge to see when the window ended and what to do. - Inventory Commitments: “Demand window ended date. This plan can be completed.” A Draft commitment says “Confirm it to track results, or cancel it.” instead. - Sales Plans: “Plan window ended date. Mark it Completed to close it out.” A Draft sales plan says “Confirm it to track results, or cancel it.” instead. A window that ends today hasn’t elapsed yet. “Today” is the day in your store’s time zone from Shopify (UTC when it can’t be read), so the badge appears once your store’s last window day is over. The New Product Planning list doesn’t show this badge. ## Completing early If you complete a plan while its dates are still running, Logistified asks first with “Complete this plan early?”. The message names the last day of the plan’s window (for example “Its demand window runs until Oct 30, 2026.”) and says what completing changes for this plan: - A commitment or a launch plan that feeds the forecast: its remaining planned demand leaves the forecast. - A sales plan: the forecast quantities stay the same. Only its remaining targets disappear from the sales plan comparison in the forecast. - A plan that doesn’t feed the forecast (an excluded commitment, or a launch plan with Feed into forecast off): nothing changes in the forecast. Click Complete to go ahead. You can reopen the plan later. A plan whose window has already passed completes straight away, without the question. What Complete means per plan type: - Inventory commitment: the plan played out as planned. - Sales plan: the period is closed. Its attainment figures on the Analytics tab stay available. - Launch plan: the product has launched, and the plan stops feeding the forecast. From now on the product’s own sales drive its forecast. If you’d rather stop the plan automatically, see “Stop feeding on first real sale” in [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/#launch-plans-follow-their-curve). ## Completed vs Cancelled Both close a plan, and neither counts in the forecast any more. The difference is what happened: - Completed means the plan happened. You can Reopen it later if you closed it too soon. - Cancelled means it didn’t happen. That’s final: a cancelled plan can’t be reopened. A Completed plan can’t be cancelled directly; reopen it first if it really didn’t happen. Completing a plan whose dates have already passed changes nothing in the forecast, because demand in the past never counts anyway. Completing keeps your list tidy and stops the Window elapsed reminder. ## Deleting a plan - From the list: on the Inventory Commitments and Sales Plans lists, open a row’s … menu and choose Delete. It’s offered only for plans in Draft, Completed or Cancelled. The New Product Planning list has no row menu. - From the plan page: Actions › Delete works in any status. Logistified asks you to confirm first: “Delete this plan?” says “This removes the plan and its items. This cannot be undone.” (and, while the plan feeds the forecast, that it will no longer feed it). A deleted plan disappears from every list and stops feeding the forecast. Orders you created from it stay as they are. To keep a record of a plan that didn’t happen, cancel it instead. ## Leaving a plan with unsaved changes If you try to leave a plan page while a change is still being saved, an “Unsaved changes” dialog warns: “A save is still in progress. If you leave now it may not complete.” Choose Stay or Leave without saving. On a sales plan, the same dialog also appears when you’ve changed numbers in the grid without saving them. On a launch plan it appears when the plan has unsaved changes on the Plan tab, including settings in a size group’s panel that you haven’t saved with Save & rebuild. While a sales plan or a launch plan has unsaved changes, Lock, Complete and Cancel are greyed out with “Save or discard your changes first”. ## Notes Every plan has a Notes section on its details card. Click the text to edit it in place; it saves when you click away. Notes can be edited while the plan is Draft or Confirmed, and every change is recorded on the Activity tab. ## See also - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): what each status means for your forecast. - [Inventory Commitments] (/features/inventory-planning/commitments/overview/), [Sales Plans] (/features/inventory-planning/sales-plans/overview/) and [New Product Planning] (/features/inventory-planning/new-product-planning/overview/): the three plan types. - [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/): the Activity tab records every status change. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/search-and-filters/ # Search and filter plans and promotional events Find plans and promotional events with search, filters, AI search and shop-wide saved presets. [Enhanced plan] (/reference/subscription-plans/) In Logistified, the Inventory Commitments, Sales Plans, New Product Planning and Promotional Events lists share one toolbar: a search box (with AI search, once it’s enabled for your shop), filters, and named presets that save a filter set for everyone in your shop. New Product Planning and Promotional Events come with the Enhanced plan. Inventory Commitments and Sales Plans need Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - The four lists - Searching - Filters - AI search - Saved presets - Page size - Walkthrough: find every confirmed commitment due next month - See also ## The four lists Open Inventory Planning and click a tile to open its list. List Columns Inventory Commitments Commitment, Location(s), Items, Total est. qty, Expected qty, Status, Target date, Updated Sales Plans Sales plan, Locations, Products, Target units, Status, Plan window, Updated New Product Planning Plan, Product, Launch, Status, Projected units, Forecast Promotional Events Event, Next occurrence, Repeats, Uplift, In forecasts Each list is described on its own page: [Inventory Commitments] (/features/inventory-planning/commitments/overview/), [Sales Plans] (/features/inventory-planning/sales-plans/overview/#the-list), [New Product Planning] (/features/inventory-planning/new-product-planning/overview/) and [Promotional events] (/features/inventory-planning/promotional-events/). The count under each list’s title reads, for example, “(34 total)”. While a search or filter is active it compares the matches with all plans or events of that list, for example “(3 of 34)”. Sorting. On the three plan lists, click a sortable column header to sort by it: once for ascending, again for descending, a third time for the default order, newest first. The sortable columns are the plan column, Status (in lifecycle order, Draft first), the date column (Target date, Plan window or Launch) and Updated. The plan column’s arrow menu picks Name, Plan number or Created date. Plans without a value sort last, and the sort is kept when you change filters or presets. Quantity columns aren’t sortable. On Inventory Commitments and Sales Plans, an amber Window elapsed tag next to the status means the plan’s dates are over but it is still open. Hover it for what to do. See [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). ## Searching Type into the search box. The list updates shortly after you stop typing; the × in the box clears it. List Placeholder What it finds Inventory Commitments, Sales Plans, New Product Planning “Search by name, plan #, SKU, or product…” The plan’s name or plan number, and the SKUs and product titles in it Promotional Events “Search events by name…” The event’s name So searching MUG-01 on Sales Plans lists every sales plan with that SKU. The search term, the filters and the sort are part of the page’s address, so a bookmarked or shared link opens the same list. Reloading the page in the Shopify admin keeps them too, including a filter where you ticked several values. ## Filters Click Filter and pick a field. For Status, Location and Category, tick the values and click Apply. For a date filter, pick a quick range, or click a start and an end day in the calendar: the filter applies as soon as the range is complete. Each active filter shows as a chip below the toolbar: click it to change it, or its × to remove it. Clear all removes every filter and the search term. Filter Lists What it matches Status The three plan lists One or more of Draft, Confirmed, Locked, Completed and Cancelled. Location The three plan lists Plans with something planned at one of the locations you pick. A sales plan is also found at every location it covers, even one where it has no products yet. Created The three plan lists When the plan was created. Target date Inventory Commitments The commitment’s target date. For a date range, its end. Plan ends Sales Plans The last day of the plan window. Launch date New Product Planning The plan’s default launch date. Category Promotional Events Holiday, Promotion, Sales event or Other. The date filters only look at the plan’s own dates. Dates set on single items or locations aren’t filtered on. Date ranges. Every date filter offers custom from and to dates, and quick ranges: Today, Last 7 days, Last 30 days, Last 365 days, This month and Last month. Target date, Plan ends and Launch date look ahead too, so they add Tomorrow, Next 7 days, Next 30 days and Next month: - Next 7 days and Next 30 days include today. - On these three filters, This month covers the whole month, including the days still to come. On Created it runs from the 1st to today. ## AI search Instead of building filters by hand, describe the plans or events you want. AI search works on all four lists once it’s enabled for your shop. Note If you click into the search box and don’t see the Tab: try AI search badge, AI search isn’t enabled for your shop yet. The normal search box and filters work exactly as described above. 1. Click into the search box and press Tab, or click the light-blue Tab: try AI search badge. On a phone or tablet, tap AI search. 2. Type your request in English and press Enter. 3. Check the preview. It shows the filters AI search understood, and nothing changes until you click Apply. AI search works with each list’s own filters, the ones in the table above. Some requests it understands: - Inventory Commitments: “confirmed commitments at the Berlin warehouse due next month” - Sales Plans: “draft sales plans ending this month” - New Product Planning: “confirmed launch plans launching in the next 30 days” - Promotional Events: “holiday events” Name the date you mean: “due” for a commitment’s target date, “ending” for a sales plan, “launching” for a launch plan. A plan number such as SP-00012, a SKU or a name goes into the search box instead of a filter. The applied filters are ordinary chips you can edit or save as a preset. For how to word requests, what the preview shows and what AI search doesn’t handle yet (for example “not at a location” or two date periods at once), see [Find orders by describing them (AI search)] (/guides/search-with-ai/). ## Saved presets A preset saves the filters and the search term under a name. Presets are kept per list: a preset saved on Sales Plans doesn’t appear on Inventory Commitments. - Save a preset. Once your filters differ from the selected preset, a save button appears next to the filter bar. On All, the unfiltered default, it reads Save filters. On a saved preset, Save overwrites that preset, and Save as… in the menu next to it creates a new one. Give it a name and click Save preset. - Use a preset. Pick it in the preset menu at the start of the toolbar. All clears every filter and the search. - Make it the default. Pick the preset, open the preset menu again and choose Set as default under Manage “preset”. Everyone in your shop then opens the list with those filters, unless they open a link that already carries filters. The default preset carries a star in the menu. Only one preset per list can be the default; Clear default removes it. - Rename or delete. With the preset picked, use Rename… or Delete… in the preset menu. Deleting a preset keeps the current filters until you change them, and no plans or events are affected. Note Presets are shared by the whole shop. Saving, renaming, deleting or setting a preset as the default changes it for everyone who uses that list. ## Page size Below each list, a footer shows which rows you’re looking at, for example “Showing 1 to 10 of 34 sales plans”, with buttons to move between pages. Pick how many rows a page shows: 10, 20 or 50. The plan lists start at 10 and Promotional Events at 20. On the three plan lists, Logistified remembers your choice. ## Walkthrough: find every confirmed commitment due next month 1. Open Inventory Planning and click the Inventory Commitments tile. 2. Click Filter › Status, tick Confirmed and click Apply. A Status chip appears below the toolbar. 3. Click Filter › Target date and choose Next month. A Target date chip appears, and the list shows the confirmed commitments whose target date falls next month. 4. To keep this view, click Save filters, name it Due next month and click Save preset. With AI search enabled for your shop, the same list is one sentence: press Tab in the search box and type “confirmed commitments due next month”. ## See also - [Find orders by describing them (AI search)] (/guides/search-with-ai/): how to write requests and read the preview. - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): what each status means. - [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/): export the plans you found. - [Inventory Planning] (/features/inventory-planning/overview/): the hub and its four lists. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/plans-in-the-forecast/ # Plans in the forecast How inventory commitments, launch plans, sales plans and promotional events change, or don't change, your forecast and reorder suggestions. [Enhanced plan] (/reference/subscription-plans/) Your forecast predicts demand from what you sold in the past. Logistified’s Inventory Planning lets you add what the past can’t show: a big order that’s coming, a product you’re about to launch. This page explains, plan type by plan type, what reaches the forecast and what doesn’t. ## On this page - At a glance - Planned outflow - Which date it lands on - Launch plans follow their curve - Sales plans: goals, not demand - Excluding one commitment - Plans and locations - Promotional events - See also ## At a glance Changes the forecast and reorder suggestions? When Inventory commitment Yes, as planned outflow While it’s Confirmed or Locked, unless you excluded it with Exclude from forecast Launch plan Yes, as planned outflow along its launch curve While it’s Confirmed or Locked and Feed into forecast is on (it’s on by default) Sales plan Never Its targets are shown next to the forecast for comparison while it’s Confirmed or Locked Promotional event Yes, as extra demand on the event’s dates While it’s switched on with Use in forecasts Draft, Completed and Cancelled plans never change the forecast. See [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). Each one also needs a subscription plan that includes it. Commitments count on the Elevate plan, launch plans and promotional events on the Enhanced or Elevate plan. On a lower plan they stop changing the forecast, but nothing is deleted, and they count again once you upgrade. The Supply view’s sales-plan chart needs Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## Planned outflow [Planned outflow] (/reference/glossary/#planned-outflow) is demand you’ve told Logistified about in advance. The forecast treats it like sales that will happen on top of your normal sales: stock runs down sooner, the reorder date moves earlier, and the suggested reorder quantity grows to cover it. Gross Profit at Risk also counts the planned units you couldn’t ship if you run out before the supplier’s lead time. How much counts: - Inventory commitments count their expected quantity: the estimated quantity times the probability. An item of 500 units at 80% adds 400 units. See [Items, dates & probability] (/features/inventory-planning/commitments/items/). - Launch plans count their launch curve, the units the plan expects week by week. Where you see it: - The In Stock cell. In a forecast view, a line under the variant’s quantity, such as “− 400 planned outflow”, shows the planned outflow that is still ahead, from tomorrow on. A commitment spread over a week that started three days ago counts only the days still to come, and a plan dated today counts 0. - The In Stock hover card. Point at a variant’s In Stock cell to see a Planned outflow tile with the total and how many plans contribute, and one row per plan with its plan number, status, start date and what it still takes from tomorrow on. - The Supply view. A period with planned outflow shows a planned outflow icon in its cell (or the units, if you pick Value under Show in cells). Click the cell: its card shows Planned outflow under Inventory movements, and Inventory documents lists every contributing plan by plan number, with its status and date. Click a plan number to open the plan. See [Supply view] (/features/forecast/supply-view/). Planned outflow is kept apart from the forecast’s own demand line, so nothing is counted twice. Note Only future days count. Demand on days that have already passed is left out, because it either happened (and is in your sales history already) or didn’t. ## Which date it lands on Each commitment item lands on its own date if it has one. If not, it uses the commitment’s Target date: - A single date puts the whole expected quantity on that day. - A date range spreads it evenly over every day of the range. A 300-unit item over March adds about 10 units a day. So you can give a whole commitment one date and override it only for the items that differ. The Target date column on the Items tab shows Plan default for items that use the commitment’s date. ## Launch plans follow their curve A launch plan doesn’t spread its units evenly. It adds them day by day along its launch curve, so a launch that starts slowly and then picks up does the same in the forecast. See [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/). Two switches on a launch plan control this: - Feed into forecast: on by default. Turn it off to keep the plan for reference without changing the forecast. A badge beside the title of the plan’s Details card shows where the plan stands right now: Feeds forecast only while the switch is on and the plan is Confirmed or Locked, Not feeding forecast otherwise (a Draft, Completed or Cancelled plan, or the switch is off), and Excluded from forecast for a plan that was excluded from the forecast through the API. Point at the badge, or move to it with the keyboard, to see why, for example “Feed into forecast is off for this plan. Turn it on in Edit details.” The New Product Planning list’s Forecast column says the same in short: Feeding, Not feeding, Off (the switch is off) or Excluded. - Stop feeding on first real sale: when it’s on, the plan stops feeding the forecast at a location as soon as the new product has its first real sale there. From then on, the product’s own sales drive its forecast. Once every product of the plan has sold at its locations, the badge reads Stopped (first sale) and the list’s Forecast column says the same. While some locations still have no sale, the plan keeps feeding there and the badge stays Feeds forecast. Completing a launch plan also stops it feeding the forecast. ## Sales plans: goals, not demand A sales plan is a goal, not a prediction. It never changes forecast quantities, reorder dates or reorder suggestions. That way an ambitious target can’t make you overbuy. While a sales plan is Confirmed or Locked, its targets are shown next to the forecast so you can compare: - The Supply view: a Sales plans chart above the table with Sold, Forecast and Plan bars per period, and the plan totals in each cell’s and period’s card. You can leave single plans out of a view, and a Show sales plans switch in the Supply menu hides or shows them all. See [Supply view] (/features/forecast/supply-view/#the-sales-plan-chart). To act on a sales plan, adjust your forecast settings or order through the forecast as usual. See [Sales Plans] (/features/inventory-planning/sales-plans/overview/). ## Excluding one commitment To keep a single commitment out of the forecast without changing its status, open it and choose Actions › Exclude from forecast. To bring it back, choose Include in forecast. This works while the commitment is Draft, Confirmed or Locked, even though a Locked plan can’t otherwise be edited. The badge next to Details on the commitment page always tells you where it stands. Point at it for the reason: - Feeds forecast: “This commitment’s expected quantities count as future demand while it is Confirmed or Locked.” - Not feeding forecast: “A commitment feeds the forecast only while it is Confirmed or Locked.” - Excluded from forecast: “Excluded from the forecast. Include it again from the Actions menu.” Use it to test what the forecast looks like without a commitment, or to keep a doubtful one on file. ## Plans and locations Forecast views can cover all locations or only some. A view covers all locations when it’s set to All locations or when it picks every one of your locations. Planned outflow follows the location it’s planned at: - A commitment item with a location counts in views that include that location, and in views covering all locations. - A commitment item set to Unallocated (all locations) counts once in views covering all locations, and not in views limited to some locations. Pick a location to count it there. - Launch plans and sales plans plan each product per location. Each location’s numbers count in views that include it, and a view covering all locations adds the locations up. See [Plans at several locations] (/features/inventory-planning/locations/). ## Promotional events A promotional event lifts the forecast on its dates every year, once you switch it on with Use in forecasts. Unlike plans, it applies to every product and location. With an uplift per product, each product gets its own measured uplift. The forecast’s Amplifiers popover shows which events are active. See [Promotional events] (/features/inventory-planning/promotional-events/). ## See also - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): which statuses count. - [Supply view] (/features/forecast/supply-view/): planned outflow and sales plan targets period by period. - [Plan for a large order with an inventory commitment] (/guides/plan-for-a-large-order/): a commitment from start to finish. - [Order stock for a plan] (/guides/order-stock-for-a-plan/): how each plan type leads to orders. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/exports-and-documents/ # Exports, documents & activity Download a plan as PDF, Excel or CSV, export the plan lists, attach files to a plan and follow its activity log. [Enhanced plan] (/reference/subscription-plans/) In Logistified, every inventory commitment, sales plan and launch plan can be downloaded as a PDF or a spreadsheet, carries its own documents, and keeps a log of what happened to it. This page covers all three plan types. Promotional events have none of these. You can export and download on every subscription plan. To upload documents or attach a printout, your subscription needs to include the plan’s type: Enhanced or Elevate for a launch plan, Elevate for a commitment or a sales plan. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - Quick PDF export - Export a plan - Export a sales plan for review - Exporting the list - The Documents tab - The Activity tab - Dates and your store’s time zone - Templates - See also ## Quick PDF export On a plan’s page, open Actions › Quick PDF export. The PDF downloads straight away, using your default PDF template (or the standard layout if you haven’t set one up). The PDF is titled by plan type (Inventory Commitment, Sales Plan or New Product Plan) and lists the plan’s details, its recipient when it has one, and its items: SKU, product, location, target date, estimated quantity, probability, expected quantity, and the price and value unless your template hides prices. On a sales plan’s PDF, the quantities and values are the ones its Products tab shows, including revenue you typed in yourself. ## Export a plan Actions › Export lets you choose the format and template: 1. Excel Spreadsheet (.xlsx), CSV File (.csv) or PDF Document (.pdf). The gear icon next to a format opens its template settings. 2. Tick Attach printout to my documents to save a copy on the plan’s Documents tab as well. 3. Click Next. Without templates for that format, the file downloads now. Otherwise pick a template, or Use default settings. For a PDF, Preview shows the result with the plan’s data; the preview’s Page size (A4 (210 x 297 mm) or US Letter (8.5 x 11 in)) only changes the preview. 4. Click Export PDF, Export XLSX or Export CSV. The file downloads. Exporting works in every status and on every subscription plan, so you can download a Locked, Completed or Cancelled plan too. A spreadsheet with Use default settings has one row per item: plan number and name, status, product, variant, SKU, location, estimated quantity, probability, expected quantity and the item’s target date. A launch plan has no single target date per item, so its default spreadsheet shows each item’s Launch start and Launch end instead. On a launch plan’s PDF, the target window runs from the launch date to the end of the plan horizon, and follows any change you make to either. When Attach printout to my documents is greyed out, the reason replaces its help text: - The plan is Locked, Completed or Cancelled, so its documents are read-only. You can still download the printout. - Your subscription doesn’t include this type of plan: “Attaching needs the Elevate Plan. You can still download the printout.” On a launch plan it names the Enhanced Plan. ### Walkthrough: save a commitment as a PDF for your customer 1. Open the commitment and click Actions › Export. 2. Pick PDF Document (.pdf) and tick Attach printout to my documents. 3. Click Next, choose a PDF template (if you have several), and click Preview to check it. 4. Click Export PDF. The PDF downloads, and a copy appears on the Documents tab. 5. Attach the downloaded PDF to your email to the customer. ## Export a sales plan for review On a sales plan’s page, open Actions › Export for review (XLSX). An Excel workbook downloads for the locations you picked in the location switcher: one, several or all of them. It’s laid out for a review with your CEO or finance team: - Summary: per location and in total, last year, baseline, initiatives (and their risk-adjusted value), manual change, plan, goal and gap to goal, and the plan against last year in money and in percent. Below the tables, notes on anything that needs a look, such as products without a price, a goal for all locations that doesn’t match the locations’ goals, or a last year that isn’t over yet, and a short guide to the terms. - Months (revenue) and Months (units): the same lines for every month of the plan, with the plan’s total. - Initiatives: each initiative with its lever, owner, status, timing, probability, impact and where it applies, then the initiatives in the plan month by month. Last year is what the plan’s products sold at those locations on the same days a year earlier. A month that isn’t over yet last year shows in italics, and the plan is compared with last year over complete months only. When you plan with Claude, Claude can build the same workbook and give you a download link. The link works for 15 minutes; after that, ask Claude for a new one. Through Claude, the export needs the Elevate plan. ## Exporting the list What you can export from a list depends on the plan type: List Export Inventory Commitments Export (or Export N with commitments ticked) opens Export Commitments: choose the commitments, the data level and the format. See below. Sales Plans Export downloads a CSV straight away: the ticked plans, or every plan on the current page. Plans on other pages aren’t included, so raise the page size to 50 to export more at once. One row per plan, with plan number, name, locations, products, target units, status, plan window and last update. New Product Planning No list export. Export each plan from its page. Promotional Events No export. Export Commitments goes through four steps: 1. Scope: Selected (the commitments you ticked), All on this page, or All filtered (every commitment matching your search and filters, across all pages). 2. Data level: Line item export (one row per item of each commitment) or Commitment level export (one row per commitment, with its item count, estimated and expected quantities and locations). 3. Format: Excel spreadsheet (.xlsx) or CSV file (.csv), and an export template if you have one. 4. Export: the file downloads when every commitment has been read. Cancel export stops it without downloading anything. ## The Documents tab The Documents tab holds files that belong to the plan: a customer’s order confirmation, a contract, a product brief, or printouts you attached when exporting. - Upload new document opens Upload Document. Drop a file or click to browse: PDF, images, Excel, CSV or Word, up to 10 MB. Give it a Document Type (pick an existing one or type a new one; empty means General) and click Upload. - Each document shows its name, type, size and upload date, with buttons to download or delete it. Deleting asks for confirmation and can’t be undone. You can upload and delete documents while the plan is Draft or Confirmed and your subscription includes its type. Once it is Locked, Completed or Cancelled, documents can still be downloaded but not changed. ## The Activity tab The Activity tab is the plan’s history, newest first, in your store’s time zone (the one set in Shopify). Logistified records what happened, for example: - status changes (“Status changed: Draft → Confirmed”) and edited details, - items or products added, updated or removed. On a commitment, an item edit names the product, its location and what changed, for example “Updated Mug · Blue at Berlin: estimated qty 100 → 120”, - orders created from the plan, by number, for example “Purchase order created: PO-…”, - on a sales plan: growth changes, re-seeded targets, locations added or removed, - on a launch plan: size groups created, saved or removed, rebuilt curves, adjusted curves, locations added or removed. Comments. Type in Add a comment to the activity log… and click Add, for example to note why a target changed. Comments can’t be edited or deleted. The comment box is hidden once the plan is Locked, Completed or Cancelled. If the history can’t be read for a moment, the tab says “Couldn’t load the activity.” instead of showing an empty log, and no comments can be added until it loads again. ## Dates and your store’s time zone Times and dates on Inventory Planning pages and in their exports follow your store’s time zone from Shopify, not the time zone of the computer you’re using: the Created line under a plan’s title, the Activity times, a document’s upload date, the list’s Updated column, the PDF’s created, confirmed and “Generated on” times, the date in export file names and the created, updated, confirmed and locked times in a spreadsheet. If Logistified can’t read your store’s time zone for a moment, these show UTC (universal time) instead. Plan dates you pick (a target date, a plan window, a launch date) are calendar days and always show the day you chose. ## Templates PDF and spreadsheet templates for plans are set up in Settings › Inventory Planning › Export templates: a PDF template, an item-level spreadsheet template and a plan-level one for the commitment list. A PDF template can show barcodes and product images, or hide prices. See [Inventory Planning settings] (/features/inventory-planning/settings/). Tip Quick PDF export uses your default PDF template, so set that one up first and every one-click PDF has your layout. ## See also - [Inventory Planning settings] (/features/inventory-planning/settings/): export templates and plan numbers. - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): which statuses are read-only. - [Search, filters & saved views] (/features/inventory-planning/search-and-filters/): narrow a list before exporting it. - [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/#editing-in-a-spreadsheet): download a launch plan’s Week grid, edit it and upload it again. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/adding-products/ # Adding products to a plan Each variant is in a plan only once. What that means when you add products, and how to bring back products removed at one location. [Enhanced plan] (/reference/subscription-plans/) A variant can be in a plan only once. Whenever you add products to a plan, Logistified won’t let you add one that’s already there. If you removed a product at one location and want it back there, use Add missing products. Launch plans come with the Enhanced plan. Inventory commitments and sales plans need Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - Ways to add products - A variant can only be added once - Adding virtual materials - Bring back products removed at a location - When a location has no products left - See also ## Ways to add products Sales Plans and New Product Planning share one Add products menu, in the wizard when you create the plan and on the plan’s page later. It offers five ways to add: Source What it does Browse products The product picker: search your Shopify products and tick variants, or a whole product. Scan barcodes Scan a barcode or SKU with a scanner, or type one and press Enter. Each product is added once, however often you scan it. Upload a spreadsheet A CSV, XLS or XLSX file with one product per row, identified by Variant ID, SKU or Barcode. From a forecast view Every product a saved forecast view (or filters you build on the spot) finds at the plan’s locations. Virtual materials Raw materials you manage in Assemblified. See [Adding virtual materials] (#adding-virtual-materials). Where each one is offered: - Sales Plans: all five, in the wizard and on a saved plan. On a saved plan, each product you add is planned at every location of the plan, seeded from that location’s sales last year. - New Product Planning: all five for individual products. A size group’s Add variants, and To “group” on a saved plan, offer fewer: browse, virtual materials and, in the wizard, scanning and spreadsheets. See [Size groups] (/features/inventory-planning/size-groups/). - Inventory Commitments use their own Add items menu on the Items tab: Add from Shopify, Virtual materials, Scan barcode and Upload CSV. Scanning there counts: each scan adds 1 to the item’s estimated quantity. See [Items, dates & probability] (/features/inventory-planning/commitments/items/). ### Upload a spreadsheet Upload products reads one product per row and ignores other columns. In each row, the first identifier it finds decides: 1. Variant ID: the Shopify variant ID. 2. SKU, when the row has no Variant ID. Common names such as Article number or Item code are recognised too. 3. Barcode (EAN, UPC or GTIN), when the row has neither. Example file › Download CSV or Download XLSX gives you a file to fill in. Files up to 20 MB work. If the columns match, the mapping step is skipped; otherwise you map them yourself. Before anything is added, the preview tells you what it found, for example “3 products to add. 1 already on the plan (skipped). 1 not found: ABC-1.” Rows that match nothing, or more than one product, are listed and left out. Click Add 3 products to add them, or Change mapping or Upload a different file. ### From a forecast view Add products from a forecast view lets you reuse a view you already have, for example Bestsellers or Winter range. Pick it under View, or choose Create custom filters to build a one-off selection. - Every product the view finds that is stocked at the plan’s locations is added. - The view’s own location filter doesn’t count: “This view’s location filter is replaced by this plan’s locations.” - Filters on forecast numbers (such as days of stock) aren’t used to pick products. The dialog names the ones it leaves out. - If the products don’t fit in the plan, nothing is added and the dialog says how many the plan can hold. Narrow the view, or pick fewer locations. ### After adding A short summary says what happened, for example “120 added. 12 already on the plan (skipped).” Products that couldn’t be found are named. A variant that’s already in the plan is never added twice; the next section explains why. ## A variant can only be added once This applies to every Inventory Planning plan: when you create one, and when you add products later with Add products (on a commitment, Add items). In the product picker, a variant that’s already in the plan is marked Already added and can’t be ticked. If you tick a whole product, only its variants that aren’t in the plan yet are added. If every variant of a product is in the plan, the whole product reads Already added. On a New Product Planning plan with size groups, Add products opens a menu. The rule applies to both entries: New products, and To “group” for adding variants to a size group. A variant added to a size group gets an even share of the split (with four sizes, 25%) and the other sizes scale down, so the group still adds up to 100%. The group’s panel then says “size was added with an even share. Check the split.” until you save the group. See [Size groups] (/features/inventory-planning/size-groups/). When you create a New Product Planning plan, each size group has its own Add variants button. It offers every way to add except a forecast view (browse, scan barcodes, upload a spreadsheet, virtual materials), and a variant that’s already in the plan, as an individual product or in another group, is marked Already added there too. “Already in the plan” means at any location. On a New Product Planning plan or a Sales Plan with several locations, a new product is planned at every location of the plan at once. You never need to add it a second time for another location. Why: a variant planned twice would have its plan counted twice, and its attainment would no longer mean anything. If two people add the same product at the same moment, the second add skips it and says so: “1 already on the plan (skipped)”. ## Adding virtual materials Virtual materials are the raw materials you manage in Assemblified. You plan them exactly like a Shopify product: - Inventory Commitments: on the Items tab, open Add items and choose Virtual materials. - Sales Plans and New Product Planning: open Add products and choose Virtual materials, when you create the plan or later. On a New Product Planning plan, a material can also join a size group (Add variants, or To “group” on a saved plan) and be a similar product (Add similar product → Virtual materials). The same rule applies: a material already in the plan is marked Already added. Targets, revenue, curves, the forecast and promotional events treat a material like any product: its history is what Assemblified used of it, and its revenue comes from its price. One thing works differently, because virtual materials don’t exist in Shopify: Create sales order on a commitment leaves them off the Shopify draft order. The dialog says so before you create the order, for example “1 virtual material is not sold in Shopify and stays off this order.”, and its quantities and line count only cover what the draft order gets. Afterwards, the confirmation names the materials it skipped. ## Bring back products removed at a location When you remove a product at one location, it stays in the plan at its other locations. That’s why Add products shows it as Already added. To plan it at that location again, use Add missing products: 1. In the location switcher at the top of the plan, pick the location. 2. Open Actions and choose Add missing products…. The menu says how many products are missing, for example “2 products planned elsewhere but not at Berlin”. 3. Check the summary and click Add 2 products. Logistified confirms with “Berlin: 2 products added back”. Only the missing products are added. Nothing else in the plan changes. Add missing products… only shows up in the menu when a single location is picked and that location is missing products the plan has elsewhere. Where the restored numbers come from: - New Product Planning: each curve is rebuilt from the product’s similar products at that location. A size-group variant comes back with its old share of the split, and the group’s other sizes scale down so the split still adds up to 100%. - Sales Plans: targets are seeded from that location’s own sales last year, at each product’s growth. If a product can’t be brought back, a message names it and says why. If none could, you’ll see “Nothing was added back at location”. Products deleted in Shopify. A product you deleted in Shopify keeps the rows it already has on the plan, but it is never planned anywhere new: Add missing products…, Add location… and Sync locations skip it, on sales plans and launch plans alike. Add missing products… can still count it as missing; when it skips it, the message reads, for example, “1 product could not be added back here because it was deleted from the shop: Mug (Blue)”. ## When a location has no products left - Sales Plans: the location stays on the plan. Its Products tab reads “No products at location” and, when the Actions menu offers it, points you to Add missing products. The next time you add new products to the plan, they’re planned there too. - New Product Planning: a launch location with no products left is no longer part of the plan. Add it again with Actions › Add location…, which plans every product there. Tip A product that sells at a location where it isn’t planned doesn’t count toward the plan. The [Analytics tab] (/features/inventory-planning/plan-analytics/#sales-the-plan-doesnt-count) tells you when this happens, so you can decide whether that location belongs in the plan. ## See also - [Size groups] (/features/inventory-planning/size-groups/): plan the sizes of one product together. - [Plan analytics] (/features/inventory-planning/plan-analytics/): compare the plan with what actually sold. - [Subscription plans] (/reference/subscription-plans/): which plan each part of Inventory Planning needs. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/inventory-planning/locations/ # Plans at several locations Plan a product at many stores at once, each from its own sales, and add or remove locations on a running plan. [Enhanced plan] (/reference/subscription-plans/) In Logistified, Sales Plans and New Product Planning plan every product at every location of the plan. One plan covers all your stores, and each store gets its own numbers from its own sales. This page covers how that works and how to change a plan’s locations later. New Product Planning comes with the Enhanced plan. Sales Plans need Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - One plan, many locations - Choosing locations when you create a plan - The location switcher - Editing on All locations - Add location - Remove location - New locations since the plan was created - Add missing products - Location notices - Walkthrough: add a new store to a running plan - See also ## One plan, many locations When a plan has several locations, each product is planned once per location: - Sales Plans: each product’s target at a location is seeded from that location’s sales last year, at the product’s growth. - New Product Planning: each product’s launch curve at a location is built from the similar products’ sales at that location, and each location has its own similar products, Volume × and launch date. The plan’s locations are its launch locations. Sales at other locations are never copied over. A location where the products (or, for a launch plan, the similar products) never sold starts at 0, and the plan tells you so. Inventory Commitments work differently: each item has its own location, or none. See [Items, dates & probability] (/features/inventory-planning/commitments/items/). ## Choosing locations when you create a plan Both create dialogs ask for locations: - All locations (ticked by default on a sales plan) plans at every active location you have when you create the plan. - Untick it to pick locations from the list. The dialog counts the rows the plan will have, for example “12 products × 3 locations = 36 plan rows”. A plan can hold a limited number of rows, and the dialog warns you before you reach it; split a large range into two plans. See [Creating a sales plan] (/features/inventory-planning/sales-plans/creating/) and [Creating a launch plan] (/features/inventory-planning/new-product-planning/creating/). ## The location switcher On a plan with more than one location, a switcher sits next to the tabs. A plan with one location has no switcher. Plan type Whole-plan option Where it applies Sales Plans All locations Products, Plan, Analytics New Product Planning All locations (summary) Plan, Analytics The plan opens on the whole-plan option. Documents and Activity always cover the whole plan. Click the switcher to open its list: - The whole-plan option sits at the top. It is ticked when every location is; click it to tick them all. - Each location has a checkbox and its planned units. A location with nothing planned is highlighted. - Only, next to a location, ticks that location alone. Tick one location, several, or all of them. At least one always stays ticked: the last ticked box can’t be unticked. Nothing changes while the list is open. The tabs switch when you close it, by clicking outside it, pressing Escape or clicking the switcher again. The switcher then reads the whole-plan option, the location’s name, or for example 2 locations; hover it to see which locations those are. A reload keeps the locations you picked. What you see: - At one location, the tabs show only that location: its products, its targets or curves, and its sales. - On All locations, each product is one row that adds up its locations. A sales plan’s Products tab adds a Locations column, for example 3 of 3. On the Analytics tab, the share card compares the locations; see [Plan analytics] (/features/inventory-planning/plan-analytics/#share-by-location-or-product). - With several locations picked, the tabs work like All locations, over the picked locations only. Each product is one row that adds up those locations, the Locations column counts within them, for example 2 of 3, and the Analytics tab compares the picked locations with each other. ## Editing on All locations You can edit the whole-plan view of both plan types. A number you type there is split across the locations in proportion to what each one plans for that period. If nothing was planned there yet, a sales plan splits by each location’s total for the product, and a launch plan splits evenly. The locations always add up to exactly what you typed. Sales Plans. On All locations you can edit every cell of the plan grid, and on the Products tab the Target units, Target revenue and Growth. Growth applies to the product at every location; when the locations have different growth, the field reads Mixed. Removing a product there removes it at every location, after a confirmation. New Product Planning. On All locations (summary) you can edit the period totals in the Week grid, the Launch date and Volume × on the Volume & launch tab, and a product’s similar products: its row opens a panel for every location of the product, where a change sets one value at all the locations of a table and each location’s curve is rebuilt from its own sales history. Size-group settings and a product’s actions, such as Apply to all locations, stay per location: pick the location first. See [Similar products across locations] (/features/inventory-planning/new-product-planning/launch-curve/#similar-products-across-locations) and [Size groups] (/features/inventory-planning/size-groups/). Several locations picked. Edits work the same way, split across the picked locations only. The plan’s other locations are never changed: on a sales plan this holds for targets, growth, revenue resets and Remove, which asks, for example, “Remove product from the 2 selected locations?”. On a launch plan, a Launch date or Volume × typed on the Volume & launch tab, a size group’s launch date, and a change to a product’s similar products change the picked locations only. Add products still adds products at every location of the plan. To change one location only, pick it in the switcher first (Only next to its name). ## Add location Add a store to a running plan with Actions › Add location…. The menu item is there while the plan is Draft or Confirmed and has products. - Sales Plans: every product of the plan is added at the new location, with targets seeded from that location’s own sales last year at each product’s growth. A product with different growth at different locations starts at 0% there, and Logistified tells you which. - New Product Planning (the dialog is called Add launch location): every product and size group is copied to the new location, and each curve is rebuilt from that location’s own sales history. Curves you edited by hand aren’t copied. A product without similar products keeps the curve of the location it was copied from, and Logistified tells you which. A product you deleted in Shopify isn’t copied to the new location. Pick the location and click Add location. Logistified confirms, for example “Munich added: 40 products added there” on a sales plan, or “Munich added: 40 products, 2 size groups” on a launch plan. The item is greyed out with “Every active location is already part of this plan” when there’s nothing left to add. Note On a sales plan, unsaved growth changes aren’t copied to the new location. Save first. ## Remove location Actions › Remove location… takes a location off the plan: 1. Pick the location. The dialog shows how many rows it has there, then click Continue. 2. Confirm with Remove location. What’s removed: - Sales Plans: the location’s targets, including hand edits and revenue you typed. - New Product Planning: the location’s products and size groups. Their planned demand leaves the forecast at that location. This can’t be undone. Adding the location back later starts it fresh from last year’s sales or the similar products. A plan must keep at least one location. With one left, the item is greyed out: “A plan must keep at least one location” on a sales plan, “A plan must keep at least one launch location” on a launch plan. To stop planning altogether, cancel or delete the plan. Removing a location from an All locations plan. A plan created with All locations follows your locations. Once you remove one, it becomes a fixed set of locations and stops offering new ones. The dialog warns you before you confirm. ## New locations since the plan was created A plan created with All locations doesn’t add new stores by itself. When you add a location in Shopify later, the plan shows a notice, for example “1 new location since this plan was created.”, with the location’s name and a Sync locations button. Sync locations adds every product there, the same way as [Add location] (#add-location), and also skips products you deleted in Shopify. Logistified confirms, for example “1 location added: Munich (40 products)”. The notice appears only on plans created with All locations that are Draft or Confirmed. On a plan with picked locations, use Add location… instead. ## Add missing products When you remove a product at one location, it stays in the plan at its other locations. To plan it at that location again, pick only that location in the switcher and use Actions › Add missing products…. The menu item only appears when one location is picked and it is missing products the plan has elsewhere. A product you deleted in Shopify is never added back; the message names it. [Adding products to a plan] (/features/inventory-planning/adding-products/#bring-back-products-removed-at-a-location) describes it step by step. ## Location notices Notices about the plan’s locations sit in one folded row, Location notices, at the top of a sales plan’s Products tab and a launch plan’s Plan tab. It counts what’s inside, for example 1 info or 2 warnings. Click it to read them: - New locations to sync (see above). - Nothing planned: a location reads 0, with the reason. On a sales plan, for example, “No sales there last year, so growth has no effect. Type target units here or on the Plan tab.” On All locations, each location’s name is a link that switches to it. With several locations picked, the notice counts within them, for example “Nothing planned at 1 of 2 locations.” With no notices, the row isn’t shown. ## Walkthrough: add a new store to a running plan 1. Open the plan. It must be Draft or Confirmed; a Locked plan needs Release first. 2. If the plan was created with All locations, open Location notices at the top of the tab and click Sync locations. Skip to the last step. 3. Otherwise, open Actions and choose Add location…. 4. Pick the new store and click Add location. Every product of the plan is added there. 5. Pick the store in the location switcher and check its numbers. A new store has no sales of its own, so its targets (or curves) may start at 0. Type them in the plan grid or Week grid, and save. ## See also - [Adding products to a plan] (/features/inventory-planning/adding-products/): the add-once rule and bringing back removed products. - [Plan analytics] (/features/inventory-planning/plan-analytics/): compare locations against their plan. - [Sales Plans] (/features/inventory-planning/sales-plans/overview/) and [New Product Planning] (/features/inventory-planning/new-product-planning/overview/). - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): which statuses allow editing. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/plan-analytics/ # Plan analytics Compare a product launch or a sales plan with what actually sold, overall, by location and by product. [Enhanced plan] (/reference/subscription-plans/) In Logistified, the Analytics tab of a New Product Planning plan and of a Sales Plan compares what you planned with what you actually sold. A Sales Plan can show revenue as well as units. New Product Planning comes with the Enhanced plan. Sales Plans need Elevate. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - Choose products and a location - Plan vs. actual - On track for - Pacing this month - Plan vs. benchmark - Accuracy by layer - Planning matrix - Share by location or product - Biggest misses vs plan - Sales the plan doesn’t count - Why a number may look different from what you expect - The 10-unit rule - When the tab has nothing to show - See your plans in the forecast - See also ## Choose products and a location Two controls decide what every card on the tab shows. Location. Use the location switcher at the top of the plan. Pick All locations for the whole plan, a single location, or several locations, which every card then shows combined. On New Product Planning it reads All locations (summary). A plan with only one location has no switcher. Product search. To look at one product, type its name or SKU in the search at the start of the tab’s toolbar and pick it, or press Enter for the first match (an exact SKU comes first). Every card then shows that product. The products you picked show as chips beside the search: click × on a chip to drop that product, or Show all to go back to all variants. Once you have picked products, the next pick asks whether to Add it to them or Replace them. To stop being asked, choose Add or Replace at the bottom of the search’s list; your browser remembers the choice, and Ask brings the question back. Variants. Use the Variants menu right of the search. It starts on All variants, with the count in brackets. Once you pick, it reads, for example, 3 of 24, and None selected after Clear. You can tick a whole product, or single variants across several products. Search by product title, variant title, or SKU. - All variants and Clear sit at the bottom of the menu. - While you search, they become Select N matching and Clear N matching. Some variants are greyed out, with the reason next to them: Reason What it means Not planned at location The variant isn’t planned at the location you picked. With several locations picked: Not planned at the selected locations. No curve yet New Product Planning only. The variant has no launch curve yet, so there is nothing to compare. With All variants picked, products you add to the plan later are included automatically. Your selection stays while you switch tabs or locations. Reloading the page resets it to All variants. The toolbar also has: - Group by, which sets the columns of the [planning matrix] (#planning-matrix). It also sets the columns of the grid in the Plan tab, so the two always match. New Product Planning offers Week, Month, and Quarter, and starts on Week. Sales Plans add Year, and start on Month. - Units | Revenue, on Sales Plans only. The Revenue tab names your currency, for example Revenue (EUR). It switches every card between units and money. ## Plan vs. actual The first card is titled Plan vs. actual plus what you picked, for example “Plan vs. actual: 3 of 24 variants at Berlin”, or “… at 2 locations” with several locations picked. Hover the ⓘ icon next to any card title for a short explanation of what the card shows. It has five tiles: Tile What it shows Planned to date What the plan expected up to and including today. Actual to date What has sold since the plan started. Attainment Actual to date as a percentage of planned to date. Planned total The whole plan, to its last day. On track for Where you’ll land if recent sales continue. See [On track for] (#on-track-for). Attainment, here and on every other card, is colored the same way: green from 90%, amber from 70%, red below 70%. The chart shows two running totals over the plan’s dates: Planned (cumulative) and Actual (cumulative). Only sales inside the plan’s dates count. Sales from before the plan started don’t. Until something sells, the chart says “No sales in the plan window yet for this selection.” On a Sales Plan, only sales count. 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, so it is not in Actual to date, the chart or [Sales the plan doesn’t count] (#sales-the-plan-doesnt-count). A New Product Planning plan still counts it. With All locations or several locations picked, the card has two tabs, Total | By location. By location keeps the tiles and replaces the chart with one small chart per location, each with its own scale and its sales and plan to date, for example “225 of 270 to date · 83.3%”. With only some variants picked, the small charts show just those variants. While their numbers per location are loading, or when they can’t be read, the charts show every variant of the plan and a note says so. ## On track for The On track for tile answers: “if sales keep going like this, where do we end up?” It reads like ~90 of 180, with a line underneath such as “At 50% of plan over the last 9 days”. How it’s worked out: 1. Logistified compares sales with the plan over the last 14 full days. Today is left out because it isn’t over yet. A plan younger than 14 days uses the days it has. 2. That pace is applied to the rest of the plan. The projection follows the plan’s own shape, not a straight line. If the plan has a peak still ahead, the projection has it too. The chart draws the result as a dashed line, Projected (at recent pace). The figure is an estimate, so it is rounded and shown with a “~”. The tile shows “-” instead, with the reason underneath, when: - “The plan hasn’t started yet” - “The plan has ended, so actual to date is final” - “Too few sales so far to project”: fewer than 10 units sold (see [The 10-unit rule] (#the-10-unit-rule)) - “No full day of sales yet to measure the pace”, or “No full week of sales yet to measure the pace” on a large plan (see [Why a number may look different] (#why-a-number-may-look-different-from-what-you-expect)) - “Nothing was planned in the last 14 days” On a Sales Plan’s Revenue tab, the projection uses the revenue pace. It can therefore differ from the Units tab, for example when a product has a revenue override or no price. ## Pacing this month The Pacing card, right after the first card, shows the period you are in: this month on a Sales Plan, this week on New Product Planning, following Group by. Its title names it, for example “Pacing: this month (Nov 2026)”. For each variant it lists: Column What it shows Plan The target for the whole period. Plan to date The target from the first day of the period up to today. Actual to date What has sold in the period so far. Delta Actual to date minus plan to date. % of plan Actual to date as a percentage of plan to date. Status How the variant is doing, see below. The status uses the same scale as the rest of the tab: - Ahead: at or above plan. - On track: from 90% of plan to date. - Slightly behind: from 70%. - Behind: below 70%. - No plan yet: nothing was planned so far in the period. Variants furthest behind come first, and chips under the title count the variants per status. Before the plan starts, the card says when pacing starts; after it ends, it says when the plan ended. Under 10 units sold in the period, the title carries an Early days tag. ## Plan vs. benchmark On a Sales Plan, the Plan vs. benchmark by month card compares the plan with another sales plan of your shop, its benchmark: your planners’ own spreadsheet brought in as a plan, or another plan built in Logistified. Both plans are read on the same calendar days. Pick the plan to compare with in Benchmark, at the top right of the card. The choice is saved on the plan, so it’s there the next time anyone opens the tab. None removes it. While a plan is Locked, Completed or Cancelled, your choice applies only until you leave the page. A plan without products, or with no dates in common with this plan, is listed but can’t be picked, and says why. To bring a spreadsheet in, ask Claude in the planning chat to bring your sheet in as a plan, then pick that plan in Benchmark. The card shows: - Plan, Benchmark, Difference (the plan minus the benchmark on the days both cover, and as a percentage of the benchmark) and Largest difference: the month where the two differ most, either way. - Differences always compare the same days. If the benchmark covers only part of the plan, for example its sheet ends on December 15, the card compares only the days both cover and shows Plan on days the benchmark doesn’t cover on its own line. A month covered in part says how many of its days the benchmark covers. - A bar chart per month: purple for the plan, blue for the benchmark. A pale blue bar is a month the benchmark covers only in part, for example when it starts mid-month. With all variants selected, the dashed line is the plan’s goal. - Where they differ, By location or By group (your plan’s product grouping): a bar to the right where the plan is higher, to the left where the benchmark is higher. A location only one of the two plans has is marked. - Show months: the figures month by month. Show products: the products that differ most, and those only in one of the two plans. The card follows the location switcher, the Variants menu and Units / Revenue. Figures are whole units or whole amounts, and each column adds up to its total. If the benchmark plan is deleted or cancelled later, the card says so and you can pick another. ## Accuracy by layer On a Sales Plan, the Accuracy by layer card shows how close each layer of your plan came to what actually sold: - Baseline: what your sales history said before anyone changed the plan. - Your benchmark plan, named by its plan name: for example your planners’ own spreadsheet, picked in Plan vs. benchmark. - Plan: the baseline plus your initiatives and edits. Comparing the plan with the baseline shows whether your initiatives and edits made the plan more accurate, or less. It counts complete days only, through yesterday, so today’s sales, still coming in, don’t skew it. Pick To date or a month in the strip at the top. The running month is marked *, and its figures are so far. For each layer, the card shows: - Forecast, Sold and Difference: what the layer expected, what sold, and the gap between them. - Error: how far off the layer was, per product and month, as a share of what sold. Lower is closer. The closest layer is in bold. Total below it is the same for each location’s month as a whole, the way a goal is compared. It’s lower, because a product that sold more makes up for one that sold less. - Bias: whether the layer expected more than sold (over) or less (under), as a share of what sold. Below the table, a sentence says which layer came closer. When the error per product disagrees with the Total or with the Bias over the whole period, it names both: for example, the plan can be closer in total but further off per product, when your changes added sales to other products, locations or months than the ones that sold them. A month in which the locations you’re looking at sold below the pacing card’s “behind” line, under 70% of the plan, carries a Behind flag in the strip. Under Show months, that month’s row names each location and product group that fell behind too, with the share of the plan it sold (for example “Behind: Berlin 54%, Hats (group) 48%”), the furthest behind first. The card checks the last complete month and the running one. A month planned under 10 units isn’t flagged. Every layer is measured on your plan’s products. The benchmark is measured only on the days its own dates cover and at the locations it plans. The card follows the location switcher and Units / Revenue, and covers every product of the plan. Before the plan starts, the card says that accuracy starts once sales come in. ## Planning matrix The Planning matrix sets your products against the calendar. The columns follow Group by. Each cell shows actual / target for that period, colored by attainment. - The current period is marked to date. It compares sales so far with the target so far. - Future periods show the target only. - The Total column runs to date. - The row pinned at the bottom adds up everything you picked. It reads All products, or Selected variants when you picked only some. The Variants | Products tabs choose the rows: - Variants (the default) shows one row per variant. - Products shows one row per product, adding up the variants of that product you picked. - Locations, with All locations or several locations picked, shows one row per location against the periods, with all your locations added up at the bottom. With only some variants picked, the rows show just those variants (while they load, or when they can’t be read, every variant, with a note). The total row is the same in the Variants and Products views. ## Share by location or product The share card, below the planning matrix, shows how your plan and your sales split, each as a percentage of its own total. Because it compares shares rather than totals, it’s useful mid-plan. Say every location is behind plan. If Berlin was planned for 40% of the sales but has made only 25%, Berlin is falling behind faster than the others. What the card splits by depends on what you picked: You picked Card title All locations, on a plan with several locations Share by location (to date) Several locations Share by location (to date), over the picked locations One location, or a plan with only one location Share by product (to date) One location, and what you picked there is a single product Share by variant (to date) The planned share only counts what was planned up to today, the same cut-off as the sales. So a location that launches later shows 0% planned until its start date. ### To date | Whole plan Two more tabs choose the time span: - To date compares planned and actual shares up to today, as described above. - Whole plan shows the planned mix of the whole plan, from its first to its last day, for example how next year’s plan splits across your locations. It shows planned shares only, because sales exist only up to today, and its title reads, for example, Share by location (whole plan). While nothing is planned before today, for example on a plan that starts next year, the card opens on Whole plan. ### Dumbbell | Donuts Two tabs switch the chart. Both show the same numbers. - Dumbbell (the default) shows one row per location or product. The hollow dot is the planned share and the filled dot is the actual share. The further apart the dots, the bigger the difference. - Donuts shows a planned donut and an actual donut side by side. With more than six entries, the chart keeps the five with the largest planned share. The rest are combined into one grey Other. The table below the chart still lists every entry and marks the combined ones In Other. ### The table The table is folded away so the card shows just the chart. Select Show table under the chart to open it, and Hide table to fold it again. It stays open while you switch locations. Column What it shows Planned / Actual Units, or revenue, to date. Planned share / Actual share Each entry’s percentage of the column’s total. Share gap Actual share minus planned share, in percentage points (“+3 pts”, “−3 pts”). Attainment Actual as a percentage of planned, on the same green / amber / red scale. On All locations, this table is where you read each location’s attainment. On All locations, a location’s row can carry a note: - No curve yet on New Product Planning, or Nothing planned on Sales Plans: the location is part of the plan for these variants, but has nothing planned to compare yet. - No sales history here (counts as zero): see [Why a number may look different] (#why-a-number-may-look-different-from-what-you-expect). ### When the chart is replaced by a note These notes replace the whole chart: Note Why “Nothing planned before today” To date only: the plan hasn’t reached any planned sales yet. The table still shows actual sales. Switch to Whole plan for the planned mix. “Select more products or locations to compare shares” There’s only one entry, so there’s nothing to compare. “No planned revenue before today: the selected variants have no price” Revenue tab: the variants are planned, but they have no price. These replace only the actual side, and the planned side stays: Note Why “Too few sales so far to compare shares (n units)” Fewer than 10 units sold. See [The 10-unit rule] (#the-10-unit-rule). “No revenue recorded to date” Revenue tab: nothing has sold with a price yet. ## Biggest misses vs plan The Biggest misses vs plan card, at the bottom of the tab, shows two small tables side by side: the five entries furthest Ahead of plan and the five furthest Behind plan, within what you picked. Each row shows the entry, its Miss (sold minus planned to date) and its % of plan. Hover the info icon next to the title for what the card counts. - On All locations, or with several locations picked, each entry is one variant at one location. - At one location, each entry is one variant. The gap is actual to date minus planned to date: “+42 units”, “−35 units”, or an amount in your currency on the Revenue tab. Each entry also shows its attainment. A variant that sold without anything planned so far is listed as ahead, with “-” for attainment. Click a row to focus the whole tab on that variant. The location stays as it is, and the row you clicked stays highlighted until you change the selection. To go back, open the Variants menu and choose All variants. Instead of the tables, you may see: - “Biggest misses need at least two variants or locations to compare.” - “Nothing was planned before today, so there are no gaps yet.” While fewer than 10 units have sold, the card’s title carries a small Early days tag: gaps get meaningful once sales come in. ## Sales the plan doesn’t count Each location in a plan counts only the sales of the variants planned there. A sale is credited to the location that fulfilled the order. All locations adds those up. So if a variant sells at a location where it isn’t planned, that sale isn’t in the plan’s numbers. When this adds up to something worth knowing, a single line appears above the chart on All locations. A plan with only one location shows it on that location too. With several locations picked, the line isn’t shown. For example: Berlin isn’t on this plan but sold 120 units of these variants since the plan started. Those sales aren’t counted here. Hamburg sold 40 units of these variants where they aren’t planned (not counted here). 15 units of these variants were sold elsewhere or without a fulfilment location (not counted here). A location is named only when it sold at least 10 units and at least 5% of everything those variants sold, counted or not. The line always counts units, also on the Revenue tab. The line is only a hint. It doesn’t add anything to the plan or change any number. Use it to decide whether that location belongs in the plan. See [Adding products to a plan] (/features/inventory-planning/adding-products/). ## Why a number may look different from what you expect Analytics reads the saved plan. Edits in the Plan tab show up here only after you save. On a Sales Plan with unsaved changes, the tab says: “Analytics reads the saved plan. Your unsaved changes show here once you save them.” “To date” follows UTC, not your shop’s timezone. The tab’s “today” changes at midnight UTC. In New York, for example, that is 8 pm in summer and 7 pm in winter. “Planned to date” already includes the whole of today, while today’s sales are still coming in. So early in the UTC day, attainment and On track for read a little low and catch up by the end of it. “No location” counts sales at every location. Some older plans have products planned without a location. They appear as No location on the share card and on Biggest misses vs plan, and they count that product’s sales at all your locations. On such a plan, All locations can be more than the sum of the individual locations. A variant planned both with and without a location shows the same sales in both places. A location with no sales history counts as zero. If a product has sold in your shop but never at a planned location, its actual sales there are zero. Sales from other locations aren’t moved over. The tab says so in a message above the chart, for example “No sales history at Berlin for 1 product, so its actuals count as zero there (shop-wide sales are not used).” Revenue comes from the price on the plan (Sales Plans). Planned revenue is the revenue you set for a product, or else its planned units × its price. Actual revenue is units sold × the price on the plan, not what customers paid, so discounts don’t show up. The card reminds you: “Revenue is derived from price.” When you typed revenue in for some products, it says so instead, for example “Planned revenue includes 2 overrides; actual revenue uses the product price.” Large plans count by week. On a very large plan, the tab loads with “Loading a large plan. This can take a little while.” and the first card notes “Weekly totals: this plan is too large for daily detail.” The numbers are then added up per week, and On track for measures the pace over whole weeks. A completed Sales Plan keeps updating. Completing a Sales Plan doesn’t freeze its numbers. If a late order lands inside the plan’s dates, the Analytics tab picks it up. ## The 10-unit rule With only a handful of sales, percentages swing wildly. Until what you picked has sold 10 units: - the share card hides its actual side and shows “Too few sales so far to compare shares (n units)”, - On track for shows “-” with “Too few sales so far to project”, - Biggest misses vs plan carries an Early days tag next to its title. The rule counts units, also on a Sales Plan’s Revenue tab. ## When the tab has nothing to show Message What to do “No analytics yet” (New Product Planning) Nothing to do yet. The tab fills in once the plan has a forecast and its products start selling. “No targets to analyze yet” (Sales Plans) Seed the plan from history or set targets in the Plan tab. “Nothing planned at location yet” Plan something at that location in the Plan tab, or pick another location. “No variants selected” You cleared the Variants menu. Pick some variants. “None of the selected variants are in this plan any more” The variants you picked were removed from the plan. Pick other variants. “None of the selected variants are planned at location” Pick other variants or another location. “Nothing planned for the selected variants yet” New Product Planning: the variants you picked have no launch curve yet. Pick other variants, or give them a curve in the Plan tab. “No products at location yet, so there is nothing to compare with actual sales.” (Sales Plans) The products were removed at that location. Bring them back with [Add missing products] (/features/inventory-planning/adding-products/#bring-back-products-removed-at-a-location). “Couldn’t load plan vs. actual” Click Retry. With several locations picked, these messages name “the selected locations” instead of one location, for example “Nothing planned at the selected locations yet”, and suggest picking other locations. Tip Biggest misses vs plan and the planning matrix are the quickest way to see which variants are behind. Click an entry in Biggest misses vs plan, then switch locations to see where that variant is falling short. ## See your plans in the forecast Confirmed and Locked Sales Plans also appear in the forecast. In a [Supply view] (/features/forecast/supply-view/#the-sales-plan-chart), a chart above the table compares each period’s plan target with sales so far and the forecast, and each cell’s card shows how close that variant comes to its target. Each plan in the chart’s plan list links back to its Analytics tab. This tab tells you how a plan has done so far. The forecast tells you whether the coming periods will reach it. The two can show different numbers; [Why the chart and a plan’s Analytics tab can differ] (/features/forecast/supply-view/#why-the-chart-and-a-plans-analytics-tab-can-differ) explains why. ## See also - [Check how a plan is doing] (/guides/check-how-a-plan-is-doing/): read this tab step by step, and decide what to do about a gap. - [Sales Plans] (/features/inventory-planning/sales-plans/overview/) and [New Product Planning] (/features/inventory-planning/new-product-planning/overview/): the two plan types with an Analytics tab. - [Plans at several locations] (/features/inventory-planning/locations/): the location switcher and how a plan covers many locations. - [Supply view] (/features/forecast/supply-view/): your Sales Plans against the forecast, period by period. - [Adding products to a plan] (/features/inventory-planning/adding-products/): why a variant can only be in a plan once, and how to bring back products removed at a location. - [Subscription plans] (/reference/subscription-plans/): which plan each part of Inventory Planning needs. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/commitments/overview/ # Inventory Commitments Record demand you know is coming, such as a big order or a contract, so Logistified's forecast and reorders account for it. [Elevate plan] (/reference/subscription-plans/) In Logistified, an [inventory commitment] (/reference/glossary/#inventory-commitment) records demand you expect on top of your normal sales: a wholesale customer’s order before they place it, a contract, a promotion, a tender. You list the products, how many you expect to need, when, and how likely it is. Once you confirm the commitment, the forecast counts those units as future demand, so your reorder dates and quantities make room for them. Caution A commitment doesn’t reserve or hold stock in Shopify. Your available quantities don’t change. It only tells the forecast that the demand is coming, so you can buy or move stock in time. ## On this page - What a commitment is - When to use one - The list - The commitment page - Editing details - Recipient - What you can do here - See also ## What a commitment is A commitment has: - A name and a plan number. Out of the box, plan numbers start with IC-, for example IC-00012. You can switch to your own format; see [Plan numbers] (/features/inventory-planning/settings/#plan-numbers). - A target date: one day, or a date range. It’s when the demand happens, for every item that has no date of its own. - A default probability: how likely the demand is, from 0 to 100%. 100% means it’s certain. - Items: the products, each with an Estimated qty and a location (or Unallocated (all locations)), and optionally its own date and probability. The forecast counts each item’s Expected qty, the estimated quantity times the probability. - Demand type, reason and source: labels for your records, such as Promotion, Sales Commitment and Sales Team. They don’t change the forecast. - A recipient (optional): who the units are for. Like every plan, a commitment starts in Draft and feeds the forecast while it’s Confirmed or Locked. See [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). ## When to use one - A customer has announced a large order. Record it as soon as you know, with the probability you’d give it, and raise the probability as the deal firms up. - You’ve signed a contract for regular deliveries over a period. Use a date range so the demand is spread over it. - You’re running a promotion on specific products and expect extra sales. - You’ve bid on a tender and want to see what winning it would take, at a low probability. When not to use one: - For a sales goal you hope to reach, use a [sales plan] (/features/inventory-planning/sales-plans/overview/). A sales plan never changes the forecast, so a target can’t make you overbuy. - For a holiday that comes back every year, such as Black Friday, use a [promotional event] (/features/inventory-planning/promotional-events/). You set it up once, and it lifts the forecast every year. - For a product you haven’t sold yet, use [New Product Planning] (/features/inventory-planning/new-product-planning/overview/). It gives the product a launch curve based on similar products. ## The list Open Inventory Planning and click the Inventory Commitments tile. The list shows every commitment with these columns: Column What it shows Commitment The name, with the plan number underneath. Click it to open the commitment. A commitment without a name shows “Unnamed commitment”. Location(s) The location of its items: one name, “Multiple (n)” for several, or “-” when no item has a location. Items How many products it holds. Total est. qty The sum of the estimated quantities. Expected qty The sum of the expected quantities, after probability. This is what the forecast counts. Status The status badge, plus an amber Window elapsed badge when all its dates have passed but it’s still open. Point at the badge to see when the window ended and what to do. Target date The commitment’s date, for example “Dec 1, 2026”, or its date range. Updated When it last changed. Click the Commitment, Status, Target date or Updated header to sort the list. Each row’s … menu has View/Edit Details, and Delete for commitments in Draft, Completed or Cancelled. Delete asks first (“It will be removed from all views.”) and goes ahead with Delete Inventory Commitment. Above the list you can search, filter and save filter sets; see [Search, filters & saved views] (/features/inventory-planning/search-and-filters/). Export downloads the commitments you ticked, the current page or every commitment matching your filters as a spreadsheet; see [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). ## The commitment page Click a commitment to open it. - Header: the plan number as the title, the name under it, and when it was created. The status stepper sits at the top right. - Tabs: Items, Documents and Activity, the first two with a count, for example Items (3). On the same row, on the right: Edit details, the next-step button (such as Confirm) and the Actions menu. - Linked orders: once you’ve created orders from the commitment, slim bars at the top of the Items tab read Linked purchase order (Linked purchase orders once there are several), Linked transfer order or Linked sales order. Purchase and transfer orders are linked by their number; the sales order has an Open link. See [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/). - Details card: Name, Status, Default probability, Target date, Demand type, Reason, Source and Items, then Notes and Recipient. Next to the Details title, a badge shows whether the commitment feeds the forecast: Feeds forecast, Not feeding forecast or Excluded from forecast. Point at the badge, or move to it with the keyboard, for the reason. See [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/#excluding-one-commitment). - Items table: the products, with their quantities, locations, dates and probabilities. See [Items, dates & probability] (/features/inventory-planning/commitments/items/). Most fields have a small info button next to their label. Point at it (or tap it) for a short explanation. The Actions menu holds: - Edit details (while the commitment can be edited) - The other status moves, such as Back to Draft, Complete, Release or Cancel - Exclude from forecast or Include in forecast (while it’s Draft, Confirmed or Locked) - Create purchase order, Create transfer order, Create sales order. Once created, they become View purchase order (one per purchase order) with Create another purchase order, View transfer order and View sales order. - Quick PDF export and Export - Delete Each entry has a one-line description of what it does. The status moves are explained on [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/#moving-a-plan-along). The Documents tab holds files you attach, such as the customer’s letter of intent. The Activity tab records every change and lets you add comments. An item edit says what changed, for example “Updated Mug · Blue at Berlin: estimated qty 100 → 120”. See [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). ## Editing details Click Edit details to open the edit dialog (titled, for example, Edit IC-00012). It has the same fields as the create dialog: name, target date or date range, default probability, demand type, reason, source, notes and recipient. Change what you need and click Save changes. Details can be edited while the commitment is Draft or Confirmed. Changing the default probability or the target date updates every item that doesn’t have its own. A Confirmed commitment must keep a target date: to remove it, move the commitment back to Draft first. You can also edit Notes straight on the Details card: click the text, type, and click away to save. ## Recipient The Recipient (optional) section stores who the units are for: first and last name, email, phone, company and address. “Where these units go. Stored like a Shopify customer so a sales order can be prefilled later.” When you choose Create sales order, the Shopify draft order gets the recipient’s email and shipping address. Without a recipient, the Details card says “No recipient set.” See [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/#create-sales-order). ## What you can do here [Creating a commitment] (/features/inventory-planning/commitments/creating/) Create one by hand, or several at once from a spreadsheet. [Items, dates & probability] (/features/inventory-planning/commitments/items/) Add products and set their quantities, locations, dates and likelihood. [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/) Create purchase orders, a transfer order or a Shopify draft order. [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/) Confirm, lock, complete or cancel a commitment. ## See also - [Plan for a large order with an inventory commitment] (/guides/plan-for-a-large-order/): the whole job, step by step. - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): exactly how a commitment changes the forecast. - [Inventory Planning settings] (/features/inventory-planning/settings/): demand types, reasons, sources and plan numbers. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/commitments/creating/ # Creating a commitment Create an inventory commitment by hand, or import several at once from a spreadsheet. [Elevate plan] (/reference/subscription-plans/) In Logistified, you can create one inventory commitment at a time by hand and add its products afterwards, or create several commitments, products included, from one spreadsheet. Every new commitment starts in Draft, so nothing reaches the forecast until you confirm it. ## On this page - Two ways to create - Create manually - Single date or date range - Probability - Demand type, reason and source - Import several from a spreadsheet - See also ## Two ways to create On the Inventory Commitments list, click Create Inventory Commitment. The button opens a menu: - Create manually: fill in one commitment’s details, then add its products on the commitment page. - Import from CSV/XLSX: create one or more commitments with their products from a file. ## Create manually The Create Inventory Commitment dialog says “Capture expected future demand. Commitments start in Draft. Add items on the next screen.” It has four sections. The links at the bottom left (Details, Timing, Categorization, Recipient) jump to each one. - Plan Details: Name. It’s optional: leave it empty and the commitment is called by its plan number, such as IC-00001. - Timing & Likelihood: the Target date, as a Single date or a Date range, and the Default probability. - Categorization: Demand type, Reason, Source and Notes. - Recipient (optional): who the units are for. Click the heading to open the section. Target date, Default probability, Demand type, Reason and Source have an info button next to their label with a short explanation. 1. On the Inventory Commitments list, click Create Inventory Commitment › Create manually. 2. Enter a Name, for example Hotel chain spring order. 3. Under Target date, choose Single date or Date range and pick the date or dates. 4. Set the Default probability, for example 80. 5. Optional: pick a Demand type, Reason and Source, add Notes, and fill in the Recipient. 6. Click Create Inventory Commitment. Logistified confirms with “Inventory Commitment IC-… created” and opens the new commitment in Draft. Add its products on the Items tab next; see [Items, dates & probability] (/features/inventory-planning/commitments/items/). If the commitment can’t be created, the dialog stays open with everything you typed, and a message says why. You can leave the target date empty while you work on a draft, but you need one to confirm the commitment. See [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/#a-target-date-is-needed-to-confirm). ## Single date or date range - Single date (one Target date): the whole demand happens on that day. Use it for an order that ships on one day. - Date range (Start date and End date): “Demand is spread evenly across the range.” Use it for a contract or a promotion that runs over weeks. The chips above the dates fill in a common period in one click: This Quarter, Next Quarter, Rest of Year, This Year, Next Year or Next 12 Months. The end date must be on or after the start date, or the dialog says “End date must be on or after the start date”. The target date applies to every item that has no date of its own. You can give single items their own date later. ## Probability The Default probability says how likely the demand is, from 0 to 100%. It starts at 100 and can’t be left empty (“Enter a probability from 0 to 100”). The forecast counts each item’s estimated quantity times the probability: 500 units at 80% count as 400. Use it to plan for demand that isn’t certain yet: - A signed order: 100%. - A customer who said “very likely”: 80%. - A tender you’ve bid on: 20% or 30%. Items can have their own probability, which overrides the default. When you order from a commitment, you can choose between the full planned quantity and the probability-weighted one. See [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/#order-quantity). ## Demand type, reason and source These three labels help you sort and report on your commitments. They’re for your records only and don’t change the forecast. - Demand type: what kind of demand it is, such as Promotion, Seasonal or Contract. - Reason: why you expect it, such as Sales Commitment or Customer Forecast. - Source: where it comes from, such as Sales Team or Customer. Click a field (it reads Select demand type, Select reason or Select source) to pick from your list. To add a new value on the spot, type its name and choose Create demand type “…” (or Create reason “…”, Create source “…”); the hint at the bottom of the list, “Type a name above to add a new demand type”, reminds you. Logistified confirms with, for example, ‘Demand type “Wholesale” added’. The new value is added to your list for every plan. Manage the lists in [Inventory Planning settings] (/features/inventory-planning/settings/#demand-types-reason-codes-and-sources). ## Import several from a spreadsheet Use Import from CSV/XLSX when the demand comes from a spreadsheet, for example a customer’s forecast with one block of rows per store. Each row is one product. Logistified finds the product by its SKU or barcode. The file’s columns: Column Required What it holds Commitment No The name of the commitment the row belongs to. Rows with the same name become one commitment. Rows without one are imported together as a single commitment called “Imported commitment N”, which you can rename in the review. SKU or Barcode One of the two Identifies the product. Quantity Yes The estimated quantity. Rows with 0 are left out. Location No The location’s name. Rows without one, or with a name Logistified doesn’t recognise, are Unallocated (all locations). Target date No A single date for the row. Start date and End date No A date range for the row instead. A start date without an end date is a single date. Probability % No The row’s probability. Without it, the row uses the commitment’s probability. Demand type, Reason, Source No Labels for the commitment. The first value found in its rows is used. The importer recognises common alternative column names and lets you match the rest by hand. To start from a template, click Example file › Download CSV or Download XLSX in the import dialog. For how importing works in general, see [Import data from CSV or XLSX] (/guides/import-data-csv-xlsx/). 1. On the Inventory Commitments list, click Create Inventory Commitment › Import from CSV/XLSX. The Import commitments from CSV/XLSX dialog opens. 2. Upload your file. If the columns aren’t matched automatically, match them to the fields above. 3. Check the Review commitments step. Its summary reads, for example, “2 commitments ready · 0 with no matched items”. Each commitment is shown as a card with its Name, Timing (Single or Range, with the date or dates) and Probability %, which you can change here. The card says how many items matched (for example 12 items) and lists any SKUs or barcodes that weren’t found (for example “2 not matched: SKU-9, SKU-10”). 4. Click Create N commitments (Create 1 commitment for one). Logistified confirms with “Created N commitments”, and they appear in the list as Drafts. What happens during the review: - Timing is taken from the rows. If any row of a commitment has a date range, the commitment gets a date range from its earliest start to its latest end. Otherwise it gets the earliest single date. Each row also keeps its own date. - The probability starts at 100% for each commitment. Change it on the card if the whole commitment is less certain. - Repeated products are combined. If a product appears in several rows of the same commitment, the rows become one item with the quantities added up; its location, probability and dates come from the last of those rows. The card says so, for example “2 rows for SKU-123 combined”. - Unmatched rows are left out. A commitment with no matched products isn’t created. If the review doesn’t look right, use the buttons at the bottom: Change mapping to match the columns again, or Upload a different file. If some commitments can’t be created, the others are created anyway. The ones that failed stay in the review with “Not created:” and the reason, and a message names them, for example “Couldn’t create 2 commitments: North, South”. Fix them and click Create N commitments again: only the ones left are created, never the same one twice. Once part of the file has been created, Change mapping is greyed out. Tip To add products from a file to a commitment that already exists, open it and use Add items › Upload CSV on the Items tab instead. See [Items, dates & probability] (/features/inventory-planning/commitments/items/#uploading-items-from-a-file). ## See also - [Items, dates & probability] (/features/inventory-planning/commitments/items/): add and adjust the products. - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): confirm the commitment when you’re ready. - [Plan for a large order with an inventory commitment] (/guides/plan-for-a-large-order/): the whole job, step by step. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/commitments/items/ # Items, dates & probability Add products to an inventory commitment and set each one's quantity, location, date and likelihood. [Elevate plan] (/reference/subscription-plans/) The products of an inventory commitment in Logistified 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. ## On this page - The Items tab - Adding items - Location per item - Dates per item - Probability per item and Expected qty - Uploading items from a file - Removing items - See also ## 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] (#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] (/features/inventory-planning/adding-products/). 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 1. 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.” 2. Scan a barcode or SKU. The product appears in the list with a count of 1. 3. Scan the same product again for each unit: every scan adds one to its count. You can also type the count. 4. 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. 5. 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] (/features/inventory-planning/plans-in-the-forecast/#plans-and-locations). ## 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. Note Items can only be added, changed or removed while the commitment is Draft or Confirmed. To change a Locked commitment, Release it first; a Completed one, Reopen it first. ## See also - [Adding products to a plan] (/features/inventory-planning/adding-products/): the add-once rule and virtual materials. - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): how dates, probabilities and locations reach the forecast. - [Ordering from a commitment] (/features/inventory-planning/commitments/ordering/): turn the items into orders. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/commitments/ordering/ # Ordering from a commitment Turn an inventory commitment into purchase orders, a transfer order or a Shopify draft order in a few clicks. [Elevate plan] (/reference/subscription-plans/) An inventory commitment tells Logistified’s forecast that demand is coming. When you’re ready to act on it, you can create the orders straight from the commitment: buy the stock from your suppliers, move it to the right location, or prepare the customer’s order in Shopify. The three actions are in the commitment’s Actions menu. ## On this page - Three orders from one commitment - Order quantity - Create purchase order - Create transfer order - Create sales order - If only some orders are created - After creating - When the actions are missing or greyed out - See also ## Three orders from one commitment Action What it creates Use it to Create purchase order One draft purchase order per supplier Buy the stock you need for the commitment Create transfer order One draft transfer order between two of your locations Move stock to where the demand happens Create sales order A Shopify draft order for the commitment’s recipient Prepare the customer’s order in Shopify All three order actions are available in every commitment status, including Locked, Completed and Cancelled. Purchase orders can also be created again for a top-up. Each one opens a short dialog that ends with the same Order quantity choice and a line such as “4 items will be included.” ## Order quantity Every dialog asks which quantity to order: - Planned quantity: each item’s full Estimated qty. Use it when you’ll need the stock if the deal happens, whatever its probability. - Probability-weighted: each item’s Expected qty, the estimated quantity times its probability, rounded to whole units. Use it to buy only what you expect on average, for example across several uncertain deals. The dialog shows the total of each option in units, for example “Planned quantity (500 units)” and “Probability-weighted (400 units)”. The line under the choice counts the lines the order will get, for the option you picked: “4 items will be included.” A product planned at several locations becomes one line, with the quantities added up. Items whose quantity comes out at 0 are left off the order and aren’t counted. If no item has anything to order, the line says “No item has a quantity to order.” and the create button is greyed out. Enter quantities on the Items tab, or choose Planned quantity if the probabilities round everything down to 0. ## Create purchase order “Draft a purchase order from this plan’s items. Items are split into one draft PO per supplier.” 1. Open the commitment and choose Actions › Create purchase order. 2. Pick the Destination location, where the stock should arrive. A purchase order needs one. It starts at the location most of the items are planned at. 3. Choose the Order quantity: Planned quantity or Probability-weighted. 4. Click Create purchase order. Logistified confirms with, for example, “Created 2 purchase orders”, and opens the first one. 5. Review each draft purchase order, then send it to the supplier as usual. See [Purchase orders] (/features/supply-orders/purchase-orders/overview/). How the purchase orders are built: - One per supplier. Each item goes to its primary supplier, so a commitment with products from two suppliers creates two purchase orders. - Named after the commitment. Each purchase order is called “commitment name · supplier name”, for example “Hotel chain spring order · Linen Co”. - Items without a supplier are skipped. The message says how many, for example “Created 1 purchase order. 3 items had no supplier and were skipped.” Connect those products to a supplier and order them separately. If no item has a supplier, nothing is created and the dialog says “None of the planned items could be matched to a supplier.” - Virtual materials go on their supplier’s purchase order like any product. ## Create transfer order “Move this plan’s planned quantity between two locations.” 1. Choose Actions › Create transfer order. 2. Pick the From location (where the stock is now) and the To location (where it’s needed). To location starts at the location most of the items are planned at. The two must differ, or the dialog says “Source and destination must differ.” 3. Choose the Order quantity and click Create transfer order. Logistified confirms with “Transfer order created” and opens it. It’s called “Transfer for commitment name”. See [Transfer orders] (/features/supply-orders/transfer-orders/overview/). ## Create sales order “Create a Shopify draft order from this plan’s items, addressed to the plan’s recipient.” 1. Choose Actions › Create sales order. The dialog shows the commitment’s recipient (name and email), or “No recipient set on this plan.” 2. Choose the Order quantity and click Create sales order. Logistified creates the draft order in Shopify and opens it in your Shopify admin in a new tab. The message names it, for example “Sales order #D12 created in Shopify”. The draft order: - Holds one line per product, at the chosen quantity. - Uses the recipient’s email and shipping address, if the commitment has a recipient. Set the recipient under Edit details before you create the order; see [Recipient] (/features/inventory-planning/commitments/overview/#recipient). - Is tagged Logistified, Inventory Plan and the commitment’s plan number, and carries the note “Sales order created from inventory plan IC-…”. It stays a draft in Shopify until you complete it there. Virtual materials can’t be sold in Shopify, so they’re left off the draft order. The dialog says so before you create it, for example “1 virtual material is not sold in Shopify and stays off this order.”, and its totals and line count only cover what the draft order gets. Afterwards, the message lists the materials it skipped, for example “Skipped 1 virtual material (not sold in Shopify): Linen yarn.” On a commitment that holds only virtual materials, the dialog says “No item has a quantity to order.” and Create sales order stays greyed out. If Shopify refuses the draft order, the dialog stays open with Shopify’s reason, for example “Shopify couldn’t create the draft order: Email contains an invalid domain name. Check the recipient’s email.” Fix the recipient under Edit details and try again. Creating a sales order doesn’t change the commitment or the forecast. When the customer’s order is placed and the stock has gone out, Complete the commitment so it stops counting as future demand. ## If only some orders are created When something goes wrong on the way, the dialog stays open and lists what happened under Order creation results. The choices above it lock, so a retry uses exactly the same destination and order quantity. - Open PO-… links every purchase order that was created. - “Order created; review its lines.” means the purchase order exists, but some of its lines may not have been saved. Open it and check its lines. - “Supplier name: order not created.” names a supplier whose purchase order failed, with the reason. - “Supplier name: order was created but its details were not returned. Do not create it again.” means a purchase order exists. Look for it in your purchase orders before ordering again. - “Order PO-… was created but could not be linked to this plan … Contact support to relink it; there is no relink action here. Do not create it again.” The order exists but doesn’t show on the commitment. Opening it doesn’t repair the link. A transfer order or a sales order that couldn’t be linked reads the same way, with Open #D… in Shopify for the draft order. Retry failed suppliers retries only the suppliers whose orders were not created; orders that exist are never created again. The message above the button says “Some orders still need attention. Retry only the failed suppliers; created orders will not be recreated.” When nothing can be retried, the button reads Nothing to retry and the message says “Open the orders above to review them. There is nothing to retry.” Close closes the dialog. If an attempt ends with an unexpected error or no response, check the commitment’s linked orders and your order list before trying again. The error alone does not tell you whether an order was created. ## After creating - Purchase orders add up. Actions lists View purchase order for each purchase order created from the commitment, named by its number, and Create another purchase order for a top-up. It opens the same dialog and orders the chosen quantity of every item again, so lower the lines on the new draft if part of it is already ordered. Every purchase order stays linked. - A transfer order and a sales order are one each. Their menu entry changes from Create … to View transfer order or View sales order, which opens the order (the sales order in your Shopify admin). - Linked-order bars appear at the top of the Items tab, above the details: Linked purchase order (Linked purchase orders once there are several) with a link per purchase order (its number), Linked transfer order with the transfer order’s number, and Linked sales order with Open. - Activity records each created order by its number, for example “Purchase order created: PO-2026-000123”, “Transfer order created: TO-00012” or “Sales order created: #D12”. - The orders don’t link back. A purchase order or transfer order made from a commitment is a normal order. It doesn’t show the commitment; only its name tells you where it came from. Creating an order doesn’t change the commitment’s status or what it adds to the forecast, and changing the commitment’s status later doesn’t change the orders. Once the purchase order is on its way, the forecast counts it as incoming stock, alongside the commitment’s planned outflow. ## When the actions are missing or greyed out - “Add items first”: the commitment has no items yet. Add some on the Items tab. - The actions aren’t in the menu at all: your shop isn’t on the Elevate plan. - “No item has a quantity to order.” in the dialog: every item has an Estimated qty of 0, or the probabilities round it down to 0 with Probability-weighted. See [Order quantity] (#order-quantity). - View transfer order instead of Create transfer order: the commitment already has its transfer order. Open it and change it there. ## See also - [Order stock for a plan] (/guides/order-stock-for-a-plan/): how each plan type leads to orders. - [Items, dates & probability] (/features/inventory-planning/commitments/items/): set the quantities and probabilities the orders use. - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): ordering through the forecast instead. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/sales-plans/overview/ # Sales Plans Set sales goals per product and location, in units and revenue, and track them against what actually sells. [Elevate plan] (/reference/subscription-plans/) A [sales plan] (/reference/glossary/#sales-plan) is a sales goal. It sets a target for each product at each location, day by day over the plan’s dates, in units and in revenue. Logistified starts every target from last year’s sales and your growth (one percentage for every product, or each product’s own growth measured from its sales history), and then tracks the plan against what actually sells. ## On this page - What a sales plan is - When to use one - The list - The plan page - Statuses on a sales plan - Edit details - Changing the plan window - Saving changes - What a sales plan can’t do - What you can do here - See also ## What a sales plan is A sales plan answers “how much do we want to sell, of what, where and when?” - Per product and location. Each product is planned at every location of the plan, from that location’s own sales. See [Plans at several locations] (/features/inventory-planning/locations/). - Day by day. Targets follow last year’s seasonal shape. You can view and edit them by week, month, quarter or year. - Units and revenue. Revenue is units × the product’s price, unless you type your own. See [Revenue] (/features/inventory-planning/sales-plans/products-and-targets/#revenue). - Tracked against actual sales. The Analytics tab compares the plan with what sold, and Confirmed or Locked plans show up next to the forecast in the Supply view. A sales plan is a goal, not a forecast. It never changes your forecast or your reorder suggestions. See [What a sales plan can’t do] (#what-a-sales-plan-cant-do). Sales Plans are part of the Elevate plan. On a lower plan you can review existing plans but not create or change them. ## When to use one Use a sales plan when you want to set a number and see whether you hit it: - a season or year ahead, for example “15% more than last autumn at every store”, - a target per store, with a bigger push at one of them, - a revenue goal you want to follow week by week. Use something else when the sales are expected rather than wished for: - a customer has announced a large order: use an [inventory commitment] (/features/inventory-planning/commitments/overview/), which adds that demand to the forecast, - a product is new and has no sales of its own: use [New Product Planning] (/features/inventory-planning/new-product-planning/overview/), - a holiday or sale lifts demand every year: add a [promotional event] (/features/inventory-planning/promotional-events/). ## The list Open Inventory Planning and click the Sales Plans tile. The list shows: Column What it shows Sales plan The name and, under it, the plan number. Click it to open the plan. Locations The plan’s locations, for example Berlin, Hamburg +1, or All (6) for a plan on all locations. Products How many products the plan has. Target units All targets added up. Status Draft, Confirmed, Locked, Completed or Cancelled. An amber Window elapsed tag means the plan’s dates are over but it is still open. Plan window The plan’s start and end dates. Updated When the plan last changed. Target units can have decimals, because targets are planned day by day to two decimal places. Sorting. Click the Sales plan, Status, Plan window or Updated header to sort the list. A second click reverses the order, a third goes back to the default: newest plans first. The small arrow next to Sales plan chooses what that column sorts by: Name, Plan number or Created date. The … menu on a row has View/Edit Details, and Delete for plans in Draft, Completed or Cancelled. Export to CSV. Export in the page header downloads the plans on the current page as a CSV file, not every plan matching your filters. Tick rows first to export only those: the toolbar then shows “3 selected” and Export 3. The file has the plan number, name, locations, products, target units, status, plan window and last update. For exporting a single plan with its targets, see [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). To find plans, use the search box, filters and saved presets above the list. See [Search, filters & saved views] (/features/inventory-planning/search-and-filters/). ## The plan page The header shows the plan number, the plan name and when the plan was created. On the right, the status steps show where the plan is: Draft, Confirmed, Locked, Completed. Hover a step to read what it means for a sales plan, for example “Targets are tracked against actual sales. You can edit them until you lock the plan”. In the row with the tabs, on the right, are Edit details, the next-step button (Confirm, Lock, Complete or Reopen) and the Actions menu. Actions holds Edit details again, the other status changes, Quick PDF export, Export, the location actions and Delete. See [Statuses on a sales plan] (#statuses-on-a-sales-plan). The plan has six tabs: Tab What it’s for Products One row per product with its growth, last year’s sales and targets. The number in brackets counts the products shown at the selected locations. See [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/). Plan The plan grid: targets per product and period. See [The plan grid] (/features/inventory-planning/sales-plans/plan-grid/). Initiatives The named reasons behind the plan, and how far it is from its goal. See [Initiatives] (/features/inventory-planning/sales-plans/initiatives/). Analytics The plan against actual sales. See [Plan analytics] (/features/inventory-planning/plan-analytics/). Documents Files attached to the plan, with their count in brackets. See [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). Activity A log of every change to the plan, and your comments. The location switcher. On a plan with more than one location, a switcher sits next to the tabs. Tick All locations for the whole plan, a single location, or several locations, which the tabs then show combined. The plan opens on All locations. It applies to the Products, Plan and Analytics tabs. Each location shows its planned units, and a location with nothing planned is highlighted. See [The location switcher] (/features/inventory-planning/locations/#the-location-switcher). Location notices. When something about the plan’s locations needs your attention, a folded row, Location notices, sits at the top of the Products tab. Click it to read the notices: for example “Nothing planned at 1 of 3 locations.”, with the reason, or new Shopify locations you can add with Sync locations. See [Location notices] (/features/inventory-planning/locations/#location-notices). The Details card is at the top of the Products tab: - Name - Plan window: start and end date, and the number of days. - Products: how many products, and how many location targets when the plan has several locations. - Locations: the first few names, with +N more to see the rest. A plan on all locations reads, for example, Locations (6 · All). - Demand type, Reason and Source, only when they are set. - Notes: click to add or edit notes. They save when you click away. A sales plan has no probability and no recipient. When the plan is Locked, Completed or Cancelled, a Read-only banner says so and what to do: “This plan is Locked. Release it to make changes.”, “This plan is Completed and is read-only. Reopen it to make changes.” or “This plan is Cancelled and can no longer be changed.” ## Statuses on a sales plan A sales plan uses the same five statuses as every plan: Draft, Confirmed, Locked, Completed and Cancelled. On a sales plan they are about tracking targets, never about the forecast. The button next to Actions is always the next step; the other moves are in the Actions menu. Status Next-step button Also in Actions Draft Confirm: “Start tracking this plan’s targets against actual sales” Cancel Confirmed Lock: “Freeze the plan from further edits” Complete: “Close the period. Attainment figures stay available”, Back to Draft, Cancel Locked Complete Release: “Unfreeze the plan so its targets can be edited again”, Cancel Completed Reopen: “Move back to Confirmed and track its targets again” none Cancelled none none: a cancelled plan can’t be moved again - What you can edit. Only a Draft or Confirmed plan can be changed: its details and notes, its products, growth, targets and revenue, its locations, documents and comments. - What Locked prevents. A Locked plan is frozen: every tab is read-only and Edit details, Add products and the location actions are gone. Its targets still count in the Supply view and on the Analytics tab. Release it to edit again. - An empty plan can’t be confirmed. On a Draft without products, Confirm is greyed out: “This sales plan has no products. Add at least one product before confirming.” - Completing early. Completing a plan before its window ends asks first, Complete this plan early?, and explains that the forecast stays the same: only the plan’s remaining targets leave the sales plan comparison. - Cancelling always asks first, because it can’t be undone. The full rules for every plan type are on [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). ## Edit details Click Edit details (also in the Actions menu). The dialog, titled with the plan number, has these sections: - Plan Details: Name. Leave it empty to use the plan number. - Timing: the Plan window, with the same quick periods as when you created the plan, or a Start date and End date. - Categorization: Demand type, Reason, Source and Notes. The demand types, reasons and sources are the ones you set up in [Inventory Planning settings] (/features/inventory-planning/settings/), and you can also type a new one here. - Grouping: the Product grouping, how the plan’s products group into categories. Shop default follows your default grouping; the groupings are set up in [Settings → Product Groupings] (/features/settings/product-groupings/). Changing it changes no targets. Click Save changes. Edit details is only available while the plan is Draft or Confirmed. ## Changing the plan window Targets are built for the plan’s dates. So when you move the start or end date of a plan that has products, Logistified asks first, for example “Re-seed 40 products at 3 locations?”: The new window rebuilds every target from last year’s sales in that window × each product’s growth. Hand edits and revenue overrides are replaced. - Re-seed targets saves the new dates and rebuilds every target from last year’s sales at each location, for the new dates. - Keep current window goes back to the dialog without saving, so you can change the dates back. What a re-seed keeps and what it replaces: - Kept: each product’s growth at each location, so a product at +30% is seeded again at +30%. A product at -100% stays at 0. A [product sold under a year] (/features/inventory-planning/sales-plans/products-and-targets/#products-sold-under-a-year) keeps its source and is estimated again for the new dates. - Replaced: every target, including your changes in the plan grid and on the Products tab, and every revenue you typed by hand. Revenue goes back to units × price. - Unsaved changes are discarded too, and the prompt says how many products they cover. They are only discarded once the re-seed has worked: if it fails, the old dates and your unsaved changes stay. Logistified then confirms, for example “Re-seeded 120 targets for the new plan window”, and names any location where a product had no sales last year (its target there is 0). Only a date change re-seeds. Saving the name, the categorization or the notes leaves the targets alone, and a plan without products changes its dates without asking. The window can be at most 1,100 days; a longer one is refused under End date, for example “This window is 1,101 days long. A plan can span at most 1,100 days.” ## Saving changes Edits on the Products tab and in the plan grid are not saved one by one. They wait in one bar at the bottom of the page, for example “Unsaved changes: 2 products · 6 location targets” on a plan with several locations, or “Unsaved changes: 2 products” on a plan with one. - Save changes saves every change, on every tab and at every location, in one go. Logistified confirms how many targets were saved, for example “Saved 6 targets”. - Discard changes throws them all away. If some of them are at locations you aren’t looking at, the bar says so (“Includes 3 location targets at other locations (saved too).”) and Logistified asks first: Discard all unsaved changes?, with Keep editing or Discard all changes. While a growth change is loading last year’s sales, the bar reads “Loading last year’s sales…” and Save changes waits for it. Your changes stay while you switch tabs or locations. If you try to leave the plan with unsaved changes, an Unsaved changes dialog asks you to Stay or Leave without saving. While the plan has unsaved changes, Lock, Complete and Cancel are greyed out with “Save or discard your changes first”. Note The Analytics tab reads the saved plan. While you have unsaved edits, it says so: “Analytics reads the saved plan. Your unsaved changes show here once you save them.” ## What a sales plan can’t do - It doesn’t feed the forecast. Targets never change forecast or reorder quantities, in any status. While the plan is Confirmed or Locked, its targets show next to the forecast for comparison only: on the Elevate plan, in the Supply view’s Sales plans chart above the table and in the cards. See [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/) and [Supply view] (/features/forecast/supply-view/#the-sales-plan-chart). - It doesn’t create orders. A sales plan has no order actions. To buy stock for it, order through the forecast. See [Order stock for a plan] (/guides/order-stock-for-a-plan/#sales-plans-order-through-the-forecast). - It doesn’t freeze when completed. Completing a sales plan closes the period, but its Analytics keep updating if a late order lands inside the plan’s dates. To see how a plan is doing, use its Analytics tab: plan against actual sales, to date and for the whole window. See [Plan analytics] (/features/inventory-planning/plan-analytics/). ## What you can do here [Creating a sales plan] (/features/inventory-planning/sales-plans/creating/) The three-step dialog: dates, locations, growth, products and a preview of the targets. [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/) Change growth, targets and revenue per product, recalculate targets from sales history, add and remove products. [The plan grid] (/features/inventory-planning/sales-plans/plan-grid/) Edit targets per week, month, quarter or year, in units or revenue. [Plans at several locations] (/features/inventory-planning/locations/) The location switcher, editing several locations at once, adding and removing locations. [Plan analytics] (/features/inventory-planning/plan-analytics/) Compare the plan with what actually sold. [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/) Confirm, lock, complete, reopen and cancel a plan. ## See also - [Build a sales plan for next season] (/guides/build-a-sales-plan/): the whole job, step by step. - [Check how a plan is doing] (/guides/check-how-a-plan-is-doing/): read the Analytics tab and the Supply view chart. - [Supply view] (/features/forecast/supply-view/#the-sales-plan-chart): your sales plans against the forecast. - [Inventory Planning] (/features/inventory-planning/overview/): the three plan types side by side. Last updated: 7 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/sales-plans/creating/ # Creating a sales plan Set up a sales plan in three steps, with targets seeded from last year's sales at each location. [Elevate plan] (/reference/subscription-plans/) In Logistified, you create every sales plan with the same three-step dialog. You choose the dates and locations, say how much you want to grow, pick the products, and check the targets before the plan is created. Everything can be fine-tuned on the plan afterwards. ## On this page - The three steps - Setup: plan window - Setup: locations and growth - Setup: growth from sales history - Setup: products sold under a year - Products - Review - Review: growth from sales history - Review: products sold under a year - Create plan or Create empty plan - Locations with no sales last year - Walkthrough: create a sales plan - See also ## The three steps Open Inventory Planning, click the Sales Plans tile, then click Create Sales Plan. The Create Sales Plan dialog has three steps, shown as dots in its footer: Step What you do Setup Name the plan, pick its dates and locations, and set the growth. Products Choose the products to set targets for. You can also skip this step. Review Check the targets seeded from last year at each location, then create the plan. Back and Next move between steps, and you can click a dot to go back to an earlier step. Creating sales plans is part of the Elevate plan. On a lower plan the Create Sales Plan button is greyed out. ## Setup: plan window Plan name (optional) comes first. Leave it empty and the plan is shown by its plan number, for example SP-00001 (the list reads “Unnamed sales plan”). Under Plan Window, pick a Quick period or set a Start date and an End date yourself: - This Quarter, Next Quarter - Rest of Year (today to 31 December) - This Year, Next Year - Next 12 Months (the default: today until the day before the same date next year) “Today” and the quarters and years are counted on your store’s calendar, in its time zone from Shopify (UTC when it can’t be read), not your computer’s. The end date must be on or after the start date, and a plan can span at most 1,100 days. A longer window is refused right under the dates, for example “This window is 1,101 days long. A plan can span at most 1,100 days.” Targets are planned day by day over the window, so every day from the start date to the end date gets its own target. Windows longer than a year. You can plan more than a year ahead. The dialog then says so under the dates, for example “400 days. That’s longer than a year, so targets repeat last year’s sales pattern for every further year.” ## Setup: locations and growth This part of the dialog is headed Locations & Growth. Locations. A sales plan sets one target per product and location, each seeded from that location’s own sales. All locations is ticked by default. Untick it to pick locations from the list; you can search it. All locations means every active location at the moment you create the plan. A location you add in Shopify later can be added to the plan with one click; see [Plans at several locations] (/features/inventory-planning/locations/#new-locations-since-the-plan-was-created). Growth is how much more (or less) you want to sell than last year. Choose how to set it: - Same % for every product (the default): one percentage for the whole plan, under Growth vs last year. - From each product’s sales history: Logistified measures each product’s growth at each location from what it sold there. See [Setup: growth from sales history] (#setup-growth-from-sales-history). Growth vs last year starts at 20%, and the readout next to it shows what that means, for example “×1.20 of last year’s sales”. - Enter a negative number to plan for less, for example -10. The readout then shows “×0.90 of last year’s sales”. - 0% keeps last year’s level, and -100% starts every target at 0: the readout says “Every target starts at 0.” - Growth can be anywhere from -100% to +900%. Between -99% and -100%, only -100% itself is allowed: “Growth below −99% must be exactly −100%.” - A comma works as the decimal mark too, for example 12,5. The growth applies to every product in the plan. You can change it for a single product later on the Products tab; see [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/#changing-growth-for-one-product). Click Next. If something is missing, the reason is shown next to the button, for example “Pick at least one location, or tick All locations.” ## Setup: growth from sales history Pick From each product’s sales history under Growth to let each product’s own sales set its growth, location by location, instead of one percentage for every product. Three settings appear: - Growth method: how the growth is measured. Average of methods is the default, and the line under the menu explains the method you picked. The methods are compared in [Growth from sales history] (/features/inventory-planning/sales-plans/products-and-targets/#growth-from-sales-history). - Leave out suspected stock-outs: off by default. Switch it on to leave out stretches when a product was probably out of stock, so they don’t pull its growth down. Then choose Stock-out detection (Unusual for this item, the default, or All long runs) and Minimum empty run (days) (5 by default, whole days from 1 to 365). See [Suspected stock-outs] (/features/inventory-planning/sales-plans/products-and-targets/#suspected-stock-outs). - Growth for products without enough data takes the place of Growth vs last year: the percentage for a product whose sales history at a location can’t measure its growth. It starts at 20% and works like the single percentage above. The growth is measured on the Review step, once you have picked the products. ## Setup: 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. So Logistified estimates a full year for it instead. The switch Estimate a full year for products that started selling within the last year sits under the growth settings. It is on by default, with either kind of growth. Under it, Seasonal shape from sets where the shape of the year comes from: - Established products of the same type at that location (the default): products with the same product type in Shopify that have sold at that location for more than a year. - Products I pick: products you choose yourself, on the Review step. The product’s own sales over its last 90 days set how much it sells; the source sets how those sales spread across the year. With growth from sales history and Leave out suspected stock-outs switched on, days with suspected stock-outs don’t count toward those 90 days. How the estimate works: [Products sold under a year] (/features/inventory-planning/sales-plans/products-and-targets/#products-sold-under-a-year). Switch it off to plan these products from their actual sales last year, day by day. You can still change this for single products on the plan later. To do that for only some products, leave it on and choose Use actual sales from last year for them on the Review step. ## Products Click Add products and choose where the products come from: Source What it does Browse products Pick products and variants from your Shopify catalog. Scan barcodes Scan a barcode or SKU, or type one and press Enter. Upload a spreadsheet Upload a file with one product per row, identified by Variant ID, SKU or Barcode. Example file gives you a template. From a forecast view Add every product in one of your saved forecast views, or build filters for a one-off view. “This view’s location filter is replaced by this plan’s locations.” Virtual materials Add raw materials you manage in Assemblified. From a forecast view is the fastest way to plan a whole category or supplier: you probably already have a view for it. You can mix sources. Each product is picked once: products you already picked are marked Already added. The picked products are listed under Products to plan with their Product, SKU and Barcode. Use the × on a row to remove one, or Clear all to start again. For more on the product sources, see [Adding products to a plan] (/features/inventory-planning/adding-products/). How many rows the plan gets. Each product is planned at each location, so a line above the list counts the rows, for example “12 products × 3 locations = 36 plan rows”. With All locations ticked it reads “12 products × 3 locations (all active) = 36 plan rows”. Under it, the dialog tells you how many products a plan with these locations and dates can hold, for example “This plan can hold up to 547 products (5 locations, 365 days).” - Above 500 rows the dialog warns that large plans load and edit more slowly. You can still create the plan. - When the plan would be too big, the dialog says how many products to remove, or how far to shorten the window, and Preview targets stays greyed out (“Too many rows. See above.” or “Too many daily values. See above.”) until it fits. Split a large range into two plans, for example one per category. When your list is ready, click Preview targets. ## Review Logistified works out every target from last year and shows them before anything is saved. Three tiles sum up the plan: - Target units: all targets added up. - Target revenue: target units × each product’s current price. Products without a price are left out and the tile says how many. - Locations with sales last year: for example 3 of 4. When every product gets the same growth %, a line at the top of the step names it, for example “Growth: +20% on last year for every product”. Click Change to go back to Setup and change it. The table below lists each target with its Last year sales, Target units and Target revenue. Use Group by to group it by Location (the default) or by Product. Each group shows its own subtotals. Groups with sales come first, the biggest at the top. When more than three groups sold nothing last year, those groups start folded; click one to open it. Targets can have decimals: they are planned per day to two decimal places, so a slow seller can have, for example, 0.25 units a day. Revenue uses each product’s current price, as the line under the table says. How a target is worked out: each day of the plan takes the same date one year earlier at that location, multiplied by the growth. So the target keeps last year’s seasonal shape. If that date is today or later, the day takes the same date two years earlier, so a plan that starts in the future reads the most recent full year; see [How a target is seeded] (/features/inventory-planning/sales-plans/products-and-targets/#how-a-target-is-seeded). Leap days: a February 29 in the plan takes last year’s February 28, and last year’s February 29 is added to the plan’s February 28, so a full year keeps all of last year’s sales. A day that sold nothing last year stays at 0. If the targets look wrong, click Back to change products, dates, locations or growth. A product was deleted in Shopify meanwhile. If a product you picked no longer exists in your store, the Review step says so, for example “Couldn’t compute the targets: 1 product is no longer available: Mug · Blue. Remove it to continue.” Click Remove and retry to drop it and preview the rest. ## Review: growth from sales history With From each product’s sales history, the Review step first analyses the sales history of every product at every location of the plan. A progress bar counts the targets, for example “Analysing sales history: 1,500 of 2,700 targets”. - Cancel stops the analysis, and Resume carries on where it stopped. - If part of the analysis fails, the step names the targets, for example “Couldn’t analyse the sales history of targets 501–1,000.”, with Retry. If a product you picked was deleted in Shopify meanwhile, Remove and retry drops it. - “Sales history analysis isn’t available right now. Try again in a few minutes.” means the analysis can’t run at the moment. Click Try again. Create plan waits until the analysis is complete, and the reason shows next to it, for example “Analysing sales history…” or “Resume the sales history analysis first.” Once the analysis is done, the step shows: - Growth method and Leave out suspected stock-outs again, above the table. A different method, or switching stock-outs on or off, updates the targets straight away (“Updating targets…”). A different Stock-out detection or Minimum empty run (days) analyses the sales history again. - A summary line, for example “From sales history: 2,310 targets · not enough data: 390 (growth set below) · to review: 41”. - Growth for products without enough data, right below the summary line: the same percentage as on Setup. Change it here and press Enter or click away. - A Growth column in the table. Each row shows the growth it gets and, under it, the method that measured it. Not enough data, in amber, means the product’s history at that location couldn’t measure a growth, so the row gets Growth for products without enough data. A row without sales last year shows “-”: its target starts at 0 whatever the growth. - A Review badge on a measured growth below −50% or above +50%, or on a trend that would bring sales down to 0. Logistified applies it as measured and never caps it. If you disagree, change the product’s growth on the plan’s Products tab after creating it. Hover or focus a Growth value to see where it comes from: - the units sold in each 12-month period compared, for example “Last 12 months (Jul 1, 2025 – Jun 30, 2026): 1,460 units”, then “The year before (…)” and “Two years before (…)”, - each method’s growth with its likely range, for example “Trend, damped (last 12 months vs the year before): +8%, likely between +1.2% and +15.2%”, and the note “The ranges show how precise the sales history is. They don’t bound the growth applied, which is damped and clamped.”, - with stock-outs left out, how many days were left out, for example “Left out as suspected stock-outs: 12 days”, or “No suspected stock-outs found”, - on a Not enough data row, why, for example “The growth method had too little sales history here (first sale on Feb 1, 2026).”, and the growth it gets instead: “Applied: +20%, the growth for products without enough data.” All rows, Not enough data and To review above the table show only the rows you want to check. The tiles and the notice about locations without sales still count every row. When you click Create plan, each product at each location keeps the growth shown: the measured one, or Growth for products without enough data. On the plan, hover a product’s Growth to see which method set it. ## Review: products sold under a year When some products started selling at a location less than a year ago, a Sold under a year group sits above the table. Its title counts the products, and the location targets when a product is at more than one location, for example “Sold under a year · 2 products · 3 location targets”. The line under the title counts what happened at each location, for example “1 estimated · 1 not estimated · 1 too new”, and “1 using actual sales” for products you opted out. The group starts open when a product needs your attention: one that isn’t estimated, is too new or waits for picks. Otherwise it starts folded, with that line still showing. Click its title to open or fold it. Each line is one product at one location: the product’s name, with at Berlin under it. Under that, a badge says what happened and a short line says why. Next to it are the product’s actual Last year sales there, its Estimated units (before growth) and its First sale date. On a phone they sit under the name. Badge Line under it What it means Estimated “Shaped like established Tops” or “Shaped like 3 picked products” The product is estimated: its own recent sales set how much it sells, and the established Tops at that location, or the products you picked for it, give the seasonal shape. Pick products “No similar products picked yet” The source is Products I pick, and you haven’t picked any for this product yet. Not estimated Why, for example “No established Tops here”, “The product has no product type” or “No sales here in the last 90 days” The product can’t be estimated. “No sales here in the last 90 days” means it sold nothing there on the days that count. Too new to estimate “Hasn’t sold here long enough yet” It needs at least 30 days there after its first month. Full-year estimate off “Uses its actual sales from last year” You chose actual sales from last year for this product, so its full year isn’t estimated. Hover a badge, or move to it with the Tab key, for more: for example how many established products shaped the estimate and how much they sold, or why a product can’t be estimated. A product that isn’t estimated uses its actual sales from last year. Logistified never switches it to another source on its own: pick similar products for it, or change its source on the plan later. Target units in the table includes the estimate: it is the estimate × the product’s growth. Last year still shows what the product actually sold, and an estimated product doesn’t count as having no sales last year. With growth from sales history, a product sold under a year has too little history to measure a growth, so it gets Growth for products without enough data. ### Picking similar products 1. In the Sold under a year group, tick the products you want to pick for, or tick All. If the group is folded, click its title to open it. 2. Click Pick similar products…. The dialog says how many products at how many locations you’re picking for. If the products you ticked already have different picks, the list starts empty and the dialog says so: Apply gives all of them the new list, and waits until you change it. 3. Click Add similar products and choose Browse products or Virtual materials. Pick products whose sales rise and fall over the year the way this product’s should, up to 10. 4. If some of them should count more, change their Weight. Every product starts at 1. 5. Click Apply. The targets are worked out again with your picks. - Each pick counts by its weight, not by how much it sells. - The picks are read at each product’s own location. Once the targets have been worked out with them, Last 12 months shows what each picked product sold there over the last year. Until then a new pick shows “-”, and the dialog says “Units show after the preview updates.” With products at several locations ticked, it reads “Varies by location”. - A picked product only counts where it has sold for a full year and sold in the last 90 days. Otherwise it is marked Left out. - A product can’t be picked for itself. A weight must be above 0: “Enter a weight above 0.” - To go back to the source under Seasonal shape from, open the dialog again and remove all picks, or tick the product and click Use the plan’s source. When you click Create plan, each product keeps the estimate shown. Products you add to the plan later are estimated from the source under Seasonal shape from. ### Using actual sales from last year To plan a product from its own actual sales last year, day by day, instead of an estimate, tick it in the Sold under a year group and click Use actual sales from last year. The targets are worked out again, and its badge reads Full-year estimate off. - A product has either picked products or actual sales from last year. Picking similar products for it replaces actual sales, and Use actual sales from last year replaces its picks. - To go back to the source under Seasonal shape from, tick the product and click Use the plan’s source. The button shows once a product has its own picks or uses actual sales. - When you click Create plan, these products keep their actual sales from last year. You can change their source on the plan later. ## Create plan or Create empty plan - Create plan, on the Review step, creates the plan with every target you previewed. - Create empty plan appears on the Products step instead of Preview targets when you haven’t picked any products. The plan is created with its dates and locations, and you add products from the plan page later. After creating, Logistified confirms with “Sales plan SP-00001 created” and opens the plan on its Products tab. The plan starts in Draft. Every product starts at the growth you set (with growth from sales history, at its own growth per location), and its revenue is units × price until you type your own. See [Statuses on a sales plan] (/features/inventory-planning/sales-plans/overview/#statuses-on-a-sales-plan) for confirming it. A sales plan is created all at once: if creating fails, nothing is saved and the dialog stays open with the reason. ## Locations with no sales last year Targets come from each location’s own history. Sales at other locations are never copied over. So where a product didn’t sell last year, its target starts at 0. A product sold under a year that gets an estimate is the exception: its estimate gives it targets, and it isn’t counted here. The Review step tells you before you create the plan: - an amber notice, for example “No sales last year at 1 of 4 locations”. Show locations lists which locations and products are affected, - a badge on each affected group, and an icon on each affected row. After the plan is created, a message repeats which locations had no sales last year. Set targets there by hand in the [plan grid] (/features/inventory-planning/sales-plans/plan-grid/) or on the Products tab. A new store with no history is the typical case. ## Walkthrough: create a sales plan 1. Open Inventory Planning › Sales Plans and click Create Sales Plan. The dialog opens on Setup. 2. Type a Plan name, for example Autumn/Winter 2027, and pick a Quick period such as Next Year. 3. Leave All locations ticked, or untick it and pick the stores to plan for. 4. Set Growth vs last year, for example 15, and click Next. 5. Click Add products › From a forecast view, pick a saved view and click Add products. The products are listed, with the row count above them. 6. Click Preview targets and check the tiles and the table on the Review step. 7. Click Create plan. The plan opens on its Products tab, in Draft. Tip For the whole job, from the first step to a confirmed plan, follow [Build a sales plan for next season] (/guides/build-a-sales-plan/). ## See also - [Sales Plans] (/features/inventory-planning/sales-plans/overview/): what a sales plan is and how the plan page works. - [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/): change growth, targets and revenue per product. - [Plans at several locations] (/features/inventory-planning/locations/): how one plan covers many locations. - [Adding products to a plan] (/features/inventory-planning/adding-products/): the product sources and the add-once rule. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/sales-plans/products-and-targets/ # Products, growth & targets Change a sales plan's growth, targets and revenue per product, and add or remove products. [Elevate plan] (/reference/subscription-plans/) The Products tab of a Logistified 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] (/features/inventory-planning/sales-plans/plan-grid/). ## 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 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] (#several-products-at-once). A product sold under a year shows under its name how it is estimated; see [Products sold under a year] (#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] (#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…] (#recalculate-targets) and the bin icon to [remove the product] (#removing-a-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] (/features/inventory-planning/sales-plans/overview/#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] (/features/inventory-planning/sales-plans/overview/#the-plan-page). ## 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] (/features/inventory-planning/sales-plans/creating/#review). 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] (#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 Every product starts with the growth you chose when you created the plan. Products you add later start at 0%. To change one product: 1. Click the product’s Growth field. 2. Type the new growth, for example 30 for +30% or -10 for -10%, and press Enter. The targets change straight away. 3. 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] (#products-sold-under-a-year)). ## 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] (/features/inventory-planning/sales-plans/creating/#setup-growth-from-sales-history)), and you can measure it again on a running plan with [Recalculate targets] (#recalculate-targets). ### 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 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 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] (#products-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 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 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] (/features/forecast/history-period/#excluding-stock-out-periods). ### 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] (#how-a-target-is-seeded), or the estimated year of a [product sold under a year] (#products-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 - 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] (#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 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] (#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. 1. 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] (#suspected-stock-outs). 2. 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] (/features/inventory-planning/sales-plans/creating/#review-growth-from-sales-history). 3. 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. 4. 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] (#changing-the-source). 5. 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 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 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] (/features/inventory-planning/sales-plans/creating/#setup-products-sold-under-a-year)) and can change it per product later. ### 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 1. 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”. 2. 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%. 3. 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. 4. 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 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] (#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 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 Use the Sold under a year section of the [Recalculate targets] (#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] (/features/inventory-planning/sales-plans/creating/#picking-similar-products). 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 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 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] (#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] (#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 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] (#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 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 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] (/features/inventory-planning/sales-plans/plan-grid/#typing-a-revenue). ### 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] (/features/inventory-planning/plan-analytics/#why-a-number-may-look-different-from-what-you-expect). ## 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] (/features/inventory-planning/sales-plans/creating/#products). - 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] (#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] (/features/inventory-planning/adding-products/). ## 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 1. Click Add products above the table and choose New product not in Shopify yet…. 2. Enter its Name as it reads on your sheet. SKU, Price and Product type are optional. 3. Pick its Locations. The locations you’re looking at are picked to start with. 4. 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] (/features/inventory-planning/sales-plans/plan-grid/) instead. 5. 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 - 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 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 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] (/features/inventory-planning/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 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”. Tip Removed a product at one location by mistake? Pick that location and use Actions › Add missing products… to plan it there again. See [Bring back products removed at a location] (/features/inventory-planning/adding-products/#bring-back-products-removed-at-a-location). ## 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] (/features/inventory-planning/adding-products/#bring-back-products-removed-at-a-location). ## 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 - [The plan grid] (/features/inventory-planning/sales-plans/plan-grid/): edit targets per period. - [Plans at several locations] (/features/inventory-planning/locations/): how edits on All locations are split. - [Adding products to a plan] (/features/inventory-planning/adding-products/): product sources and the add-once rule. - [Sales Plans] (/features/inventory-planning/sales-plans/overview/): the plan page and saving changes. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/sales-plans/plan-grid/ # The plan grid See and edit a sales plan's targets per week, month, quarter or year, in units or revenue, one cell or a whole period at a time. [Elevate plan] (/reference/subscription-plans/) The Plan tab of a Logistified sales plan is a grid: one row per product, one column per period. It shows when each target falls, and it’s where you shape a target over time, for example to push December harder. ## On this page - What the grid shows - Group by week, month, quarter or year - Editing a cell - Editing on All locations - Typing a revenue - Changing a whole period - Totals - Resetting revenue - Saving - Walkthrough: raise December’s target - Walkthrough: plan 10% more in Q4 - See also ## What the grid shows Each row is one product. Under its name, the row says where it’s planned: at one location Location: Berlin and the product’s growth, for example Growth: +20%; on All locations, All locations (3); with several locations picked, for example 2 locations (2). Each column is a period of the plan. Use the location switcher next to the tabs to choose the location; see [Plans at several locations] (/features/inventory-planning/locations/). Two tabs above the grid switch what the cells show: - Units: the target in units. Units can have two decimals, because targets are planned day by day; when any number in the grid has decimals, all show two. - Revenue (EUR): the target in your shop’s currency. A product without a price shows no price, its revenue cells can’t be edited here, and a note under the grid says how many products are left out of the revenue totals, for example “1 product has no price, so it is not included in the revenue totals.” To give it a revenue, type one on the Products tab first. The grid keeps your choice while you switch tabs or locations, and the Analytics tab uses the same Units or Revenue choice. Use Search products or SKUs… to narrow the rows; while you search, the toolbar shows how many rows match, for example 4 of 120. A cell that reads “-” is outside the product’s plan dates. Rows you changed but haven’t saved are highlighted. A plan without products shows “No products in this plan yet”: add them on the Products tab. A location of the plan without products reads “No products at location”. ## Group by week, month, quarter or year Group by sets the columns: Week, Month, Quarter or Year. The grid starts on Month. Group by Column header Week The calendar week, for example KW03 (calendar week 3), with its dates as day and month (12.01 – 18.01, 12 to 18 January). Weeks start on Monday. Month The month and year, for example Feb 2027. Quarter Q1 to Q4 and the year. Year The year, for example 2027. When the plan covers only part of a quarter or year, the header shows the dates it covers, for example Nov 15 – Dec 31. The Analytics tab’s planning matrix uses the same Group by, so the two always match. ## Editing a cell While the plan is Draft or Confirmed, every cell is a field. Click it, type the new target for that period and press Enter. - Enter keeps your entry and moves down one row. It’s saved when you click Save changes. - Arrow up and Arrow down move to the cell above or below. - Tab moves to the next cell. - Escape undoes what you typed. The cell stays selected, so you can type again or move on with the keyboard. - Clicking away also keeps your entry. A new number for a period is spread over its days the way the old one was, so the shape inside the period stays. If the period was 0, the number is spread evenly. Type 0 to clear a period; an empty cell changes nothing. A comma works as the decimal mark too. Targets can’t be negative. A number that can’t be used is put back and the toolbar says why, for example “Mug, Dec: a target can’t be negative.” Editing a cell doesn’t change the product’s growth. Revenue cells work the same way, except that Logistified first asks whether a new revenue should raise the units: see [Typing a revenue] (#typing-a-revenue). When the plan is Locked, Completed or Cancelled, the grid is read-only, and the column headers are plain labels. ## Editing on All locations On All locations, each cell is the period’s total over every location of the plan, and you can edit it. The number you type is split across the locations in proportion to what each one had in that period. If Berlin had 60 and Hamburg 40, and you type 150, Berlin gets 90 and Hamburg 60. If nothing was planned in that period yet, the split follows each location’s total for the product, and if the product has no target anywhere, the locations get equal shares. The locations always add up to exactly what you typed. Several locations picked. When you pick some of the plan’s locations in the switcher, each cell is the total over those locations, and what you type is split across them in the same way. The plan’s other locations keep their targets. To change one location only, pick it in the switcher first. More on this: [Plans at several locations] (/features/inventory-planning/locations/#editing-on-all-locations). ## Typing a revenue When you type a new revenue into a cell on Revenue (EUR), nothing changes yet: the cell keeps its old number and Logistified asks what the new revenue should mean. The question names the period and the change, for example “Revenue in Q1 2027: €100,000.00 → €200,000.00 (+100%)”, and offers three answers: - Raise units plans more units so that the period 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 in that period, like a units edit. Inside the period, each location keeps its day-by-day shape. Revenue stays units × price, so no blue dot appears. - Set revenue only keeps the units and stores the revenue you typed by hand, as before: see [Resetting revenue] (#resetting-revenue). - Cancel (or Escape) changes nothing. Before you answer, the dialog shows what Raise units (or Lower units) does, for example “Units 1,000 → 2,000 at Berlin, Hamburg. Revenue becomes €199,998.40.” That is the revenue the new units bring. It can be a few cents off what you typed, because units are planned to two decimals. If the period was at 0, the units are worked out from the product’s price. Rows units can’t move. Raise units and Lower units leave a location’s row as it is when its revenue doesn’t follow its units: a product without a price there, or a revenue typed by hand over 0 units or as 0. The dialog names each one, for example “Kept as they are (units can’t change their revenue): Mug at Munich (no price).” The other locations then make up the whole change. A revenue you typed by hand earlier, over units, stays typed by hand and changes by the same ratio as its units. When units can’t reach the new revenue at all, only Set revenue only is offered, and the dialog says why, for example “Products that units can’t change already bring €500.00 here. Enter €500.00 or more.” This also happens when the units would go above 1,000,000,000 in a cell. Typing the revenue that is already shown changes nothing and doesn’t ask. After your answer, the cell you typed into is selected again, so you can carry on with the keyboard. ## Changing a whole period While the plan is Draft or Confirmed, every column header (each week, month, quarter or year) is a button. Click one to change that period for all the products in view at once, for example to plan 10% more in Q4. Hover a header to see what it does, for example “Change Q4 2027 for the products in view”. The dialog is named after the period, for example Change Q1 2027, and says what it covers, for example “Q1 2027 · 45 products at 3 locations”. Which products and locations. The change covers the products in view: the locations picked in the switcher, and only the products that match your search. Search for a product line first to change just that line. The plan’s other locations and the products your search hides keep their targets. What you choose. - Action: Change by %, for example 10 for 10% more or -5 for 5% less, or Set total to to give the period a new total. - Measure: Units or Revenue. It starts on the one the grid shows. The result as you type. Under the field, the dialog shows what the change does, for example “Units 10,000 → 11,000 (+10%) · Revenue €100,000.00 → €109,998.12 (+10%).” On two or more locations, a second line says how it’s split, for example “Split across Berlin (60%), Hamburg (40%) in proportion to what each plans in Q1 2027.” If nothing is planned in the period yet, the split follows each location’s plan for the whole plan instead. How it’s split. Each location and each product keeps its share of the period: a product that planned a fifth of Q1 still plans a fifth after the change, and inside the period each one keeps its day-by-day shape. A revenue you typed by hand changes by the same ratio as its units. A change in revenue is made with units. Logistified works out the units that bring the new revenue, as Raise units does when you [type a revenue] (#typing-a-revenue). Rows whose revenue doesn’t follow their units (no price, or a revenue typed by hand over 0 units or as 0) keep their revenue, and the dialog names them. With Change by %, the rows units can move change by exactly that percentage, so the period’s total revenue moves a little less, and the dialog says so. Apply. Apply is greyed out until the change can be made. When it can’t, the dialog says why, for example “Enter a change of −100% or more.” or “That would put more than 1,000,000,000 in a cell.” Click Apply to make the change: the changed rows are highlighted, and the change waits in the save bar like any other edit. Click Save changes to keep it, or Discard changes to throw it away. Cancel closes the dialog without changing anything. ## Totals - The Total column on the right adds up each product over the whole plan. - The Total row at the bottom adds up every product per period, over the rows shown. Both stay in view while you scroll. On a narrow screen such as a phone, the product column gets narrower and the Total column scrolls in after the last period, so at least two periods stay visible and editable. Each revenue total is rounded to the cent once, so a product’s Total can differ by a cent from the sum of its rounded periods. ## Resetting revenue Revenue is units × price unless you type your own (which price: see [Revenue] (/features/inventory-planning/sales-plans/products-and-targets/#revenue)). When you type a revenue in any period and choose Set revenue only, the product’s revenue counts as typed by hand for the whole plan, not only that period, and a blue dot marks it next to the product’s name. From then on, a change to the units in a period scales that period’s revenue by the same ratio, and a growth change scales all of it. To go back to units × price, click the reset icon next to the product name: “Reset revenue to derived (units × price)”. The reset applies to the whole row, not to one cell. On All locations, the reset applies at every location. When more than one location has a revenue typed by hand, Logistified asks first: “Reset revenue at all locations?” Click Reset at all locations to confirm. With several locations picked, the reset applies at those locations only, and the question reads “Reset revenue at the selected locations?” with Reset at the selected locations. ## Saving Your edits, and changes you apply to a whole period, wait in the save bar at the bottom of the page together with changes on the Products tab. Click Save changes to save everything, or Discard changes to throw it away. See [Saving changes] (/features/inventory-planning/sales-plans/overview/#saving-changes). ## Walkthrough: raise December’s target 1. Open the sales plan and click the Plan tab. 2. Leave Group by on Month and Units selected. 3. In the location switcher, pick the store you want to push, for example Berlin. Leave it on All locations to raise every store together. 4. Click the product’s Dec cell, type the new target, for example 180, and press Enter. The row is highlighted and the Total column updates. 5. Click Save changes in the bar at the bottom of the page. Logistified confirms how many targets were saved, for example “Saved 1 target” at one location, or one per location on All locations. ## Walkthrough: plan 10% more in Q4 1. Open the sales plan and click the Plan tab. 2. Set Group by to Quarter. Leave the location switcher on All locations to change every store, and type in Search products or SKUs… to narrow the products, for example to one collection’s SKUs. 3. Click the Q4 header. The Change Q4 2027 dialog says how many products at how many locations it covers. 4. Leave Change by % and Units selected and type 10. Check the result line and how the change is split across the locations. 5. Click Apply. The changed rows are highlighted. 6. Click Save changes in the bar at the bottom of the page. Tip To raise a product over the whole plan rather than one month, change its Growth on the Products tab. See [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/#changing-growth-for-one-product). ## See also - [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/): growth, total targets and revenue per product. - [Plans at several locations] (/features/inventory-planning/locations/): the location switcher and how edits are split. - [Plan analytics] (/features/inventory-planning/plan-analytics/): the plan against actual sales. - [Sales Plans] (/features/inventory-planning/sales-plans/overview/): the plan page and saving changes. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/sales-plans/initiatives/ # Initiatives Name the reasons a sales plan sits above its baseline, see where each one lands and how far the plan still is from its goal, and find the changes that have no reason yet. [Elevate plan] (/reference/subscription-plans/) The Initiatives tab of a Logistified sales plan lists the named reasons behind the plan: a promotion, a new store, a price change, products back in stock. Each initiative adds units to the products, locations and months it names, and nowhere else. The tab shows, for each location, how the plan is built from its baseline, its initiatives and the changes made by hand, and how far it still is from the goal. ## On this page - What the tab shows - What you can do here - Adding or editing an initiative - Putting an initiative into the plan - Changes without a reason - Markers on the Products and Plan tabs - When the buttons wait - See also ## What the tab shows The tab covers the whole plan, every location at once, so the location switcher is hidden on it. Where the plan stands. One row for All locations, then one row per location: Column What it means Baseline What history says: last year’s sales, times the growth measured from them. Initiatives The units the initiatives in the plan add. Below it, the same weighted by each initiative’s probability (risk-adj.). No reason Units the plan holds above its baseline and initiatives without a named reason. Units lowered by hand show below it. Plan What the plan holds now. Goal The number the plan has to reach, for example your CEO’s. No goal when none is set for that location. Gap How far the plan is from the goal, in words: “3,810 short”, “420 over” or “On goal”. Below it, the gap with the risk-adjusted initiatives. A bar at the end of each row draws the same to scale: the baseline in slate, the initiatives in teal and the changes without a reason in amber, up to the plan’s edge in violet. A thin dark line marks the goal. Units and Revenue switch the figures, the same choice as on the Plan and Analytics tabs. The initiatives. One row per initiative, in number order (IN-001, IN-002, …): its lever, scope, dates, impact, probability, risk-adjusted units, owner, status and commitment, and whether it’s In plan. Out of date means its dates, scope or impact changed since it went into the plan; apply it again to update the plan. Checks flags what needs a second look, for example Overlaps IN-004 when two initiatives add to the same products in the same months, so they add up. Hover a flag for its figures. Once Claude has checked an initiative’s evidence, a badge says whether the data backs it: Supported, Partly supported, Not supported or Can’t verify. Flags never block anything. Changes without a reason. The products with the largest increases no initiative explains, each with Explain…. Set goals. Click Set goals… above the table, + Set goal in a location’s Goal cell, or Add goals… in the plan’s actions menu. All three open the same editor: one row per location, one column per month, in Units or Revenue. - Type a location’s Goal total and it is spread over the months: like the plan, like the baseline, or evenly by day. The months always add up to the total. - Or type each month. The total adds them up. Typing a new total over months you typed asks before it replaces them. - Paste a block of numbers from your spreadsheet into the first month: it fills the months and the rows below. - All locations is the sum of the locations. Tick Own goal to give it a number of its own, for example when your CEO sets only a company total. - Gap shows how far the plan would still be from the goal before you save. You can also share your goal sheet with Claude and ask it to set the goals. The Gap to goal card on the Analytics tab shows them month by month. See [Plan analytics] (/features/inventory-planning/plan-analytics/). ## What you can do here - New initiative: create one, with or without putting it into the plan. - Click a row to edit an initiative. The ⋯ menu also offers Apply…, Remove from plan… and Delete…. - Explain… a change without a reason. Claude can do all of this too, and works on the same initiatives, so what Claude adds shows up here. ## Adding or editing an initiative The dialog has the form on the left and a preview on the right. - Title, Lever (Price, Promotion, New product, Assortment, Distribution, Marketing, Trade terms, Stock-out recovery or Other), Owner and Notes. - Commitment: Committed or Discretionary. - Status: Idea, Proposed, Accepted, Rejected or Done. Only proposed, accepted and done initiatives can go into the plan. - Probability: how likely the initiative is to deliver, from 0 to 100%. It’s required, and it weighs the risk-adjusted figures. - Timing: the dates the initiative covers, inside the plan’s dates. - Locations and Products: every product, chosen products, or a product group (see [Product groupings] (/features/settings/product-groupings/)). - Impact: units, or a percentage of the baseline. Tick Split by month to say how many units fall in each month; the amount is then their total. ## Putting an initiative into the plan 1. Fill in the form. The preview shows what the initiative would do: the units it adds, where they land by location and month, and the gap to goal before and after, per location. It updates while you type. 2. Click Save and apply. The units are added to the products and months the initiative names, spread by each product’s baseline, and the plan’s numbers change. 3. To take an initiative out again, use Remove from plan…. It shows first how many units come off. If you lowered those products by hand since, the units that can’t come off stay, and they show as a change without a reason. Editing the dates, scope or impact of an initiative in the plan puts it in again with the new values: Save and re-apply. Setting its status to Idea or Rejected takes it out of the plan. ## Changes without a reason When you raise a product’s target by hand, on the Products or Plan tab, the extra units have no named reason. A product with more than half a unit of such an increase in any month gets an amber flag. Explain… opens a new initiative already filled in with that product, its locations and the units. Give it a title, a lever and a probability, then Save the reason. The units are already in the plan, so the initiative is saved without adding them again. ## Markers on the Products and Plan tabs - Products: under a product’s name, chips show what adds to it, for example +120 u from IN-003. Click one to open the initiative. An amber ▲ +240 u, no reason marks a change without a reason. Click it for the figures and Explain with an initiative…. The No reason choice above the table lists only those products. - Plan: small markers next to the product name show the same. Click them for the details. The markers show the saved plan. A product you’ve edited but not saved shows its markers faded until you save. ## When the buttons wait - While the plan has unsaved edits, Save and apply, Remove from plan… and the other buttons that change the plan’s numbers wait: “Save or discard your plan edits first. Applying changes the same products.” Changes to an initiative’s title, owner or notes can still be saved. - If someone else, or Claude, changed the same initiative while you had it open, the save stops and says so. Click Reload to see the latest, then redo your edit. - A Locked, Completed or Cancelled plan shows its initiatives but can’t change them. ## See also - [Sales plans overview] (/features/inventory-planning/sales-plans/overview/) - [Products, growth & targets] (/features/inventory-planning/sales-plans/products-and-targets/) - [The plan grid] (/features/inventory-planning/sales-plans/plan-grid/) - [Plan analytics] (/features/inventory-planning/plan-analytics/) Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/new-product-planning/overview/ # New Product Planning Forecast a product you have never sold from the sales of similar products you already sell, then order stock for the launch. [Enhanced plan] (/reference/subscription-plans/) A new product has no sales history, so the forecast has nothing to work with. A launch plan fills that gap: you pick products you already sell that you expect the new one to sell like, and Logistified builds a launch forecast from how they sold after their own first sale. You fine-tune it week by week, let it feed the forecast, and order the launch stock from it. ## On this page - What a launch plan is - When to use it - The list - The detail page - Edit details - Feeding the forecast - Completing a launch - What you can do here - See also ## What a launch plan is A launch plan (a new product plan) holds one or more new products. For each of them it plans the units you expect to sell, day by day, from the launch date over the plan’s horizon. That plan is the product’s launch curve. The curve comes from similar products: products you already sell that the new one should behave like. Logistified lines up each similar product’s sales from its own first sale, blends them by the Weight you give each one, and scales the result with Volume ×. A Volume × of 1.5 plans one and a half times what an average similar product sold. See [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/). Every launch plan gets a plan number such as NP-00001 and moves through the same statuses as every other plan: Draft, Confirmed, Locked, Completed and Cancelled. See [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/). New Product Planning comes with the Enhanced and Elevate plans. On a lower plan you can still open and review your launch plans, but not create or change them, and they don’t feed the forecast. See [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## When to use it - You’re launching a product you have never sold, and you want stock ready for its first weeks. - You know which existing products it will sell like: the previous model, the same cut in another fabric, last season’s bestseller in the same range. - You want the launch to show up in the forecast and reorder suggestions before it has sold anything. Individual products or a size group? Add a product as an individual product when it has its own launch curve. When a new product comes in several sizes that sell in a steady proportion, plan them as a [size group] (/features/inventory-planning/size-groups/): the product is forecast once and split across its sizes by percentage. Use an [inventory commitment] (/features/inventory-planning/commitments/overview/) instead when you expect a specific large order, and a [sales plan] (/features/inventory-planning/sales-plans/overview/) when you want to set sales goals for products you already sell. ## The list Open Inventory Planning in the top navigation and click the New Product Planning tile (or View All Launch Plans). The list shows one row per plan: Column What it shows Plan The plan’s name and, underneath, its plan number. Click it to open the plan. Product The first product in the plan. Launch The plan’s default launch date. Status Draft, Confirmed, Locked, Completed or Cancelled. Projected units Everything the plan’s launch curves add up to. Forecast Feeding when the plan adds its curves to your forecast right now: Feed into forecast is on and the plan is Confirmed or Locked. Not feeding when the switch is on but the plan is Draft, Completed or Cancelled. Off when Feed into forecast is off. Excluded when the plan was excluded from the forecast through the API. Click the Plan, Launch or Status header to sort the list. Search by name, plan number, SKU or product, filter by status, location, creation date or Launch date, and save the filters you use often. See [Search, filters & saved views] (/features/inventory-planning/search-and-filters/). Create a plan with Create New Product Plan. See [Creating a launch plan] (/features/inventory-planning/new-product-planning/creating/). ## The detail page The page header shows the plan number, the plan’s name under it, and the status steps on the right. Purchase orders created from the plan are linked right under the header. On the tab row, to the right of the tabs: - the location switcher, on a plan with several launch locations, - Edit details and the primary next-step button (Confirm on a Draft plan, Lock on a Confirmed one, Complete on a Locked one and Reopen on a Completed one), - Actions, which holds Edit details, the other status changes, Create purchase order (and View purchase order for each order created from the plan), Quick PDF export, Export, Rebuild forecasts, the location actions on a plan with several locations (Add location…, Remove location… and, when a location is missing products, Add missing products…), and Delete. The page has four tabs: - Plan: the Details card, the projected demand chart, and the table with the Week grid and Volume & launch tabs. The tab counts the plan’s products, a size group counting once. This is where you build the launch. See [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/). - Analytics: the plan next to what the products actually sold once they launched. See [Plan analytics] (/features/inventory-planning/plan-analytics/). - Documents: files you attach to the plan. See [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). - Activity: what happened to the plan, and comments from your team. The Details card shows the Default launch date, the Horizon in days, Total est. units and, on a plan with launch locations, Locations with their count (· All when the plan was created for all locations). A badge beside the title shows whether the plan feeds your forecast right now: Feeds forecast, Not feeding forecast or, once every product has sold with Auto-stop on first sale on, Stopped (first sale) (see [Feeding the forecast] (#feeding-the-forecast)). Hover or focus it to see why. Auto-stop on first sale appears when that option is on. Click the notes to edit them; they save when you click away or press Cmd+Enter or Ctrl+Enter. Press Escape to leave without saving. Plans at several locations have a location switcher next to the tabs. All locations (summary) adds every location up, and ticking several locations adds up just those. There you can also change a product’s similar products at all those locations at once; size groups are changed at one location. See [The location switcher] (/features/inventory-planning/locations/#the-location-switcher). A product you delete in Shopify keeps the rows it already has on the plan, but it is never copied anywhere new: Add location…, Sync locations and Add missing products… skip it. When Add missing products… skips one, its message names the product and says it “could not be added back here because it was deleted from the shop”. Once a plan is Locked, Completed or Cancelled, it is read-only: Edit details, Rebuild forecasts and the location actions go away, and the grid can’t be edited. A Locked plan can still order: see [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/). ## Edit details Edit details opens a dialog with the plan-wide settings: - Name. - Default launch date. The launch date new products get when you add them. It can’t be left empty. - Horizon (days): how far past the launch the plan runs, up to 180 days. Changing it resizes the curves at every location: a shorter horizon cuts them, a longer one keeps your week edits and fills the new days from the similar products. - Default volume ×: the Volume × new products get when you add them, from 0 to 10. - Notes. - Feed into forecast and Stop feeding on first real sale. See the next section. The default launch date and volume don’t move the products already in the plan. The dialog says so: “Default launch date and volume × apply to products added from now on. Change existing products on the Volume & launch tab.” See [The Volume & launch tab] (/features/inventory-planning/new-product-planning/launch-curve/#the-volume--launch-tab). Click Save changes. If a change can’t be saved, the dialog stays open and says why. Editing is possible while the plan is Draft or Confirmed. ## Feeding the forecast A launch plan can add its curves to your demand forecast, so the new product shows up in forecasts and reorder suggestions before it has sold anything. - Feed into forecast is on by default. The plan only feeds the forecast while it is Confirmed or Locked: a Draft plan never does, and its badge reads Not feeding forecast until you confirm it. Switch it off to keep the plan for ordering and analysis only. You can change the switch with Edit details while the plan is Draft or Confirmed. - Stop feeding on first real sale is off by default. Switch it on to drop a product from the plan’s forecast as soon as it has real sales of its own, so the forecast takes over from the plan. On a plan with several locations this happens location by location. The switch covers the whole plan; there is no per-product switch in the app. A plan can also be paused from the forecast through the REST or MCP API, which works while the plan is Locked too. Such a plan shows Excluded from forecast on its badge and Excluded in the list. To include it again, use the same API: the app has no Include in forecast for launch plans. A plan with Feed into forecast off shows Off in the list whether or not it was excluded. The list’s Forecast column and the badge on the Details card show which plans feed the forecast. See [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/) for how planned demand appears in the forecast. ## Completing a launch When the product has launched, click Complete (the primary button on a Locked plan, or in the Actions menu on a Confirmed one). Completing marks the plan as launched and stops it feeding the forecast; from then on the product is forecast from its own sales. If the plan’s horizon hasn’t ended yet, Logistified asks first: “Complete this plan early?” A Completed plan can be reopened with Reopen, which moves it back to Confirmed. Its numbers stay available on the Analytics tab. A Cancelled plan can’t be reopened. Tip Stop feeding on first real sale and Complete do different jobs. The switch hands each product over to its real sales automatically, one by one. Complete closes the whole plan when you decide the launch is over. ## What you can do here [Creating a launch plan] (/features/inventory-planning/new-product-planning/creating/) The Create New Product Plan dialog, section by section. [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/) How the curve is built, and how to fine-tune it week by week. [Size groups] (/features/inventory-planning/size-groups/) Plan the sizes of one product together with a size split. [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/) Create a draft purchase order that covers the launch. [Plans at several locations] (/features/inventory-planning/locations/) Launch at several stores, each planned from its own history. [Plan analytics] (/features/inventory-planning/plan-analytics/) Compare the plan with what the products actually sold. ## See also - [Plan a product launch] (/guides/plan-a-product-launch/): the whole launch, step by step. - [Plan sizes together with a size group] (/guides/plan-sizes-with-a-size-group/). - [Inventory Planning] (/features/inventory-planning/overview/): the three plan types side by side. - [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). - [Subscription plans] (/reference/subscription-plans/): New Product Planning comes with the Enhanced plan. Last updated: 7 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/new-product-planning/creating/ # Creating a launch plan Set up a new product plan in one dialog, with its launch locations, launch date, horizon, new products and their similar products. [Enhanced plan] (/reference/subscription-plans/) You create a launch plan in one dialog, Create New Product Plan. It asks for the essentials: where and when the products launch, which new products are in the plan, and which existing products they should sell like. Logistified builds the launch curves when you create the plan, and you fine-tune them on the plan’s page afterwards. ## On this page - Open the dialog - Plan Details: name and launch locations - Launch & Horizon - Individual products - Size groups - Forecast - Create the plan - Walkthrough: one product at two locations - See also ## Open the dialog Go to Inventory Planning › New Product Planning and click Create New Product Plan. The dialog has five sections: Plan Details, Launch & Horizon, Individual products, Size groups and Forecast. The buttons at the bottom (Details, Launch, Products, Size groups, Forecast) jump to each section. Every new plan starts in Draft. ## Plan Details: name and launch locations Name is optional. Leave it empty and the plan is named after its plan number, for example NP-00001 · New product. Launch locations are the stores or warehouses the products launch at. Pick one or more, or tick All locations to use every active location when the plan is created. A shop with a single location has it picked already. Each product is planned once per launch location, each with its own curve. With more than one location, the dialog shows how many plan rows that makes, for example “3 products × 2 locations → 6 plan rows”. A size group is counted with its sizes, for example “1 size group (4 sizes) × 2 locations → 8 plan rows”: every size is a plan row at each location. At each location, the curve is built from what the similar products sold at that location. A location where they never sold starts at zero, and the plan tells you so. See [Plans at several locations] (/features/inventory-planning/locations/). Large plans. Above 200 rows, the dialog warns: “That is over 200 rows, and large plans are slower to edit. You can still create it.” A plan also has a maximum size. The Individual products section shows how many products the plan can hold at your locations and horizon, and tells you when a selection doesn’t fit. Pick fewer products or locations, or a shorter horizon, or split the launch into two plans. ## Launch & Horizon Default launch date is day 0 of every curve: the day the products go on sale. Each product can have its own launch date, which overrides it. Horizon is how far past the launch the plan runs: 1, 2, 3, 5 or 6 months (about 30, 60, 90, 150 or 180 days). The default is 5 months. Later, Edit details shows the horizon in days (Horizon (days)), so 5 months reads as 150. ## Individual products Each individual product is forecast on its own curve. Add products offers Browse products, Scan barcodes, Upload a spreadsheet, From a forecast view and Virtual materials. See [Adding products to a plan] (/features/inventory-planning/adding-products/#ways-to-add-products). Each product row shows the product’s name with its variant and SKU underneath, and has: - Volume ×: 1 plans what an average similar product sold, 0.5 half of it, 2 twice as much. - a launch date: empty (it reads Plan date) means the plan’s default launch date. - a remove button. - Similar products: click Similar products to open the list, then Add similar product › Browse products or Virtual materials. Each similar product has a Weight, 1 by default. A higher weight gives that product more say in the curve. A product can be added without similar products. Its curve then starts at zero, and you plan its weeks by hand on the plan’s page. Picking several sizes of one product. When you pick two or more variants of one product with Browse products or Virtual materials, Logistified asks Group this product by size? Group by size puts them in a size group; Keep separate adds them as individual products. ## Size groups A size group plans the sizes of one product together: one forecast for the product, split across its sizes by a percentage. Click Add group to start one. Each group card has its own Add variants, its Volume ×, the size split with Split evenly, Normalize to 100% and Suggest from history, and Similar products for the whole group. A group card you leave without sizes isn’t saved with the plan. Everything about size groups is on the [Size groups] (/features/inventory-planning/size-groups/) page. ## Forecast - Feed into forecast, on by default: the plan’s curves are added to your demand forecast once the plan is Confirmed. - Stop feeding on first real sale, off by default: a product drops out of the plan’s forecast as soon as it has real sales of its own. You can change both later with Edit details. See [Feeding the forecast] (/features/inventory-planning/new-product-planning/overview/#feeding-the-forecast). ## Create the plan Click Create plan. While something is missing, the button is greyed out and a hint beside it says what: Hint What to do “Couldn’t load locations. Reload the page.” Reload the page, then open the dialog again. “Pick at least one launch location, or tick All locations.” Pick a location in Plan Details. “Set a default launch date to create this plan.” Set Default launch date. “Add at least one product or size group.” Add an individual product or a size group. “Too many products for this plan. See Products.” Remove products or locations, or pick a shorter horizon. While the plan is being created the button reads Creating… and the dialog can’t be closed. If the plan can’t be created, the dialog stays open and says why. Otherwise Logistified builds every curve from the similar products and opens the new plan on its Plan tab, in Draft. From there you check the curves, adjust them, and confirm the plan. See [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/). Note With several launch locations, a Volume × or weight you change in the dialog applies at every location. On the plan’s page you can give each location its own Volume × and similar products, rebuilt from that location’s history. ## Walkthrough: one product at two locations 1. Go to Inventory Planning › New Product Planning and click Create New Product Plan. 2. In Plan Details, type a name, for example Merino hoodie launch, and pick two Launch locations, for example Berlin and Hamburg. 3. In Launch & Horizon, set the Default launch date and leave Horizon at 5 months. 4. In Individual products, click Add products › Browse products and pick the new hoodie. The dialog reads “1 product × 2 locations → 2 plan rows”. 5. Open the product’s similar products, click Add similar product › Browse products and pick two hoodies you already sell. Leave their weights at 1. 6. Leave Feed into forecast on and click Create plan. The plan opens on its Plan tab, with a curve for the hoodie at each location. ## See also - [New Product Planning] (/features/inventory-planning/new-product-planning/overview/): the list, the detail page and the forecast feed. - [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/): fine-tune the curves after creating. - [Plan a product launch] (/guides/plan-a-product-launch/): the whole launch, step by step. - [Plan statuses & lifecycle] (/features/inventory-planning/lifecycle/): Draft, Confirmed, Locked, Completed and Cancelled. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/inventory-planning/new-product-planning/launch-curve/ # Similar products & the launch curve How a launch plan turns the sales of similar products into a forecast, and how to fine-tune it week by week, in the app or in a spreadsheet. [Enhanced plan] (/reference/subscription-plans/) The Plan tab of a launch plan is where you shape each product’s launch curve: the units you expect it to sell, day by day, from its launch date to the end of the plan’s horizon. Logistified suggests the curve from the similar products you picked. You change the similar products, their weights and the volume, or edit the weeks directly. ## On this page - How the forecast is built - The Plan tab - The chart - The Week grid - The product panel - Similar products - Choosing the history window - Similar products across locations - The Volume & launch tab - Saving your changes - Product actions - Rebuild forecasts - Editing in a spreadsheet - See also ## How the forecast is built 1. Each similar product’s sales are lined up from its own first sale. Day 1 of the new product is compared with day 1 of each similar product, even if they launched years apart. 2. The similar products are blended by weight. A product with Weight 2 counts twice as much as one with weight 1. When one similar product’s history runs out earlier than the others’, the rest carry on alone from that day. 3. The blend is scaled by Volume ×. 1 plans what an average similar product sold, 0.5 half of it, 2 twice as much. 4. The curve starts on the launch date and runs to the end of the plan’s horizon. On a plan with several launch locations, each location’s curve uses only what the similar products sold at that location, unless you change History from. Days with no history to borrow from plan 0 units. You can type your own numbers into those weeks. Why similar products and not a guess? Their real sales give the new product a realistic launch shape: a strong first week, a slow start that builds up, or a seasonal peak. ## The Plan tab From top to bottom, the Plan tab shows: - notices about the plan’s locations, for example a location where the similar products never sold, - the Details card, - the projected demand chart, - the table, with two tabs: Week grid and Volume & launch. On a plan with several launch locations, All locations (summary) adds the locations up, and ticking several locations adds up just those. There you can type week numbers (see [The Week grid] (#the-week-grid)) and change a product’s similar products at all those locations at once (see [Similar products across locations] (#similar-products-across-locations)). Size groups, and the launch date and product actions in a product’s panel, are changed at one location: pick it in the switcher. See [Plans at several locations] (/features/inventory-planning/locations/). ## The chart The chart stacks the products’ planned units, one colour per product. Its title sums it up, for example “Projected demand · 1,240 units across 3 products over 150 days”. A size group is named as one, for example “across 2 products and 1 size group (4 sizes)”. Long plans are shown in weekly or monthly totals. Click Products (it shows how many are visible, for example Products (3/3)) to choose what the chart shows. Under Show in chart, tick or untick products, or use Show all and Hide all. Hovering a week in the table highlights it in the chart. ## The Week grid The Week grid has one row per product and one column per period, with a Total column and a Total row. The grid shows whole units that add up both ways: a row’s periods add up to its Total, each period’s column to the Total row, and the Total row to the grand total. Four weeks of 108.5 units read 109, 109, 108 and 108, which is 434. A number you type stays as you typed it. - Group by switches the columns between Week, Month and Quarter. Week columns are calendar weeks, for example KW03 (calendar week 3) with its dates underneath as day and month. - Search products or SKUs… narrows the rows, and shows how many match, for example 2 of 5. - Edit a cell by clicking it and typing. A week’s number is spread evenly over its days. A month or quarter keeps its shape and is scaled up or down. - Cells outside a product’s launch window show a dash: the product hasn’t launched yet, or its horizon has ended. - A product at Volume × 0 can’t be edited until you give it a volume: hovering its cells says “Volume is ×0. Set a volume to edit the curve”. - Size groups are one row with their sizes beneath. See [Size groups in the Week grid] (/features/inventory-planning/size-groups/#size-groups-in-the-week-grid). Editing on All locations (summary). On a plan with several locations, the summary is editable too. A line above the chart explains it: “This is the total of all locations. A number you change here is split across them in proportion to what each one plans for that period.” When no location plans anything in that period yet, the number is spread evenly across them. The split lands on each location as an unsaved week edit, exactly as if you had typed it there. A product row on the summary opens its similar products at all those locations (see [Similar products across locations] (#similar-products-across-locations)); a size group’s panel opens at a single location only. Several locations picked. When you tick some of the plan’s locations, the grid, the chart and the Volume & launch tab add up just those, and the line reads “This is the total of 2 locations.” A number you change is split across the picked locations only; the plan’s other locations keep theirs. A plan you can’t edit. On a Locked, Completed or Cancelled plan, a Read-only notice under the tabs says so and what to do, for example “This plan is Locked. Release it to make changes.” The line above the chart then only says what is summed, for example “This is the total of all locations.” ## The product panel Click a product’s expander on the Week grid to open its panel. At one location, the panel belongs to that location’s product, and its list reads Similar products · location. On All locations (summary) or with several locations picked, the panel covers the product at all those locations instead: see [Similar products across locations] (#similar-products-across-locations). At one location, the panel holds the product’s similar products, Volume ×, Launch date, and a chart of how much each similar product contributes. - Volume × (0 to 10) scales the product’s current curve, including your week edits. When you raise it from 0, the note “Curve rebuilds on save” appears. - Launch date moves the product’s curve to a new start. Everything you change in the panel is saved with the page’s Save button above the table, together with your week edits. The panel has no save button of its own, so closing it or switching locations keeps your changes. ## Similar products Similar products lists what the product’s curve is built from: Column What it is Product, Variant, SKU, Barcode The similar product. Weight How much it counts in the blend. New similar products start at 1. 0 leaves it out. History from Which location’s sales it reads: Item’s location (the default), All locations, or locations you pick. History start The day its history is read from. Auto means its first sale. Click it to choose another day. - Add similar products › Browse products or Virtual materials adds more. - The × on a row removes a similar product. - As soon as you change the similar products or their weights, the curve and the chart show the rebuilt forecast. - Your changes count as unsaved changes on the page: Save above the table stores them with the curve you see, and Discard throws them away. Caution Changing a product’s similar products or weights rebuilds its curve, so week edits you made to that product are replaced. Changing only Volume × or Launch date keeps them. ### Walkthrough: swap a similar product 1. On the Week grid, click the product’s expander. Its panel opens. On a plan with several locations, pick a single location first to change only that location, or stay on All locations (summary) to change the product at every location at once. 2. Under Similar products, click Add similar products › Browse products and pick the product that fits better. 3. Click the × on the row of the similar product you want to drop. 4. Adjust the Weight of each similar product, if one should count more than the others. 5. Check the rebuilt curve in the panel’s chart, then click Save above the table. ## Choosing the history window By default, a similar product’s history is read from its first sale. When its first weeks don’t represent a normal launch, for example a launch that was delayed by a stock-out, choose a later start. Click a similar product’s History start cell. The History window dialog shows its weekly sales at the locations it reads from, with its first sale marked. - Click a week, or pick a date in History starts. Weeks before it turn grey: they are left out. - The line under the field says how many days of history that leaves, next to the plan’s length, for example “From Mar 03, 2025: 120 days of history for the 150-day plan.” Without a pick it reads “Auto: from the first sale (Feb 10, 2025).” followed by the same count. - Use this window applies the choice and rebuilds the product’s curve straight away. Week edits to that product are replaced. Click Save above the table to keep it. - Clear (auto) goes back to the first sale; click Use this window to apply it. If the similar product has no sales at those locations, the dialog says so, and that product adds nothing to the curve. Change History from to read from other locations. ## Similar products across locations On a plan with several launch locations, a product row opens on All locations (summary) and with several locations picked too. Its panel shows the product’s similar products at every location of the product in view, so you can change them everywhere at once instead of one location at a time. The panel’s title names the locations, for example Similar products · Berlin, Hamburg. When the product isn’t planned at every location you picked, it also says at how many, for example “(2 of the 3 selected locations)”. Past three names it reads, for example, “4 locations”; hover it for the names. One table per group of locations. A similar product may be used at some of the product’s locations and not at others, so the panel groups the similar products into tables by where they are used: - At both locations or At all 3 locations: used at every location of the product in view. - At Berlin and Hamburg (past three names, At 4 locations; hover it for the names): used at some of them. - Only at Munich: used at one. Values that differ show as a range. When the locations of a table use different values, the cell shows the range instead of one value: Weight 1–10, History start Mar 02, 2026 – Apr 10, 2026 (or Auto – Apr 10, 2026 when some locations read from the first sale), and History from Mixed (hover it to see each location’s choice). What a change does. - A change in a table (Weight, History from, History start) sets that one value at every location of that table. Typing over a range sets them all to the same value. - Add similar products adds the similar product at every location of the product in view, with Weight 1, History from set to Item’s location and History start on Auto. - The × on a row removes the similar product at that table’s locations only. - History start opens the History window dialog. When the table’s locations read the similar product’s sales from different places, the dialog has one tab per place: the location alone when the locations read their own sales, for example “Berlin”, and otherwise where the sales come from and which locations use them, for example “Munich (for Berlin, Hamburg)”. A line under the tabs repeats which locations the open tab is for. On a phone the tabs are a list to choose from. Use this window sets the start at every location of the table. - Volume × sets one volume at all those locations. While the locations differ, the field is empty and shows the range in grey, for example 1× – 2×. As at one location, it scales each location’s curve and keeps your week edits. - Launch date is shown, not changed here: launch dates stay per location. Change them on the [Volume & launch tab] (#the-volume--launch-tab) or at one location. Each location keeps its own curve. A change rebuilds each location’s curve from what the similar products sold at that location (or wherever its History from points), at that location’s own Volume ×. While the curves are rebuilt, the chart reads, for example, “Updating 2 of 3 locations…”. The chart shows the product’s curve added up over those locations. If a location’s new curve can’t be shown, the panel names the location, and Save builds that curve from the new similar products. Hand-edited curves. As at one location, changing the similar products rebuilds the curve and replaces your week edits. Before you change anything, the panel names the locations whose curves you edited by hand, for example “A similar-products change here rebuilds the hand-edited curves at Berlin, Hamburg, as it does at one location. Discard undoes it until you save.” Size groups stay per location. Where the product is part of a size group at one of the locations, the panel names it, for example “At Munich this product is part of the size group Tees; change it there.” Size groups are changed at one location, in the group’s panel, and a size group’s row on the summary doesn’t open. Saving. Each location you change counts as an unsaved row: Save above the table keeps them all, for example Save 3 rows, and Discard throws them away. The product actions (Apply to all locations, Reset to suggested forecast, Remove product) and the chart of what each similar product contributes are in the panel at one location. ## The Volume & launch tab The Volume & launch tab lists the same products, with two columns you can edit quickly across the whole plan and one total: - Launch date: when each product launches. - Volume ×: how much each product plans relative to its similar products. - Planned units: what the product plans in total (read-only). A size group’s row moves the launch date of all its sizes. Its volume is changed in the group’s panel, so a size shows via group. See [Size groups on the Volume & launch tab] (/features/inventory-planning/size-groups/#size-groups-on-the-volume--launch-tab). On All locations (summary), a value that differs between locations shows as a range. Typing a new value sets it at every location. With several locations picked, it sets it at the picked locations only, and a size group’s launch date moves only their sizes. ## Saving your changes Week edits, launch dates, volumes and a product’s similar products stay unsaved until you click Save above the table. The button counts what you changed, for example Save 3 rows. Discard throws the changes away, including unsaved settings in a size group’s panel. A size group’s panel is the one exception: it saves its own settings with Save & rebuild. While a group has unsaved settings, the bar says so, for example “1 size group has unsaved settings (Save & rebuild in the group)”. See [Size groups] (/features/inventory-planning/size-groups/). While the plan has unsaved changes, Lock, Complete, Cancel, Rebuild forecasts and Create purchase order are greyed out with “Save or discard your changes first”. So is a panel’s Apply to all locations while that product or size group has unsaved settings. They all work from the saved plan, so they wait until your changes are saved or thrown away. If you try to leave the page with unsaved changes, Logistified asks first. Changes are kept for the whole plan, so you can switch locations and save everything at once. “+2 unsaved at other locations (saved too)” reminds you of changes at locations you can’t see. If you click Discard while other locations have changes, Logistified asks first, because those are discarded too. ## Product actions The ⋯ menu (Product actions) in a product’s panel at one location holds: - Apply to all locations, on a plan with several locations: copies this product’s similar products and Volume × to the same product at the plan’s other locations. Each location is rebuilt from its own sales history. Locations where you edited weeks by hand keep their numbers unless you switch on Also overwrite hand-edited curves. It copies what is saved, so it’s greyed out with “Save or discard your changes first” while the product has unsaved changes. Confirm with Apply to N locations. - Reset to suggested forecast: replaces the product’s curve with a freshly suggested one, sets Volume × back to 1, and discards your week edits. - Remove product: removes the product and its forecast. All three ask for confirmation first. A reset shows as unsaved changes: Save keeps it, Discard undoes it. Remove product takes effect straight away and can’t be undone. On a plan with several locations it removes the product at the location you have open only: the dialog says how many other locations still plan it, and Actions › Add missing products… can add it back there later with a fresh forecast. When that location is the only one that plans it, the product leaves the plan. If the removal is refused, the dialog stays open and says why. ## Rebuild forecasts Actions › Rebuild forecasts rebuilds every curve in the plan from its saved similar products (and, for size groups, the saved split). Logistified asks “Rebuild all forecasts?” first, because it discards every week edit in the plan. Click Rebuild to go ahead; a message confirms it, for example “Rebuilt 6 forecasts”. Use it after you changed many similar products and want to start over from the suggestions. Rebuild forecasts is available while the plan is Draft or Confirmed, and greyed out with “Save or discard your changes first” while the page has unsaved changes. On a size group that has already launched, a rebuild changes the weeks from today on only. ## Editing in a spreadsheet For bigger changes, download the Week grid, edit it in a spreadsheet and upload it again. - Import / export › Download as XLSX or Download as CSV downloads every row of the plan, at every location, with one column per week, whichever location the switcher shows. A search you typed in the grid narrows the download too. The rows are identified by Item ID, SKU and Location; Location holds the location names you see in the app. - Only the week numbers are read back. Changing a product’s name, launch date or total in the sheet changes nothing. An empty cell leaves that week as it is. - Weeks outside a product’s launch window are skipped. To plan them, change the product’s launch date or the plan’s horizon first. ### Walkthrough: edit weeks in a spreadsheet 1. On the Week grid, click Import / export › Download as XLSX. 2. Change the week numbers you want in the spreadsheet and save the file. Keep the Item ID, SKU and Location columns as they are. 3. Back on the plan, click Import / export › Upload edited sheet and choose the file. 4. Check Review import: how many rows matched, how many products and weeks changed, and any rows that were skipped and why. 5. Click Apply to grid. The new weeks appear in the grid as unsaved changes. 6. Click Save. Nothing is saved before this step. Rows are matched by Item ID, or by SKU and Location when the Item ID is missing. If a row can’t be matched, the review says why, for example a product that isn’t in the plan or a SKU that appears at two locations. Add the product to the plan first, or keep the Item ID column in the sheet. ## See also - [Creating a launch plan] (/features/inventory-planning/new-product-planning/creating/): pick the similar products when you create the plan. - [Size groups] (/features/inventory-planning/size-groups/): plan the sizes of one product together. - [Plans at several locations] (/features/inventory-planning/locations/): the location switcher and All locations (summary). - [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/): order stock from the curve. - [Plan a product launch] (/guides/plan-a-product-launch/). Last updated: 7 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/size-groups/ # Size groups Plan the sizes of one new product together, with one forecast for the product and a size split that always adds up to 100%. [Enhanced plan] (/reference/subscription-plans/) A size group plans the sizes of one product together in a New Product Planning plan. Logistified forecasts the product as a whole, then splits that forecast across its sizes by a percentage you control: the size split. ## On this page - What a size group is - Create a size group - Add a size to an existing group - Size groups in the Week grid - The group panel - Suggest a split from history - Save & rebuild - After launch: switch to the actual size mix - Size groups on the Volume & launch tab - Ordering a size group - Size groups at several locations - See also ## What a size group is Everything that describes the product is set once, for the whole group: - One set of similar products. The group’s forecast is built from what those products sold. - One Volume ×. It scales the whole group up or down. - One launch date. Every size launches on it, unless you move a single size on purpose. - One size split. Each size gets a share, and the shares always add up to 100%. Each size’s forecast is its share of the group’s forecast. With a split of 20 / 50 / 30 for S, M and L, M plans half of everything the group plans. Size group or individual products? Use a size group when the sizes are one product and you expect them to sell in a steady proportion, as with clothing or shoes. Add variants as individual products when each one needs its own similar products, its own volume or its own launch, for example colors you expect to sell very differently. ## Create a size group ### In the Create New Product Plan wizard The Size groups section comes after Individual products. Click Add group to start a group card. Each card has: - the group name (an unnamed group takes its product’s title when you add its first sizes), the group’s Volume × and a remove button, - a Sizes block with Add variants at its top right. It offers Browse products, Scan barcodes, Upload a spreadsheet and Virtual materials. Each size row has its share, a launch date (the plan date unless you pick another) and a remove button, - the total of the split, for example Total 100%, green at 100% and amber otherwise, with Split evenly, Normalize to 100% and Suggest from history. A line under the buttons says “The mix should add up to 100%.” while it doesn’t, and why a button is greyed out, for example “Already split evenly.” or “Add similar products below to suggest a mix.” A split that doesn’t add up to 100% is still scaled to 100% when the plan is created, - Similar products for the whole group. Adding sizes splits the group evenly again. Under the name, the card reads “Sizes of product”. It turns amber when the sizes come from more than one product, because a size group usually holds one product’s sizes. A group card you leave without sizes isn’t saved with the plan. ### From a product pick When you add new products and pick two or more variants of the same product with Browse products or Virtual materials, in the wizard’s Add products or on a saved plan, Logistified asks Group this product by size? - Group by size puts them in a new size group with an even split. - Keep separate adds them as individual products. New products that come from scanning barcodes, a spreadsheet or a forecast view are added as individual products. To put scanned or uploaded sizes in a group, use the group card’s Add variants in the wizard. ## Add a size to an existing group On a saved plan with size groups, Add products opens a menu. Next to New products there is one To “group” entry per group, with Browse products and Virtual materials. A size added this way gets an even share: with four sizes after the add, 25%. The other sizes scale down in proportion, so the group still adds up to 100%. The group’s panel then says, in amber, “size was added with an even share. Check the split.” The note goes away when you save the group or reload the page. A variant that’s already in the plan, as an individual product or in a group, is marked Already added. See [Adding products to a plan] (/features/inventory-planning/adding-products/). ## Size groups in the Week grid On the Week grid tab, a size group is one row with its sizes indented beneath it. The group row shows the sum of its sizes and how many sizes it has. - Only the group row expands. Click its expander to open the group panel. Sizes have no expander and no panel of their own: everything about a size is managed on its group’s panel. - Sizes keep their week cells. You can still type into a size’s weeks, and show or hide a single size on the chart with Products › Show in chart. Week edits are saved with the page’s Save button. ## The group panel Open the group panel from the group row’s expander. On a plan with several locations, pick a single location first: the panel belongs to that location’s group. ### Similar products Similar products for the whole group lists the products the group’s forecast is built from, with their weights. Use Add similar products and choose Browse products or Virtual materials. ### Volume × and launch date Volume × scales the whole group. Launch date moves every size of the group. The line under it says “Every size launches on this date. Change a single size’s date on the Volume & launch tab.” When the sizes launch on different dates, the panel shows the range instead and starts with “Sizes launch on different dates. Picking a date moves every size.” To move one size on its own, use the [Volume & launch tab] (#size-groups-on-the-volume--launch-tab). A date picked here is saved with the page’s Save button. ### The size split The Size split table has one row per size: Product, Variant, SKU, Barcode (only when a size has one) and Share. Its title shows the total, for example “· 100% of 100%”, green at 100% and amber otherwise. On a plan with several locations the title names the location, for example Size split · Berlin. - Even split gives every size the same share. - Normalize scales the shares to add up to 100% and keeps their proportions. - Suggest from history fills the split from what the similar products sold, size by size. See [Suggest a split from history] (#suggest-a-split-from-history). Whatever you type, the group is saved at 100%. If your shares add up to 90%, Logistified scales them up in proportion, so the group never plans less than its forecast. While the total is not 100%, the title says so beside it: “Save & rebuild scales the shares to 100%.” Click Normalize to see the scaled shares before you save. ### Remove one size Each size has a trash button. Logistified asks Remove this size? first. The other sizes take the removed size’s share in proportion, and the dialog says what that means for the total: - Usually: “Its share goes to the other sizes, so the group’s total stays the same.” - When other sizes have week edits, it names them, for example “except M, which keeps its edited weeks”. Their weeks don’t change, so the group’s total can. - When the group has launched, the share moves “from today on” and “Weeks before stay as planned.” On a plan with several locations, the size is removed only at the location you have open, and the dialog names that location. The removal can’t be undone. If it’s refused, the dialog stays open and says why. The last size of a group has no trash button. To remove it, remove the whole group. ### Group actions The ⋯ menu (Group actions) next to Add similar products holds: - Apply to all locations, on a plan with several locations. It copies the group’s similar products and Volume × to the same group at the plan’s other locations. See [Size groups at several locations] (#size-groups-at-several-locations). - Reset sizes to suggested forecast. Every size goes back to its share of the group’s suggested forecast, and your week edits are discarded. Logistified asks “Reset to the suggested forecast?” first. The reset is saved with the page’s Save button, and Discard undoes it until then. - Remove group. It removes the group and all of its sizes from the plan at every location; the dialog says how many. This cannot be undone. ## Suggest a split from history Suggest from history opens Suggest size split from history. It needs at least one similar product. How the split is worked out: 1. Each size borrows from a size of the similar products. By default a size borrows from the size with the same name, for example M from M. The Based on column shows the choice for each size; change it to borrow from another size. Your choice applies to every similar product that has that size. 2. Each similar product gets its own size shares from what it sold in those sizes. 3. The products’ shares are blended by their weights. At equal weight, a product that sold 20 / 50 / 30 and one that sold 30 / 40 / 30 give 25 / 45 / 30, even if one sold many more units. A product with no sales in these sizes adds nothing, and the others share its weight. The dialog names it. If every product with sales has weight 0, they count equally. Each size shows its suggested share and the number of sales behind it. If no size can be matched, its Based on reads Not set and the size gets 0%. Confidence. A line at the top says how much history backs the split, for example “Based on 34 sales, low confidence.” Confidence Sales behind the split What it means None 0 No similar product sold in these sizes. The split is even. Low fewer than 100 A rough guide. Shares can move by several points as sales come in. Medium 100 to 399 A useful starting point. High 400 or more Shares are well established. Before applying. Click Apply split. When confidence is none or low, or a size would get 0%, the dialog warns you first, for example “Only 34 sales back this split.” or “XL would get 0 %, so it is not planned.” The button then reads Apply anyway. Applying fills the split. In the group panel, nothing is saved until you click Save & rebuild. In the wizard, the split is saved when you create the plan. ## Save & rebuild Save & rebuild saves the group’s similar products, Volume × and size split, then rebuilds the group’s forecast (its weekly curve) and splits it across the sizes again. Picking Use this window in a similar product’s sales history does the same straight away. Keep your week edits? If some sizes have saved week edits, Logistified asks first and names them, for example “2 sizes have week edits: M, L.” - Keep my edits (preselected): those sizes keep their weeks. - Replace with the rebuilt curve: those sizes lose their week edits and get their share of the rebuilt forecast. If no size has week edits, the group saves straight away. “Save or discard your week edits first”. While a size of the group has week edits you haven’t saved yet, Save & rebuild, Use this window and the After launch buttons are greyed out with this message beside them. Click Save or Discard on the page first. This keeps the two saves from overwriting each other. Tip Week edits and a new launch date are saved with the page’s Save button. Similar products, Volume × and the size split are saved with Save & rebuild in the group panel. Unsaved group settings are kept. If you close the group panel or switch locations before Save & rebuild, the changes are still there when you open the panel again. The bar above the table reminds you, for example “1 size group has unsaved settings (Save & rebuild in the group)”. Discard on the page throws them away after asking first, and Logistified also asks before you leave the page with them unsaved. ## After launch: switch to the actual size mix Your split is a guess until the product sells. Once it does, the group panel shows how the sizes are really selling next to the split you planned, and you decide whether the rest of the season should follow the real mix. Where it is. Open the group row’s expander on the Week grid, at a single location. The After launch section sits under Size split. Before the first size launches, a line there says the actual sales mix will show up after launch. When it shows. Logistified compares the sizes once the group has sold for at least 14 days and at least 30 units at that location. Until then it says how far along you are, for example “Not enough sales yet to compare the size mix: 9 days and 21 units since Oct 7. It shows after 14 days and 30 units.”, or “No sales yet since Oct 7. It shows after 14 days and 30 units.” when nothing has sold. What it shows. One row per size: - Pre-launch: the share you planned before launch. - Planned now: the share the group uses today, shown once it differs from the pre-launch share. - Selling: the size’s share of what the group sold at this location. - Units: what the size sold at this location. - All locations: the size’s share across every location of the plan, on plans with several locations. The header gives the sales period and a confidence label, for example “Sales Oct 7 to Oct 28 (21 days) · Medium confidence”. The confidence uses the same scale as Suggest from history: a few dozen sales can still move by several points. Under the table, a line totals the units sold since launch at this location. Sales are counted from the day the last of the group’s launch sizes launched, so a size that launched later doesn’t look less popular. A size that hasn’t launched yet reads “Launches date” and keeps its share. Sizes you add after launch don’t restart the comparison. Such a size reads “No sales history yet” until it has sold for 14 days and at least 30 units on its own; then it joins the comparison. Until then, Use actual mix keeps that size’s share and gives the rest to the other sizes by how they sell. Once it joins, sales are compared from the day that size launched. Sold out sizes. A size that is out of stock now gets the warning “Sold out now. Its real share may be higher.” One that sold nothing for a week or more while the other sizes kept selling gets “No sales from to to while other sizes sold. It may have been out of stock, so its real share may be higher.” A size can only sell what’s on the shelf, so its real share may be higher than it looks. Adjust its share by hand if you know it would have sold more. Use actual mix for the remaining weeks. Click it to see exactly what would change before anything is saved: the dialog, for example “Use the actual sales mix from Oct 28?”, shows each size’s share now and after, and the units it plans from today on. Then: - Only the weeks from today change. Earlier weeks stay as you planned them, so Plan analytics still compares what you sold with what you planned at the time. - Sizes with week edits are listed. Replace their remaining weeks is preselected; their earlier weeks stay either way. Keep my edits leaves those sizes as they are, and the dialog shows how far the sizes then plan above or below the group. - Also at the other N locations, each with its own actual mix (plans with several locations) gives every location its own actual mix. Locations that haven’t sold enough yet are named and skipped. - The dialog says how the forecast is affected: the forecast uses the new split from today, unless the plan doesn’t feed the forecast, or Stop feeding on first real sale has already stopped sizes that sold. Click Use actual mix to apply it. A message confirms it, for example “Size split switched to the actual sales mix from Oct 28”, and offers Undo. Later, Back to the pre-launch mix returns to the split you planned, again from today. On a Locked plan the section is read-only and says “Unlock the plan to change the split.” Click Release to change it. Note Once a group has launched, every change to it applies from today: a share you type, Save & rebuild, Rebuild forecasts, Apply to all locations, and adding or removing a size. Weeks before today keep what was planned. A size added after launch starts today. The plan’s horizon can’t be shortened to end before today while a group has launched. Here “today” changes at midnight UTC (universal time), like Plan analytics, because the sales it compares are counted in UTC days. See it in Analytics. See sizes in Analytics opens [Plan analytics] (/features/inventory-planning/plan-analytics/) with the group’s sizes selected at this location, to compare planned and actual week by week. ## Size groups on the Volume & launch tab The Volume & launch tab lists the same rows as the Week grid. - The group row’s launch date moves every size of the group. When the sizes launch on different dates, it shows the range. - A size row’s launch date is that size’s own. This is the one place to move a single size away from the group’s date. - Volume belongs to the group. The group row shows it read-only, and a size row reads via group. Change it in the group panel. ## Ordering a size group Create purchase order rounds a size group once, not each size on its own. Five sizes that each need 2.2 units order 11 units together, not 3 each (15). The units are then shared out across the sizes. With One PO per location each location’s group is rounded on its own; One combined PO rounds the group once across all its locations. On a plan with size groups, the dialog has At least 1 per size, off by default. Tick it to order at least 1 unit of every size, taken from the largest sizes. If the group needs fewer units than it has sizes, the order grows to 1 per size. On a combined PO that means one unit per size on the whole order, not per location. After launch, the dialog covers from today by default, so a reorder follows the size split the group uses now and takes off the stock you already have or have on order. Individual products are rounded up one by one. See [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/). ## Size groups at several locations On a plan with several launch locations, each location has its own copy of the size group. - Each copy is planned on its own. Its forecast comes from that location’s sales history, and you can give it its own split, Volume × and similar products. - All locations (summary) shows one row per group with every location added up. Settings are per location, so pick a location to open the group panel. - Apply to all locations copies similar products and Volume × to the other locations. Apply split to all locations, in the Size split title row, copies the split as well. Both copy the group as last saved, so while the panel has unsaved settings they are greyed out with “Save or discard your changes first”: click Save & rebuild first. Each location is still rebuilt from its own history. Week edits at those locations are kept unless you switch on Also overwrite hand-edited curves. - When the split differs between locations, the panel says “Split differs across locations. Applying this one replaces the others’ splits.” - Remove group removes the group at every location. - Add products › To “group” adds the size at every location of the plan. - Removing one size removes it only at the location you have open. ## See also - [Plan sizes together with a size group] (/guides/plan-sizes-with-a-size-group/): a size group from start to order, step by step. - [New Product Planning] (/features/inventory-planning/new-product-planning/overview/): launch plans, the list and the detail page. - [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/): how a forecast is built from similar products. - [Ordering for a launch] (/features/inventory-planning/new-product-planning/ordering/): the Create purchase order dialog. - [Adding products to a plan] (/features/inventory-planning/adding-products/): why a variant can only be in a plan once. - [Plan analytics] (/features/inventory-planning/plan-analytics/): compare the plan with what actually sold. - [Subscription plans] (/reference/subscription-plans/): size groups come with New Product Planning on the Enhanced plan. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/inventory-planning/new-product-planning/ordering/ # Ordering for a launch Turn a launch plan's first weeks into a draft purchase order, one per launch location or one combined. [Enhanced plan] (/reference/subscription-plans/) In Logistified, a launch plan knows how many units each new product should sell in its first weeks. Create purchase order turns that into a draft purchase order, so the launch stock is ordered from the same numbers the forecast uses. ## On this page - Create purchase order - Coverage window - One PO per location or one combined PO - What will be created - How quantities are rounded - Suppliers - If only some orders are created - After creating - When it’s greyed out - Walkthrough: order 8 weeks of launch stock - See also ## Create purchase order On the launch plan, open Actions › Create purchase order. The dialog creates one draft PO line per variant, sized to cover the plan’s demand over a window you choose. It works while the plan is Draft, Confirmed or Locked: ordering doesn’t change the plan, so a Locked plan can order too. The order is sized from the plan as saved. Save or discard your changes on the Plan tab first; until then the menu item is greyed out (see [When it’s greyed out] (#when-its-greyed-out)). A launch plan creates purchase orders only. It can’t create transfer orders or Shopify draft orders; those are for [inventory commitments] (/features/inventory-planning/commitments/ordering/). ## Coverage window Coverage window (days) is how many days of the launch the order covers. The default is 60 days. Cover from sets where the window starts: - Launch: the window starts on each product’s launch date. A product launching on Mar 1, 2027 with a 60-day window orders what the plan expects it to sell from Mar 1 to Apr 29, 2027. Stock you already have or have on order is not subtracted. This is the default before launch. - Today: the window starts today, for a reorder once the product is selling. Weeks that already passed are not ordered again, and each line takes off the stock that location has on hand and on order. A product or location that launches later covers only the days of the window after its launch: with a 30-day window, a product launching in 20 days orders its first 10 days. This is the default once any product of the plan has launched. The line under the choice says which one is active: “Covers the window from each product’s launch date.” or “Covers the window from today, minus each line’s stock on hand and incoming at its location.” The quantity is the plan’s demand in that window, minus that stock with Today. ## One PO per location or one combined PO Under Purchase orders, choose: - One PO per location (the default): one draft PO for each launch location, delivered to that location. - One combined PO: a single draft PO for every location. The same variant at several locations becomes one line with the total. Pick a Destination location (optional) for it, or leave No destination. With a single launch location, both create one PO. ## What will be created What will be created previews the result before you click: one row per PO with its Location, Lines and Units, and a total line such as “2 purchase orders · 14 lines · 860 units”. With Cover from on Today, a Stock subtracted column shows the stock on hand and on order that was taken off. A combined PO shows one row, All locations. The preview updates when you change the window, Cover from, the split or At least 1 per size. While it loads it reads “Calculating order quantities…”; if it can’t be worked out, it says “Couldn’t calculate the order quantities.” You can still create the order: its quantities are worked out when you click. If no product has anything to order in the window, it says “No variant has a positive order quantity in this window.” and the create button is greyed out. This happens, for example, with Cover from on Today when the stock you already have and have on order covers the whole window. Lines with 0 units are left out of the PO. ## How quantities are rounded - Individual products are rounded up one by one. A product that needs 41.3 units orders 42. - Size groups are rounded once, for the whole group. Five sizes that each need 2.2 units order 11 together, not 3 each (15). The 11 units are then shared out across the sizes by the split. - At least 1 per size, on a plan with size groups, is off by default. Tick it to order at least 1 unit of every size, taken from the largest sizes. If a group needs fewer units than it has sizes, the order grows to 1 per size. With Cover from on Today, a size whose own stock already covers it isn’t given an extra unit. - One combined PO rounds the locations together. A variant’s needs at every location are added up and rounded once, because the combined PO has one line per variant. A size group is rounded once across all its locations, and At least 1 per size means one unit per size on the whole order, not per location. With One PO per location, each location is rounded on its own. See [Ordering a size group] (/features/inventory-planning/size-groups/#ordering-a-size-group). ## Suppliers The draft PO has no supplier, and a launch plan doesn’t split the order by supplier. A new product often has no supplier set up yet, so you choose it on the draft PO before sending. Only [inventory commitments] (/features/inventory-planning/commitments/ordering/) split their orders into one PO per supplier. ## If only some orders are created When something goes wrong on the way, the dialog stays open and lists the results under Purchase order creation results. The settings above lock, so a retry uses exactly the same coverage window, Cover from, rounding and split. - Open PO-… links every order that was created. - “Order created; review its lines.” means the order exists but some of its lines may not have been saved. Open it and check its lines. - “Location: order not created.” names a location whose order failed. - “Location: order was created and needs review. Do not create it again.” and “Location: order was created but its details were not returned. Do not create it again.” mean an order exists. Look for it in your purchase orders before ordering again; these locations are never retried. - “PO-… was created but could not be linked to this plan … Contact support to relink it; there is no relink action here. Do not create it again.” The order exists but doesn’t show on the plan. Opening it doesn’t repair the link, and there is no relink button. With One PO per location, the button becomes Retry failed locations: it retries only the locations whose orders were not created, and created orders are never created again. The message above it says “Some purchase orders still need attention. Retry only the failed locations; created orders will not be recreated.” When nothing can be retried, for example on a combined PO, the button reads Nothing to retry and the message says “Open the orders above to review them. There is nothing to retry.” Close closes the dialog. If an attempt ends with an unexpected error or no response, check the plan’s linked orders and your order list before trying again. The error alone does not tell you whether an order was created. ## After creating Click Create draft PO. With One PO per location and several locations, the button counts the orders, for example Create 2 draft POs. A message confirms what was created, for example “Draft PO created: 3 lines, 120 units”, or with several POs “2 draft POs created: Berlin (3 lines, 120 units), Hamburg (3 lines, 80 units)”. Open PO jumps to the new purchase order; with several, Open POs opens the purchase order list with the new ones highlighted. The plan stays open, and the new purchase order appears in the Linked purchase order bar at the top of it (Linked purchase orders once there are several), by its number. The draft PO is a normal purchase order. Set the supplier, check prices and quantities, and send it as usual. See [Purchase orders] (/features/supply-orders/purchase-orders/overview/). On the plan, Actions now lists View purchase order for each purchase order created from it (named by its number) and Create another purchase order. Use it to reorder once the product is selling: once any product of the plan has launched, the dialog opens with Cover from on Today, so weeks that already passed and stock already on hand or on order are not ordered again. Every purchase order stays linked to the plan, and the plan’s Activity names each one by its number. ## When it’s greyed out Message beside the menu item Why What to do “Plan is Completed” or “Plan is Cancelled” Ordering works while the plan is Draft, Confirmed or Locked. Reopen a Completed plan. A Cancelled plan cannot be reopened. “Add a product first” The plan has no products. Add a product on the Plan tab. “Save or discard your changes first” The Plan tab has unsaved changes, or a save is still on its way. The order is sized from the saved plan, so it waits. Click Save (or Save & rebuild in a size group’s panel), or Discard. Inside the dialog, the create button is greyed out while the coverage window is empty or the preview says no variant has a positive order quantity. New Product Planning comes with the Enhanced plan. On a lower plan the plan can be reviewed but not changed: Create purchase order is greyed out with “Requires the Enhanced Plan”. ## Walkthrough: order 8 weeks of launch stock 1. Open the launch plan and check that it is Draft, Confirmed or Locked. 2. Open Actions › Create purchase order. 3. Set Coverage window (days) to 56. 4. Keep One PO per location, or pick One combined PO and a Destination location. 5. On a plan with size groups, tick At least 1 per size if every size should be in stock at launch. 6. Check What will be created and click Create 2 draft POs (the button counts the POs it will create). A message confirms the POs; click Open POs to see them. 7. On each draft PO, set the supplier and send it. Tip Ordering doesn’t need the plan to feed the forecast. To let the forecast’s reorder suggestions take over after the launch order, keep Feed into forecast on and confirm the plan. See [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/). ## See also - [Order stock for a plan] (/guides/order-stock-for-a-plan/): what each plan type can order. - [Size groups] (/features/inventory-planning/size-groups/): how a size group’s order is shared out. - [Similar products & the launch curve] (/features/inventory-planning/new-product-planning/launch-curve/): the numbers the order is built from. - [Plan a product launch] (/guides/plan-a-product-launch/). Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/promotional-events/ # Promotional events Keep a yearly calendar of holidays and promotions, and let the forecast expect the extra sales around them. [Enhanced plan] (/reference/subscription-plans/) In Logistified, a [promotional event] (/reference/glossary/#promotional-event) is a holiday or a sale that comes back every year, such as Black Friday, Christmas, Diwali or your own summer sale. (A one-time sale works too.) You add it once with the uplift you expect, and once you switch it on, every forecast expects that much more demand on its dates, year after year. Your reorder dates and quantities follow. ## On this page - Where to find it - Find an event - Add an event from the holiday list - Create your own event - Set up the event - Date rules - The event page - Past and upcoming years - Switch an event on - Archive an event - Choose the uplift - Analyze past years - Measure one past occurrence - One uplift or one per product - Limits - Delete an event - See also ## Where to find it Open Inventory Planning and click the Promotional Events tile. The list shows every event, archived ones included, most recently changed first. The count under the title reads, for example, “(34 total)”, or “(3 of 34)” while a search or filter is active. The columns: - Event: the name, with its category. - Next occurrence: the next dates the event runs, or “-” when it has none. - Repeats: the date rule in words, for example Every year, 1 day after Thanksgiving (US), or Does not repeat for a one-time event. - Uplift: the uplift its next dates get, for example +40%. An event measured per product reads Per product variant, with the fallback a product without enough sales gets, for example fallback +20%. An event with no uplift set reads Not set. - In forecasts: On when the event’s Use in forecasts switch is on, so every forecast expects its extra demand; Off when it is off; Archived when the event is archived, which keeps it out of every forecast whatever its switch says. With no events yet, the list says “No promotional events yet” and offers Add event. A search or filter that matches nothing says “No events match these filters”, with Clear filters. Promotional events come with the Enhanced and Elevate plans. If your shop moves to a lower plan, the events stop changing your forecasts. You can still open and review them, but not add, edit or delete them: Add event is greyed out, and a banner says “Promotional Events is part of the Enhanced Plan and isn’t available on lower plans.” The forecast’s Amplifiers popover still lists the events, tagged Needs the Enhanced plan. Nothing is deleted, and the events lift your forecasts again once you upgrade. ## Find an event Search the list by name (“Search events by name…”), or filter it by Category (Holiday, Promotion, Sales event, Other; pick one or several). Once it’s enabled for your shop, you can also describe what you want with AI search, for example “holiday events”. Save a filter set as a preset to share it with everyone in your shop. The search and filters live in the page address, so they survive a reload in the Shopify admin. See [Search, filters & saved views] (/features/inventory-planning/search-and-filters/). ## Add an event from the holiday list Click Add event. The Add promotional event dialog opens on a list of popular shopping holidays from around the world: - Fixed dates, such as Valentine’s Day, Singles’ Day or Christmas. - A weekday of the month, such as US Thanksgiving, Black Friday, Cyber Monday, Mother’s Day or Memorial Day. - Around Easter, such as Easter itself, Carnival or Pentecost. - Lunar calendars and announced dates, such as Lunar New Year, Ramadan, Eid al-Fitr, Diwali, Holi, Hanukkah, the Super Bowl and El Buen Fin. - Dates you enter each year, such as Amazon Prime Day or Click Frenzy, whose dates are announced only shortly before. Search by name or by country code: black, eid or IN (which lists India’s festivals first). Each row shows the countries it is popular in (or Worldwide) and its next dates, or You enter the dates, Not announced yet, No upcoming date or No dates after 2031. Click a holiday (or highlight it with the arrow keys and press Enter) to go to the setup step. The event takes the holiday’s category and date rule. If the holiday overlaps an event you already have, for example Boxing Day and Christmas, the setup step says so, for example Overlaps Christmas Eve / Christmas Day (Dec 24 – 26, 2026). When both are switched on, their uplifts add up on the shared days. It compares with the events on the list you came from, so a filtered list can miss one. ## Create your own event If your holiday or sale isn’t in the list, click Create my own, next to the search. Enter a Name and a Category (it starts on Promotion), then choose how the event repeats. One event is one yearly series. A sale you run twice a year is two events. - Leave Repeats every year switched on for a yearly event, and pick a Date rule (see [Date rules] (#date-rules)). It starts on Same weekday as last year. - Switch it off for a one-time sale: it happens once, on the dates you pick. Same weekday as last year and a one-time event ask for the Start date and End date of one occurrence. Both start empty (“Pick a date”), and Next stays off until you pick them (“Pick the start and end dates to continue.”). Picking a start fills an empty end with the same day. The other rules ask for their own date (a month and day, a weekday of the month, …) and a Length (days) instead. If you entered dates first, switching to one of these rules carries them over: Same date every year, for example, takes the start’s month and day and the length of your dates. Click Next to set the event up. ## Set up the event Before the event is added, the setup step (Set up Black Friday, named after your event) asks for what matters most. Its subtitle repeats the date rule in words and, for a holiday from the list, the next dates at the length you set. - Name and Length (days), for a holiday from the list. Both start as the holiday’s own; rename it or make it longer (1 to 350 days), for example Black Friday weekend over 4 days. Holidays whose dates you enter each year take their length from those dates, so they have no length field, and the subtitle reminds you to enter each year’s dates on the event’s page (Actions › Add occurrence). Some holidays add a short note, for example how their length was chosen. - Uplift source (it starts on Fixed %), Measure it for and Uplift (%) or Fallback uplift (%): see [Choose the uplift] (#choose-the-uplift). - Notes, optional. - Use in forecasts, off by default: “Off: forecasts stay as they are until you switch it on from the event’s page.” Switch it on here and every forecast lifts demand on the event’s upcoming dates as soon as it is added. Click Add event: the event’s page opens. Use Back to the holiday list or Back to change your pick. Note Leave Use in forecasts off and your forecasts stay as they are until you switch the event on. An event stores only the dates you enter yourself; every other year, past or upcoming, is projected from its date rule, and past years are ready to measure. ## Date rules The date rule works out each year’s dates, so you never re-enter them: - Same weekday as last year: 52 weeks after the dates you enter, so the weekday stays the same. Good for Black Friday or a weekend sale. It counts from the nearest stored year and takes that year’s length. As 52 weeks are a day or two short of a year, every five or six years it lands a week before a holiday such as Black Friday: store that year’s real dates when that happens. - Same date every year: for Christmas, an anniversary or a fixed-date sale. - A weekday of the month: for example the 4th Thursday of November. Pick the 1st to 5th or the last one. A year without a 5th one has no date that year. - Around Easter: Easter Sunday or Orthodox Easter Sunday, moved to the day you need. - Relative to a holiday: follows another holiday from the list, for example 1 day after US Thanksgiving. - Published holiday dates: for lunar and announced holidays; follows the published dates. Years not announced yet are not projected. - Only the dates you enter: no rule; you add each year’s dates on the event yourself. Not every rule is offered everywhere. Create my own offers the first five. Published holiday dates comes with a holiday from the list that uses it. Only the dates you enter is offered in Edit, and Same weekday as last year only once the event has a stored date. Keep the current rule appears there only for a rule the form can’t show. Under Move the date, click Add a step to shift the date: Move by days (for example 3 days before, up to 366) or Move to a weekday (for example the 2nd Thursday after). A weekday step counts from the day after: the 2nd Thursday after Thursday Oct 1, 2026 is Oct 15. Steps apply in order, up to five, so a date of Oct 1 with one step is one rule that reads Every year, the 2nd Thursday after Oct 1. A rule with several steps reads in the same order, for example Every year: start on Jan 1, then 3 days before, then the 1st Friday after. Steps can move the date into another year, and the preview, the event page and your forecasts all follow them. Same weekday as last year takes no steps. Length (days) sets how long each occurrence lasts, from 1 to 350 days. Same weekday as last year takes its length from the dates you enter, so it has no length field. Preview · recent and upcoming dates shows the dates the rule gives for the last two and the next three occurrences, so you can check it before saving. Past ones are greyed and marked past. A year without a date says why, for example No 5th Monday in May 2027 or Super Bowl 2028: not announced yet. ## The event page Click an event to open it. Under its name, a line says who created it and when. The Details card has the Use in forecasts switch on its right and two lines of key facts: - Category. - Repeats: the rule in words, for example Every year, 1 day after Thanksgiving (US). - Length: shown when the rule sets each year’s length. Same weekday as last year, a one-time event and dates you enter yourself keep the length of their stored dates. - Next: the next dates, or None scheduled. - Uplift: the percent forecasts use now and where it comes from: fixed (you set it), measured (from your sales at a past year) or fallback (no past year measured yet). An event measured per product reads Per product variant. Not set or Not measured yet means nothing sets an uplift, so the event adds nothing. Below them, Uplift settings shows the uplift source, what applies, the fallback and what your past years measured. They are read-only on the page: change them, the name, the category and the date rule with Edit. The changes apply to every projected year, while dates you stored keep theirs. Notes sit at the bottom of the card. Click them to edit in place (up to 5,000 characters); they save when you click away or press Cmd+Enter or Ctrl+Enter. Press Escape to leave without saving. Occurrences lists the event’s dates over the last three and the next two years, newest first, with their Days, Uplift and Status. Its subtitle counts the dates you stored, for example 2 stored occurrences · Projected years follow the rule until you edit or skip them. Dates that are over are greyed. Status Meaning Projected Worked out from the date rule. Nothing is stored until you change it. Upcoming A date you stored that hasn’t happened yet. Past A date you stored that is over. Skipped A year you marked as not happening. Below the list, a line names each year the rule gives no date, for example Super Bowl 2028: not announced yet or No 5th Monday in May 2027. Next to Edit, Analyze past years estimates the uplift from your past sales (see [Analyze past years] (#analyze-past-years)). Under Actions you can Add occurrence to store a year’s dates yourself, for example the dates a past sale really ran (“A stored year replaces the one the rule would project.”), Archive an event (it stays on the list but is in no forecast, see [Archive an event] (#archive-an-event)) or Delete it for good. Stored dates of one event can’t overlap each other. ## Past and upcoming years A projected year applies to your forecasts as it is. Change it only when that year is different: - Edit this year stores the year with your dates; the rule keeps projecting the other years. Keep the dates within 60 days of the projected ones, or the rule projects that year again. - Skip this year marks the year as not happening. Restore brings it back. - On a projected year that is already over, the same actions read Edit and Didn’t happen. - On a stored Past or Upcoming year, Edit changes its dates and Delete removes them: “Removes the dates. If the rule covers that year, its projected dates come back.” Click Delete occurrence to confirm. - On every year that is over and happened, Analyze measures its uplift (see [Measure one past occurrence] (#measure-one-past-occurrence)). The next occurrence’s row offers Analyze past years. ## Switch an event on The Use in forecasts switch on the Details card is the event’s one on/off switch. A new event starts off, unless you switched it on in the setup step. When it is on, every forecast view lifts demand on the event’s upcoming dates, and so does everything that works from a forecast: reorder dates and quantities, orders you create from a forecast, and forecast-based notifications and reports. A toast confirms it, for example “Black Friday is now used in forecasts”. A view can still leave the event out: see [Promotional events in the forecast] (/features/forecast/growth-amplifiers/#promotional-events-in-the-forecast). Each forecast applies the event’s dates within the next two years, from tomorrow on. ## Archive an event Archive an event you don’t need now but may want back, for example a sale you’re pausing for a year. Open the event and choose Actions › Archive: “An archived event is in no forecast, whatever its switch says. You can restore it any time.” - The event stays on the list, marked Archived, and its page title carries an Archived tag. - Its Use in forecasts switch shows off and can’t be changed: “Archived events are never used in forecasts.” The switch’s own setting is kept. - Edit, Add occurrence, Analyze past years, the notes and the occurrence actions are locked until you restore it (“Restore the event from the archive to edit it”). Delete still works. To bring it back, choose Actions › Restore from archive and click Restore. The event comes back to the calendar, and its forecast switch keeps its last setting. ## Choose the uplift The uplift is how much higher demand runs on the event’s days, in percent: 40% means 1.4 times the normal forecast. Enter 0 to 1,000; an event can’t lower the forecast. Each event has one Uplift source, set in the setup step or in Edit: - Fixed %: you set the uplift, and every product’s demand rises by it. - From past years: the uplift is measured from your sales at this event in past years. Measure it for picks Your whole shop (one uplift for every product) or Each product variant (see [One uplift or one per product] (#one-uplift-or-one-per-product)). The percentage you enter becomes the Fallback uplift (%): it applies until a past year has enough sales to measure. With From past years for your whole shop, forecasts use the most recent past year that could be measured. Negative results are shown, but forecasts use 0% for them, as events only add demand. Forecasts also use at most +1,000%: a year that measured more shows its own result, and the dialog says that forecasts use at most +1,000%. The uplift is the event’s: the dates in Occurrences have none of their own. A date that still carries its own uplift from earlier shows it with (this date), and Use the event’s uplift clears it. ## Analyze past years Click Analyze past years in the page header, or on the next occurrence’s row: an upcoming event can’t be measured yet, but its past years can. (Before the event has run once, the button is locked: “There is no past Black Friday to analyze yet”.) The dialog compares what your whole shop sold per day at the event in each of the last 3 years with the days before it (the event’s comparison period, 56 days unless you changed it), matched by weekday. It lists each year by its dates (for example Sep 14, 2025), reading Not analyzed yet until you click Analyze. Then each year shows its result: - the measured uplift, for example +38%, and the range over the measured years, for example Measured: +22% to +38% (2 years); - Too few sales to measure, with the reason, for example No sales history before it when the shop had no orders yet, Only 3 days of sales history before it, or No sales in the 56 days before it. A year is measured when at least 7 days before it can be compared and something sold in them. Below the years, the dialog says what your forecasts use now, for example Forecasts use +38%, measured at Cyber Week 2025, the most recent year with enough sales. If no year could be measured, it says None of these years had enough sales to measure, so forecasts use your fallback of +20%. An event with a Fixed % keeps it; when a past year was measured, the dialog shows both values and offers Switch to From past years. If the next occurrence still has its own uplift from earlier, the dialog says so. Each result is saved on its year, and a year that was only projected is stored as a past occurrence. Click Run again after new orders came in. ## Measure one past occurrence On a past occurrence, click Analyze for a closer look at one year: - Compare with the 56 days before the event: change the number of days (7 to 365). Check Keep this period to save it as the event’s comparison period: Analyze past years and the per-product uplift then use it too. - Days are matched by weekday: a Friday in the event is compared with the Fridays before it. - Days inside other events are left out of the comparison, and so are days before your first order. The result says how many days were left out. - Click Run analysis. The result shows the uplift, for example +38% vs the 56 days before with the comparison dates, and the units sold per day during the event against the units expected from the comparison period. - A chart shows the units sold per day, the units expected on a normal day (same weekday) as a dashed line, the event as a shaded band, and the days left out of the comparison hatched. If fewer than 7 usable days remain, or nothing sold in the comparison period, the dialog says Not enough history: “No uplift is suggested, and nothing from this analysis is used in forecasts.” The result is saved on that year, so reopening the dialog shows it (“Last analyzed …”) with Run again; the chart appears after a run. Your other analyzed years are listed under Earlier analyses. With From past years for your whole shop, forecasts use the most recent year with enough sales, so analyzing an older year doesn’t replace a newer result. A result below 0% or above +1,000% gets a short note on what forecasts use from it. The analysis counts every order, including orders from your connected stores, but not test orders, orders your [order exclusion] (/features/settings/order-exclusion/) rules leave out, or products your [data exclusion] (/features/settings/data-exclusion/) rules leave out (for example a shipping protection add-on). It cannot see stock-outs: if you sold out during the event, the measured uplift is lower than the real demand. ## One uplift or one per product Not every product sells more during an event. With From past years, Measure it for decides: - Your whole shop: one uplift for every product, from your shop’s total sales. - Each product variant: each variant’s uplift is worked out from its own sales at the event’s most recent past occurrence, every time the forecast runs. Nothing is stored per product, so the list of products never needs updating. A variant’s own measurement counts in proportion to how much it normally sells in that period. A variant that sells only a few units leans mostly on the shop-wide uplift (or on the fallback until one is measured), so one lucky order does not set its uplift. A steady seller keeps nearly all of its own measured lift. Analyze past years still shows the shop-wide result, for reference. Products without sales history sets what happens to a product that had no sales before the last occurrence, such as a new product: - Use the shop-wide uplift: it leans on your shop’s uplift from past years, or the fallback. New products are included. - No uplift: it is not lifted until it has sales at a past occurrence. With this choice the event needs no percentage, so the field is hidden. The Uplift settings on the event page say what applies, for example Each variant’s uplift is worked out from its own sales at Black Friday 2025 when the forecast runs. Variants with few sales lean towards the shop-wide +38%. Before the event has run once, they say There is no past Black Friday to measure from yet. The forecast’s reorder date hover shows each product’s result, for example Black Friday: measured +233 % (4 vs 1.2 expected at Black Friday 2025), weight 29 % → +95 %: the measured lift (4 units sold against 1.2 expected), how much it counts, and the uplift used. A product that couldn’t be measured says why instead, for example no sales history before Black Friday 2025. ## Limits - Events apply to the whole shop: every product and every location. An event for one product or one store isn’t possible yet. - Uplifts only add demand. An event can’t lower the forecast, and it can’t block ordering, for example during a supplier’s holiday. - An event lasts at most 350 days, so one year never runs into the next. - Islamic holidays follow the Umm al-Qura calendar and can be a day off in your country. Holidays that begin at sunset are listed on their first full day. - Diwali, Dhanteras and Holi dates are included up to 2031. Diwali comes as two entries: Diwali (incl. Dhanteras), five days from Dhanteras, and Diwali (Lakshmi Puja day). - El Buen Fin is added with 5 days, the length of the 2025 and 2026 editions. Its length changes from year to year, so set Length (days) when you add it if an edition runs longer or shorter. Earlier years are projected with the same length, although the 2022 to 2024 editions ran 4 days: before you analyze them, correct their dates with Edit on their rows. Its dates are known up to 2026, and the Super Bowl’s up to 2027; later years read not announced yet until the dates are published. ## Delete an event Actions › Delete removes the event for good: “The event and its calendar disappear from every forecast and from this list. This cannot be undone.” Click Delete event to confirm; the list opens again. To keep the event but take it out of every forecast, [archive] (#archive-an-event) it instead. ## See also - [Set up promotional events] (/guides/set-up-promotional-events/): add Black Friday, measure its uplift and switch it on, step by step. - [Plans in the forecast] (/features/inventory-planning/plans-in-the-forecast/): how events and plans change your forecasts. - [Search, filters & saved views] (/features/inventory-planning/search-and-filters/): find events on the list. - [Growth amplifiers] (/features/forecast/growth-amplifiers/): how events show on the forecast page, and how to leave one out of a view. - [Reorder suggestions] (/features/forecast/reorder-suggestions/): where the extra demand lands. - [History period] (/features/forecast/history-period/): the window the forecast learns from. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/inventory-planning/settings/ # Inventory Planning settings Set up the demand types, reason codes and sources for your plans, their export templates, and how plans are numbered. Logistified’s Inventory Planning settings hold the lists you pick from when you categorise a plan, the templates for exporting plans, and the format of plan numbers. They apply to your whole shop. These settings are open on every subscription plan. New Product Planning and Promotional Events need the Enhanced plan, Inventory Commitments and Sales Plans the Elevate plan; see [Plan requirements] (/features/inventory-planning/overview/#plan-requirements). ## On this page - Where to find it - Demand types, reason codes and sources - Export templates - Plan numbers - What isn’t a setting - See also ## Where to find it Open Settings and, under Orders & Documents, click Inventory Planning. The page has four tabs: Demand Types, Reason Codes, Sources and Export templates. Plan numbers are set on a separate page, Settings › Document Numbering; see [Plan numbers] (#plan-numbers). ## Demand types, reason codes and sources These three lists give your plans consistent labels, so you can sort, filter and report on them later: - Demand Types: what kind of demand a plan is. - Reason Codes: why you expect it. - Sources: where it comes from. They appear as Demand type, Reason and Source on inventory commitments and sales plans. Launch plans don’t use them. The labels are for your records only and never change the forecast. A new shop starts with these values, all of which you can change or delete: List Starting values Demand Types Promotion, Seasonal, New Customer, Contract, Tender, Event, Other Reason Codes Marketing Campaign, Customer Forecast, Historical Trend, Sales Commitment, Other Sources Sales Team, Customer, Marketing, Management, Other On each tab you can: - Add a value with the Add button: give it a Name, a Color and an optional Description. - Edit a value with the pencil button (Edit option) on its row. - Delete a value with the bin button (Delete option) on its row, after confirming. Each name can be used once per list, whatever its capitals. Adding a duplicate shows, for example, “A demand type option named “Promotion” already exists”. Renaming or deleting never changes existing plans. A plan keeps the name it was given. A deleted value just no longer appears when you pick one. You don’t have to come here to add a value. In a plan’s Demand type, Reason or Source field, type a new name and choose Create demand type “…” (or Create reason “…”, Create source “…”). It’s added to the list here too. ### Add a demand type 1. Open Settings › Inventory Planning. The Demand Types tab is open. 2. Click Add. The “Add Demand Type” dialog opens. 3. Enter a Name, for example Wholesale order, pick a Color, and add a Description if it helps your team. 4. Click Add. Logistified confirms with “Option added”, and the new type is in the list, ready to pick on any commitment or sales plan. ## Export templates The Export templates tab decides what your plan exports look like. The same templates are used by all three plan types. There are three kinds: - PDF: the layout of a plan’s PDF. Options include Show barcode column and Show unit price. - Inventory Plan XLSX/CSV: one row per product in the plan. Choose the columns and their order. - Inventory Plan Level XLSX/CSV: one row per plan, for exporting a whole list of plans. Click New template in a section to create one. Tick Set as default in the template to make it the one used when you don’t pick another, for example by Quick PDF export on a plan page. How exporting works is described in [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/). ## Plan numbers Every plan gets a number when you create it. Out of the box, plans are numbered by type: - Inventory commitments: IC-00001, IC-00002, … - Sales plans: SP-00001, … - New product plans: NP-00001, … You can switch to your own format instead. Open Settings › Document Numbering and find the Inventory planning section, with one card for Inventory commitments, Sales plans and New product plans each. - The format comes pre-filled with the plan type’s prefix (IC-, SP- or NP-) and six digits, one more than the built-in numbers above. Change the Prefix (optional), Year, Digits, Separator and Suffix as you like. Next number previews the result. - Under Starting number, choose Continue from existing to carry on from the plans you already have, or Start at 1. - Click Activate numbering. From now on, new plans of that type use your format. Existing plans keep their numbers. Until you activate a custom format for a plan type, its list shows a Custom document numbers note at the top with a Configure in Settings link. Note Plan numbers are unique across all three plan types, so two plans never share a number, even with your own format. ## What isn’t a setting Most planning choices belong to a single plan, not to the shop, so they’re made on the plan itself: - Launch plans: the similar products, volume, launch date, horizon, Feed into forecast and Stop feeding on first real sale. See [New Product Planning] (/features/inventory-planning/new-product-planning/overview/). - Sales plans: the plan window, locations and growth. See [Sales Plans] (/features/inventory-planning/sales-plans/overview/). - Size groups: the sizes and their split. See [Size groups] (/features/inventory-planning/size-groups/). - Promotional events: each event’s dates and uplift. See [Promotional events] (/features/inventory-planning/promotional-events/). ## See also - [Creating a commitment] (/features/inventory-planning/commitments/creating/): where demand type, reason and source are used. - [Exports, documents & activity] (/features/inventory-planning/exports-and-documents/): exporting plans with your templates. - [Settings overview] (/features/settings/overview/): all other settings. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/overview/ # Suppliers The supplier directory: who you buy from, what you buy, and how reliably they deliver. Suppliers are the external parties you buy stock from. Each supplier carries contact details, default payment terms, currency, tax rate, and a list of the variants you buy from them. Logistified uses supplier data in three places: the Forecast page uses the primary supplier’s numbers to compute reorder suggestions (and uses a specific supplier’s numbers when you filter the forecast by that supplier), Purchase Orders inherit supplier defaults, and Return Orders return goods to specific suppliers. A supplier is not the same as a Shopify vendor. Shopify “vendor” is a text field on a product; a Logistified supplier is a richer record. You can auto-create suppliers from Shopify vendors; see [Vendor & collection groups] (/features/suppliers/vendor-and-collection-groups/). ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Supplier directory] (/features/suppliers/directory/) The supplier list, the Default supplier, and performance buckets. [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/) The numbers that drive reorder math, per supplier–variant link. [Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/) Linking variants to suppliers; primary supplier selection. [Vendor & collection groups] (/features/suppliers/vendor-and-collection-groups/) Auto-create suppliers from Shopify vendor names or collections. [Supplier credits] (/features/suppliers/credits/) Balances owed to you: minting, applying, voiding. Canonical home. [Importing suppliers] (/features/suppliers/importing/) Bulk-create from Stocky exports or CSV/XLSX. [Exporting suppliers] (/features/suppliers/exports/) Bulk CSV/XLSX export from the list, supplier level or supplier items. [Accounting contacts] (/features/suppliers/accounting-contacts/) Link suppliers to Xero contacts so bills sync to the right place. ## Key concepts - [Default supplier] (/reference/glossary/#default-supplier): the built-in sentinel attached to every variant by default. - [Primary supplier] (/reference/glossary/#primary-supplier): the one whose lead time, MOQ, pack size, and cost feed the reorder math. - [Supplier–variant link] (/reference/glossary/#supplier-variant-link): the relationship between one supplier and one variant. - [Vendor group] (/reference/glossary/#vendor-group) / [Collection group] (/reference/glossary/#collection-group): auto-creation from Shopify. - [Supplier credit] (/reference/glossary/#supplier-credit): a balance owed to you. ## Where to next - [Guides → Connect suppliers to variants] (/guides/connect-suppliers-to-variants/): getting started. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): how supplier data feeds the math. Last updated: 4 September 2026 --- Source: https://docs.logistified.app/features/suppliers/directory/ # Supplier directory The supplier list, the Default supplier, and performance buckets. Logistified’s Suppliers list is the directory of every supplier you’ve configured. This page covers what’s on the list, the special “Default supplier” entry, the supplier detail page, and what happens when you delete a supplier. ## On this page - The supplier list - Bulk actions - The Performance column - The Default supplier - Supplier number format - Supplier detail page - Default email recipients - Default values for new suppliers - Deleting a supplier - See also ## The supplier list Each row shows: - Checkbox: select one or more suppliers to reveal the bulk Actions menu (see below). - Supplier: name plus the auto-generated supplier number underneath. - Contact: primary contact person, email, phone. - Location: city, state/province, and country, with the postal code on a second line. - Performance: the supplier’s on-time-delivery rate as a percentage, with a one-word reliability label underneath (see below). - Variants: how many variants you buy from this supplier. - Actions: edit and delete. The search box above the list matches far more than the name: supplier name and supplier number, contact person, email, phone, website, city, state/province and country, and the supplier SKU, supplier product name, product URL, and variant notes on any of that supplier’s variant links, plus the product title, variant title, and SKU of the Shopify products and variants linked to that supplier. Next to it, filters narrow by location, performance bucket, and variant-count bucket (No Variants, Low (1-5), Medium (6-20), High (21+), plus the shortcuts 100+, 250+, 500+, and 1000+). The location filter’s options come from your suppliers’ cities, states/provinces, and countries. ## Bulk actions Checking one or more rows reveals an Actions menu in the search-and-filter toolbar above the table. The same toolbar row also shows how many suppliers are selected and, when the entire visible page is ticked and more results exist on other pages, a Select all N matching link that expands the selection to every supplier matching your current filters. When an accounting integration is connected, the menu carries a fourth action, Match to [provider]; see [Accounting contacts] (/features/suppliers/accounting-contacts/). ### Sync Shopify cost → supplier cost This action updates the cost on each selected supplier’s variants to match Shopify’s current unit cost for those variants. It also carries the updated cost through to any draft purchase-order line items linked to those variants. How the sync runs: 1. Click the checkboxes next to the suppliers you want to update (or use Select all N matching). 2. Open Actions → Sync Shopify cost → supplier cost. 3. If any selected suppliers use a currency other than your shop currency, a currency step appears first. For each foreign currency you choose one of: - Convert with exchange rate: multiplies Shopify’s cost by the exchange rate you enter. Logistified pre-fills a live rate automatically; you can override it. - Sync regardless (copy number): copies Shopify’s numeric cost as-is, without conversion. - Exclude these suppliers: skips all suppliers that use this currency. 4. Click Continue to start the sync. (If every selected supplier already uses your shop currency, there is no currency step and no Continue; the sync starts the moment the dialog opens.) A progress bar tracks each stage. The dialog cannot be closed while the sync is running. 5. When finished, a summary shows how many costs were updated, how many were skipped (for example, because Shopify had no cost recorded for a variant), and any errors. The supplier list refreshes automatically. Note Only draft purchase-order line items are updated alongside the supplier cost. Issued, received, or closed POs are not touched. ### Update connections This action re-runs each selected supplier’s vendor and collection connections in one pass, the same refresh you’d trigger one at a time from Manage connections on the supplier detail page, run in bulk from the list. How the update runs: 1. Click the checkboxes next to the suppliers you want to update (or use Select all N matching). 2. Open Actions → Update connections. The dialog shows the selected suppliers and waits for you to confirm; nothing changes until you click Update connections. 3. Optionally turn on Set as primary supplier before starting: every variant the update adds then gets that supplier as its primary supplier (any previous primary supplier for the variant is demoted). Variants already connected to the supplier are left as they are. 4. Logistified processes suppliers one at a time. For each supplier, newly matching variants are added and variants that no longer match are removed, except any variant that’s on a purchase order, which is kept either way. Suppliers with collection connections get the more thorough check, which also removes any variant that was manually added outside every connection. 5. A progress row per supplier shows what’s happening, with added/removed counts once it finishes, or No connections for suppliers that have no vendor or collection connections set up. A failed supplier doesn’t stop the run; it’s marked and the rest continue. 6. When finished, a summary reports the totals added/removed across all suppliers, plus how many had no connections or failed. The supplier list refreshes automatically. Note Suppliers without any vendor or collection connections are skipped and reported as “No connections”; there’s nothing to refresh. ### Export suppliers Downloads the selected suppliers, or their items, as a CSV/XLSX file; see [Exporting suppliers] (/features/suppliers/exports/) for the full walkthrough of export types and templates. ## The Performance column The Performance column shows the rate as a percentage with a reliability label underneath. Hover the cell for a one-line explanation. Label Threshold Excellent 95% or higher Good 90% up to 95% Review Below 90% No data Rate not set (a rate of 0 also reads as “No data”) The Performance filter above the list offers Excellent (≥95%), Good (90-94%), Needs Improvement (<90%), and No Data. The first three line up with the column’s bands, but No Data does not: it matches only suppliers with no rate stored at all, so a supplier whose rate is exactly 0 reads as “No data” in the column while the filter returns it under Needs Improvement (<90%). The rate is not computed automatically. You set it manually on the supplier (Edit supplier → On-time delivery rate). Treat it as an informational label for your own bookkeeping; it has no functional effect on reorder suggestions, PO creation, or notifications unless you explicitly opt in via the forecast’s supplier-reliability setting. ## The Default supplier When Logistified is installed, it creates one special supplier called [Default supplier] (/reference/glossary/#default-supplier). It: - Exists for every shop. - Is attached to every variant by default. - Carries fallback lead time, MOQ, and pack size on every link it creates: the values you entered during onboarding, or 40 days / MOQ 0 / pack size 1 if you left them blank. - Cannot be deleted. - Appears in lists but is often filtered out of pickers; most operators don’t actually buy from “default.” When you set up real suppliers, replace the Default on the variants you buy from those real suppliers. ## Supplier number format When you create a supplier by hand, Logistified generates a number in the form SUP- followed by up to four characters taken from the supplier’s name and a 6-digit timestamp suffix, for example, SUP-ACME078293. Suppliers generated from a Shopify vendor or collection, or from an accounting contact, get a shorter timestamp-only form (SUP-MJ4K8XYZ), and Stocky imports get SUP-STKY-…. The number is shown on the supplier detail page and under the name in the list; click it to copy. There is no field for editing it. ## Supplier detail page Click any supplier in the list to open the detail page. It has three tabs, in this order: - Variants (opens by default): every supplier–variant link with this supplier. The table has its own sub-views: Variants, Price breaks, My stock at supplier, and Supplier offers. The last three are plan-gated: Price breaks and Supplier offers need the Enhanced plan; My stock at supplier needs Elevate. On a lower plan the sub-view still opens and the data is still visible; what changes is that an upgrade notice appears above the table and the add/edit actions (bulk and per-row) are hidden. - Credits: credit balance + application history. Needs the Elevate plan: on a lower plan the tab still opens, but the table is dimmed behind an upgrade notice and the credit actions are hidden. - Overview: a Purchase order address defaults card (below), then basic information (supplier ID, tax ID, currency, notes), contact and address (including the default email recipients), business terms (minimum order, credit limit, payment terms, discount terms, purchase tax rate), and a created / last-updated timeline. ### Purchase order address defaults The card at the top of the Overview tab picks the addresses new purchase orders from this supplier start with. Two pickers: - Company / billing profile: the company or billing address printed on the order. - Delivery profile: the delivery address printed on the order. Both are optional; leave either on its “none” option to keep the behaviour you had before. The choices are saved the moment you pick them. Profiles themselves (creating, naming, and archiving them) live at Settings → Purchase Orders → Address profiles; see [Purchase order settings → Address profiles] (/features/supply-orders/purchase-orders/settings/#address-profiles). Assigning one here only changes what a new order starts with; purchase orders you’ve already created keep their own addresses. Note A delivery profile changes the printed address only. The order’s receiving location is unaffected, and orders delivering to a customer or to another supplier keep their own destination addresses. The Default supplier has no such card. Older links that used ?tab=supply, ?tab=terms, or ?tab=activity still work; those tabs were folded into Variants and Overview, and the links redirect there. ## Default email recipients Each supplier can carry two lists of email addresses, separate from the single Email field: - Default email recipients (To): pre-fills the To field when you email this supplier a purchase order or a return. If left empty, the Email field is used instead. - Default CC recipients: always copied in when you email this supplier, on top of any CC addresses the email template itself adds. Set these in the Create supplier or Edit supplier dialog: type an address and click + (or press Enter) to add it as a chip, and click the × on a chip to remove it. Both lists accept any number of addresses. Once set, they show up on the supplier detail page’s Overview tab, and when you open the send-email dialog for a purchase order or a return involving this supplier, they seed the To and CC fields automatically; you can still add, remove, or replace addresses before sending. Transfer-order emails go to the destination location rather than a supplier, so they ignore these lists. On a resend, the addresses used for the previous send win over the supplier defaults. Note The Email field is untouched by this; it keeps feeding PDFs, exports, and search, and still acts as the fallback when no default To recipients are set. If it holds more than one address (comma- or semicolon-separated, common after an import from another system), Logistified treats it as a list everywhere it’s used to send mail: each address gets its own chip in the send-email dialog and its own link on the Supplier & Location card. Opening Edit supplier keeps the first address in the Email field and adds any others as default To recipients the next time you save. ## Default values for new suppliers When you create a new supplier, these defaults apply: Field Default Currency Your shop currency Payment terms “No Payment Terms” (note: different from PO default which is “NET 30”) Tax rate Your default purchase tax rate, if one is marked as default under Settings → Tax Rates; otherwise none Discount terms None Credit limit (display-only: Logistified doesn’t enforce it against POs) Minimum order value 0 Edit on the supplier detail page. A supplier also carries its own Ordering Defaults: Default MOQ, Default Pack Size, Default Lead Time (days), and (for suppliers whose minimums apply per product) Default Product MOQ. These are the numbers every new supplier–variant link for this supplier starts from, however the link is created. They start empty, and changing one later asks whether to apply it to the supplier’s existing items as well. See [Lead times & MOQ → Defaults for new links] (/features/suppliers/lead-times-and-moq/#defaults-for-new-links). ## Deleting a supplier Suppliers are archived, not hard-deleted. The system: - Marks the supplier as archived. - Promotes the Default supplier to primary for every variant that had this supplier as primary, provided the Default supplier already has a row for that variant. After delete, the supplier disappears from every list and picker, but its data (variant links, purchase orders, credits) is preserved in the database. There is no in-app archived view and no restore button, so delete with care. Note The Default supplier exists so reorder math doesn’t choke on variants without a real supplier. Replacing it on a variant is the same as assigning a real supplier, with no special steps needed. ## See also - [Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/): assigning variants to suppliers. - [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/): per-link numbers that feed reorder math. - [Exporting suppliers] (/features/suppliers/exports/): the Export suppliers action in detail. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/lead-times-and-moq/ # Lead times & MOQ The per-supplier-variant numbers that drive reorder math: lead time, MOQ, and pack size. Three numbers from the supplier–variant link drive the reorder math of Logistified’s forecast: [lead time] (/reference/glossary/#lead-time), [MOQ] (/reference/glossary/#moq), and [pack size] (/reference/glossary/#pack-size). This page is the reference for what they mean, where they live, and how to set them. ## On this page - What they are - Where they’re stored - How the forecast uses them - Defaults for new links - Setting them - MOQ applies to: each variant or the whole product - Release lead time (a separate, supplier-level field) - See also ## What they are - Lead time: how many days the supplier needs from order to delivery. - MOQ: minimum order quantity. The smallest order this supplier accepts. - Pack size: the packaging increment (12 to a case, 24 to a carton). Orders are rounded up to the nearest multiple. ## Where they’re stored On the [supplier–variant link] (/reference/glossary/#supplier-variant-link): one set of values per (supplier, variant) pair. Different suppliers for the same variant can have different lead times and MOQs. ## How the forecast uses them By default the forecast uses the primary supplier’s numbers; change the primary on the variant to feed different values into reorder math. There is one important exception: when you filter the forecast view by a specific supplier, the reorder math switches to that supplier’s lead time, MOQ, and pack size instead of the primary’s. This is what lets you compare “what would my reorder look like if I sourced this from supplier B?” without flipping the primary. These three numbers flow into specific reorder columns: - Lead time → Reorder Point, Reorder Date. - MOQ → Reorder Forecast (rounded up to MOQ when raw demand is lower). - Pack size → Reorder Forecast (rounded up to the nearest multiple). ## Defaults for new links Each supplier carries its own Ordering Defaults, the numbers every new link to that supplier starts from. Set them in the Create supplier or Edit supplier dialog, under the Ordering Defaults heading: Field What it seeds Default MOQ The MOQ on every new supplier–variant link. Default Pack Size The pack size on every new link. Default Lead Time (days) The lead time on every new link. Default Product MOQ The minimum for a product that doesn’t have one of its own. Only shown when this supplier’s minimums apply per product (see below); its helper text reads “Proposed for products without a product MOQ.” Leave a field empty and it reads Not set; Logistified then falls back to its own built-in numbers (below). Every way of creating a link reads these defaults: Add variants on the supplier detail page, vendor and collection connections including the nightly refresh, the supplier–variant spreadsheet import, the Add Items to Supplier dialog on a purchase or return order, and the forecast’s Add to supplier action. A value that arrives with the link (a MOQ column in your file, a number you typed in a dialog) always wins over the default. The Stocky import’s Review suppliers step has its own per-supplier MOQ, Pack size and Lead time (days) fields. Whatever you set there is saved as that supplier’s Ordering Defaults, so the numbers you reviewed at import time keep applying to links you add later. ### When a default is empty Field Falls back to MOQ 0, except on a spreadsheet import, where it’s 1 Pack size 1 Lead time 40 days, except on a spreadsheet import, where it’s 7 days When a variant has no real supplier (only the [Default supplier] (/reference/glossary/#default-supplier)), that supplier’s own fallbacks apply instead. Best to assign a real supplier early. ### Changing a default later Changing a default to a new number on a supplier that already has items asks Apply the new defaults to all items?; it names each field and its old → new value, then offers: - Apply to all N items: overwrite that field on every item already linked to this supplier. A changed Default Product MOQ is applied to every one of the supplier’s products instead. - Only future items: leave existing items alone; the new number only seeds links added from now on. Lines on purchase orders you’ve already created keep their values either way. Clearing a default back to empty never prompts; there’s no value to apply. ## Setting them Suppliers → Supplier detail → Variants tab → click into a row → edit inline. For bulk updates, see [Importing suppliers] (/features/suppliers/importing/); the round-trip spreadsheet carries a MOQ column for the per-variant number and a Product MOQ column for the whole-product minimum. Note When you change a lead time, the forecast picks it up on the next refresh, usually within a minute. Reorder suggestions update accordingly. ## MOQ applies to: each variant or the whole product Some suppliers quote one minimum per style across every size or color, not one minimum per variant; a six-size shoe with a 50-unit minimum means 50 units total, split however you like across sizes, not 50 of each size. Logistified can apply MOQ either way, per supplier. Set it on the supplier itself: Suppliers → Create/Edit supplier → Ordering Defaults → Minimum order quantities apply: - Per variant (the default): the MOQ on every supplier–variant link is its own minimum, as described above. - Per product: one minimum per product. The forecast recommends a single total for the product and splits it across the sizes that sell; a purchase order checks the product’s combined ordered quantity against that one minimum instead of checking each line separately. Variant MOQs are kept but don’t apply. - Both: the product minimum on top of the per-variant minimums: every size still meets its own MOQ, and the product’s combined quantity meets the product minimum. A line under the picker spells out which number binds where under the option you’ve chosen, and picking Per product or Both also reveals the Default Product MOQ field described in [Defaults for new links] (#defaults-for-new-links). Switching from per-variant to per-product When you switch a supplier from Per variant to Per product, the per-variant minimums stop applying; only the product minimum counts from then on. A size whose suggested quantity was only lifted by its variant minimum can therefore show a lower quantity than before. Choose Both if you want the product minimum on top of the existing per-variant minimums. Switching an existing supplier to Per product doesn’t lose any MOQs you’ve already entered: for each product, the highest MOQ among its variants becomes the product’s minimum. You don’t need to re-enter or re-import anything. Switching back the other way is announced too; the dialog tells you how many variants carry a stored variant MOQ that becomes active again. Note See [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/#product-level-moq) for how the forecast shows and splits a product minimum, and [Purchase Orders → Line items & costs] (/features/supply-orders/purchase-orders/line-items/#constraint-badges) for how it’s checked on a PO. ## Release lead time (a separate, supplier-level field) Release lead time is a different number from the lead time above: it’s how long stock takes to travel from the supplier to a warehouse once released, and it lives once per supplier, not per supplier–variant link. It’s used only when a forecast view has Include supplier-held stock set to “After release lead time”; see [Supplier-held stock] (/features/forecast/supplier-held-stock/) for what that setting does. Set it on the supplier itself: Suppliers → Create/Edit supplier → Supplier-Held Stock → Release lead time (days). Leave it blank to fall back through the item’s own transit and lead-time settings, then the supplier’s default lead time. Because it isn’t an ordering default, changing it never triggers the [“apply to all items” prompt] (#changing-a-default-later). ## See also - [Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/): primary supplier selection. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): where the numbers land. - [Forecast → Supplier-held stock] (/features/forecast/supplier-held-stock/): what release lead time feeds into. - [Purchase Orders → Line items & costs] (/features/supply-orders/purchase-orders/line-items/#constraint-badges): how product-level MOQ is checked on a PO. - [Importing suppliers] (/features/suppliers/importing/): bulk updates. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/performance/ # Supplier performance How Logistified measures supplier reliability and what the performance buckets mean. Logistified tracks how reliably each supplier delivers, then groups them into [performance buckets] (/reference/glossary/#performance-bucket) so you can spot patterns at a glance. Today the metric is one number: on-time delivery rate. ## On this page - What performance means - How it’s calculated - Performance buckets - How the forecast uses it - Manual override - See also ## What performance means The percentage of past POs from a supplier that arrived by the expected delivery date. Higher is better. Lower means you need more safety stock to compensate. ## How it’s calculated For each closed PO from a supplier, Logistified compares the actual received date to the expected delivery date. The on-time rate is the fraction of POs that arrived on or before expected. Computed continuously: every closed PO contributes one data point. ## Performance buckets The supplier list displays the rate as a bucket: Bucket Threshold Excellent 95% or higher Good 90–94.99% Needs improvement Less than 90% No data Not enough completed POs to score ## How the forecast uses it The reorder math can optionally factor in [supplier reliability] (/reference/glossary/#supplier-reliability) when computing safety stock; a less-reliable supplier means a thicker cushion. Toggle in the forecast settings panel. When the toggle is off, safety stock is based purely on demand variability. ## Manual override You can manually set a supplier’s on-time delivery rate (rare, usually you let Logistified compute it). Useful for new suppliers where the computed value isn’t yet meaningful, or when you have data from before Logistified started watching. Note The performance bucket reflects history. Don’t expect it to change instantly when you receive a late shipment; it’ll move over time as more POs close. ## See also - [Supplier directory] (/features/suppliers/directory/): where the bucket is displayed. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): how reliability feeds safety stock. Last updated: 19 May 2026 --- Source: https://docs.logistified.app/features/suppliers/supplier-variant-mapping/ # Supplier–variant mapping Linking suppliers to variants, choosing primary, and handling cascades. In Logistified, a [supplier–variant link] (/reference/glossary/#supplier-variant-link) is a row that says “I buy variant X from supplier Y at price Z, with these terms (MOQ, pack size, lead time, supplier-side SKU).” A variant can have many links (many suppliers can sell the same SKU). One link per variant is marked primary; its values drive reorder math. ## On this page - What a link is - Adding variants to a supplier - Adding an order’s items to its supplier - Primary supplier - Changing primary - Cascading variant edits to draft POs - Removing a link - See also ## What a link is One row per (supplier, variant) pair. The link is where you record everything that’s specific to how this supplier sells this variant to you, including the things that differ from what’s in Shopify. A link carries: - Supplier SKU: the SKU your supplier uses (often different from your Shopify SKU). - Supplier product name: what the supplier calls the product on their invoices and catalogues. - Supplier product URL: a link back to the product on the supplier’s site or portal. - Supplier variant details / notes: free-text notes about this variant from the supplier (colour, finish, packaging quirks, etc.). - Barcode: supplier-side barcode if it differs from the Shopify one. - Cost + currency: your unit cost from this supplier. - MOQ: minimum order quantity for this variant. A separate Product MOQ can apply once per product instead; see [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product). - Max order quantity: optional ceiling. - Pack size: packaging increment. - Lead time: days from order to delivery. - Primary flag: exactly one link per variant is the primary. A variant can have one Default supplier link plus many real supplier links. Common cases: backup suppliers, multi-region sourcing, comparing quotes. ## Adding variants to a supplier On the supplier detail page’s Variants tab, the Add variants button opens a menu with two sources: - Shopify variants: pick from your store’s product catalogue. - Virtual materials: raw inputs tracked by the Assemblified app (fabric rolls, packaging components, and similar) that aren’t standalone Shopify variants, but can still be linked to a supplier here. The option is always in the menu; if Assemblified isn’t feeding materials into your shop, the picker simply opens empty (“No virtual materials found”). The same picker lists Assemblified sub-assemblies after the virtual materials. A sub-assembly is never linked to a supplier automatically: link it here before you purchase it, or purchase-order generation for this supplier names it as unmapped. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#purchasing-sub-assemblies). The menu is available whether the supplier already has variants linked or none yet. With no variants, the empty state shows the same Add variants menu next to an Import variants button; with variants, it sits in the table toolbar above all of the tab’s sub-views. New links are pre-filled from what you picked (supplier SKU from the variant’s SKU, cost from the variant’s Shopify unit cost, currency from the supplier) and always start as Secondary. The cost is copied as a plain number with no currency conversion, so check it when the supplier bills you in a different currency than your shop. MOQ, pack size, and lead time come from the supplier’s own [Ordering Defaults] (/features/suppliers/lead-times-and-moq/#defaults-for-new-links); if the supplier has none set, links added this way start at MOQ 0, pack size 1, and a 40-day lead time until you edit them. To make the new link drive reorder math, promote it afterwards (see [Changing primary] (#changing-primary)). ## Adding an order’s items to its supplier This is a different flow from Add variants above: it starts from an order that already has the items on it, and hands them to the order’s supplier without you retyping the terms you negotiated. A purchase order whose lines aren’t all mapped to its supplier shows task badges above the line-item table: N not from supplier and N unavailable at location. Clicking one opens the Add Items to Supplier dialog. Return orders have the same dialog. Each item gets its own card, pre-filled from the order line rather than reset to blanks: - Supplier SKU: the line’s supplier SKU, or its Shopify SKU when there isn’t one. - Unit Cost: the line’s cost. - MOQ and Pack Size: from the line (purchase orders only), falling back to the supplier’s Ordering Defaults. Above the cards, one Lead Time (days) field applies to every item at once; leave it empty and each link takes the supplier’s default lead time. Each card also has a Show more toggle that reveals three optional fields: - Supplier Barcode: the supplier’s own barcode for this variant, when it differs from the Shopify one. - Supplier Product URL: a link to the item on the supplier’s site or portal. - Supplier Variant Details: free-text notes the supplier uses to identify this variant. Add to Supplier creates the supplier–variant links and writes the values you confirmed back onto the order’s lines, so the order and the new links agree. Clearing the barcode field clears the line’s barcode override too. Note The forecast’s bulk Add to supplier action works the same way, and gains an optional Supplier barcode field when exactly one variant is selected; with several variants there’s no single barcode to apply, so the field is hidden. ## Primary supplier One link per variant is the [primary supplier] (/reference/glossary/#primary-supplier). Reorder math uses the primary’s numbers. Only one primary at a time. ## Changing primary Three ways, all on the supplier detail page’s Variants tab: - Row edit panel: each row shows Primary or Secondary in the Status column (a label, not a button). To change it, open the row’s edit side panel and turn on the Use as primary supplier toggle. - Bulk edit: select several rows and set Primary supplier status in the bulk edit panel. - Import: the supplier–variant import accepts an Is Primary Supplier column, so a file can promote (or demote) many links in one go. The confirm screen warns you when the file will reassign primaries. On the Default supplier’s own page the toggle can’t be switched off; Logistified refuses to demote a Default link from there, so you can’t leave a variant without a primary by accident. It can still lose the flag indirectly: promoting a real supplier for that variant clears the Default link’s primary flag, exactly like any other hand-off. When you set a new primary, the previous primary’s flag is unset automatically. No double primaries. ## Cascading variant edits to draft POs When you bulk-edit variants in supplier mode (e.g., via the supplier detail page’s Variants tab), the changes update Draft POs only. POs in Sent / Confirmed / further statuses are frozen; to apply the new values there, you’d edit the PO manually. ## Removing a link Removing a supplier–variant link severs the connection. The variant isn’t removed, just disconnected from that supplier. If the link was primary, Logistified tries to promote the Default supplier link as the new primary (provided the Default has a link for that variant). Note Many variants have many suppliers. The mapping tells Logistified which supplier’s terms drive your reorder math; the other links sit there for context, backup, or future sourcing decisions. Caution Bulk variant edits don’t cascade to sent POs. Review affected POs manually before assuming the changes propagated. ## See also - [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/): the per-link numbers. - [Supplier directory] (/features/suppliers/directory/): the supplier-side overview. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): where the primary supplier feeds in. - [Importing suppliers] (/features/suppliers/importing/#the-product-moq-column): setting MOQ and Product MOQ in bulk from a spreadsheet. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/vendor-and-collection-groups/ # Vendor & collection groups Auto-create suppliers from Shopify vendor names or collections. If your Shopify vendor list (or collection list) maps cleanly to your real suppliers, you can have Logistified auto-create the supplier–variant links for you. Two flavours: [vendor groups] (/reference/glossary/#vendor-group) and [collection groups] (/reference/glossary/#collection-group). They’re managed per supplier, not in Settings; each real supplier you’ve created can be wired up to one or many Shopify vendors and to one or many Shopify collections at the same time. ## On this page - Where it lives - Seeding a supplier from vendors - Seeding a supplier from collections - Mixing vendors and collections on one supplier - What gets imported (and what doesn’t) - Automatic nightly resync - Manual trigger - See also ## Where it lives Open the supplier you want to seed. In the header, click Manage Connections: - Vendor Connections opens a dialog where you pick one or many Shopify vendor names to attach to this supplier and click Refresh to pull in all matching variants. - Collection Connections does the same for Shopify collections. There is no “Vendor groups” page under Settings; everything happens from the supplier itself. ## Seeding a supplier from vendors For each Shopify vendor name you’ve attached to the supplier, Logistified: 1. Dedupes vendor names case-insensitively (so “Acme” and “ACME” are treated as the same vendor; match this to your Shopify vendor list first). 2. Fetches every variant whose product belongs to that vendor. 3. Creates supplier–variant links in bulk, using that supplier’s own [Ordering Defaults] (/features/suppliers/lead-times-and-moq/#defaults-for-new-links) for lead time, MOQ and pack size, or Logistified’s built-in fallbacks where the supplier hasn’t set one. 4. Marks each new link as primary if the variant doesn’t already have a primary supplier. ## Seeding a supplier from collections Same idea, but the source is a Shopify collection. Useful when “all products in the Imported Wines collection come from supplier Y.” ## Mixing vendors and collections on one supplier One supplier can carry both kinds of connections, and as many of each as you need. For example, a supplier “Acme Inc” might be connected to: - Vendor names: Acme, Acme US, Acme EU - Collections: Acme house brand, Acme exclusives When you click Refresh, Logistified walks all vendor and collection connections on that supplier and merges the resulting variant set into supplier–variant links, without duplicating links that already exist. ## What gets imported (and what doesn’t) The refresh respects your Data exclusion settings. Products that are archived, drafted, or matched by your exclusion rules (tag, type, vendor, etc.) are filtered out; their variants are not added to the supplier. If you want excluded products to be sourced from a supplier anyway, loosen the exclusion rule first, then refresh. ## Automatic nightly resync Vendor connections re-sync automatically every night; you no longer have to press Resync when your Shopify catalog changes. For every vendor name attached to a supplier, the nightly run applies the same diff as the manual button: - Variants of matching products that aren’t linked yet are added, never as the primary supplier, and only if they pass your [Data exclusion] (/features/inventory/data-exclusion/) settings. - Linked variants whose product no longer belongs to that vendor are removed, unless they appear on the supplier’s purchase orders, in which case they’re retained. - Variants you added manually from other vendors are never touched. Collection connections are not auto-resynced yet; refresh those manually when your collections change. ## Manual trigger You can still resync on demand, useful right after renaming vendors in Shopify instead of waiting for the nightly run. Each vendor connection in the Vendor Connections dialog has its own Resync button, and Refresh re-pulls all of a supplier’s vendor and collection connections at once. The operation is idempotent; running it twice doesn’t duplicate links. To refresh several suppliers at once instead of opening each one, select them on the [supplier list] (/features/suppliers/directory/#update-connections) and use Actions → Update connections. Note If your Shopify vendor names are inconsistent (“Acme” vs. “Acme Inc”), they won’t merge on their own. Either clean up the Shopify vendor list first, or attach all the spellings to the same supplier as separate vendor connections. ## See also - [Supplier directory] (/features/suppliers/directory/): where suppliers appear. - [Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/): what the links are. - [Inventory → Data exclusion] (/features/inventory/data-exclusion/): what’s filtered out of the refresh. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/suppliers/credits/ # Supplier credits The credit ledger: how credits accumulate, the balance, and how to manage them. In Logistified, a [supplier credit] (/reference/glossary/#supplier-credit) is a balance you have with a supplier, money they owe you. Each credit is stored with its own currency and stays available until you apply it to a future PO. This page is the canonical home for the credit ledger: how credits come into existence, how the balance works, and how to manage them. ## On this page - Where credits come from - Currency awareness - Balance computation - Viewing credits - Issuing a credit manually - Voiding a credit - Applying a credit - The credit limit field - See also ## Where credits come from Two origins, both operator-driven: - Return order (RMA) credit: minted when you issue credit on a Return Order. This is the most common source. See [Return Orders → Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/). - Manual credit on the supplier: created directly from the supplier detail page (Credits tab → Add credit) when you have a credit that didn’t come from an RMA in Logistified (a goodwill credit, a credit from before you started using Logistified, a settlement, etc.). Logistified does not auto-create credits from PO payment activity; if a supplier owes you money for any reason that isn’t an RMA, record it manually. ## Currency awareness Each credit stores its own currency. Application respects it: applying a credit to a PO in the same currency is straightforward, while applying it to a PO in a different currency requires an explicit exchange rate at the time of application (the PO-detail credit picker will prompt for one). The supplier-level balance roll-up shown at the top of the Credits tab, however, doesn’t currently separate by currency; it sums every active credit for the supplier and labels the total with whichever currency the supplier’s first credit was minted in. If your supplier has credits in mixed currencies, trust the per-credit list (which shows each credit’s currency) rather than the headline number, and prefer keeping a supplier on a single currency where you can. ## Balance computation The available balance per supplier is: ``` Sum of active credits (all currencies) − Sum of applications against those credits = Available balance ``` Currency is not part of the roll-up. A credit stays “active” even after it’s been partially applied; applications are tracked separately so a credit can be split across multiple POs. ## Viewing credits Suppliers → Supplier detail → Credits tab: - Per-credit list with mint date, source (PO or RMA), original amount, currently available amount. - Application history per credit. - Total available balance. ## Issuing a credit manually From the supplier detail page → Credits tab → Add credit. Fill in amount, currency, source, notes. The [credit memo] (/reference/glossary/#credit-memo) number is auto-generated. This is one of the two real entry points (the other is the RMA flow); use it whenever the credit didn’t originate from a Return Order in Logistified. ## Voiding a credit [Voiding] (/reference/glossary/#void) removes the credit from the available pool. Voiding is irreversible. Use Edit instead if you just need to correct the amount or notes; only void when the credit was issued in error and shouldn’t exist at all. Edit is available for credits you created manually. RMA-issued credits have a narrower edit path (you can adjust notes and a few fields, but the linked RMA constrains the rest); to substantially change one, void it and re-issue from the RMA. ## Applying a credit Application happens from the PO detail page, not from the supplier. See [Purchase Orders → Applying supplier credits] (/features/supply-orders/purchase-orders/credits/). ## The credit limit field The supplier row has a “credit limit” field. It’s display-only; Logistified doesn’t enforce it against PO totals or against the available balance. Use it as a soft reminder to your team. Caution The balance total at the top of the Credits tab is a blended sum that ignores currency. If your supplier has multi-currency credits, read each credit’s own currency from the per-credit list rather than trusting the headline figure. Note Credits have no expiry date in Logistified. If your supplier-side credit expires, you have to track that externally. ## See also - [Return Orders → Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/): minting credits from returns. - [Purchase Orders → Applying supplier credits] (/features/supply-orders/purchase-orders/credits/): using a credit on a PO. - [Guides → Apply a supplier credit to a PO] (/guides/apply-supplier-credit-to-po/): worked walkthrough. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/importing/ # Importing suppliers Bulk-create suppliers and supplier–variant links via CSV or XLSX. For initial setup or migration from another tool, [bulk import] (/reference/glossary/#bulk-import) beats clicking around. Logistified accepts CSV / XLSX uploads for suppliers and supplier–variant links, including Stocky-style exports. ## On this page - What you can import - The unified import flow - The Product MOQ column - Stocky import - Variant ID flexibility - SKU case sensitivity - Partial-failure behavior - See also ## What you can import - Suppliers: name, contact details, address (including a dedicated Province / State field), currency, payment terms. - Supplier–variant links: per-row supplier SKU, cost, MOQ, Product MOQ, pack size, lead time. - Existing-system imports: Stocky-style exports are supported (see below). ## The unified import flow Imports in Logistified share the same flow wherever they’re offered: 1. Open the import where the data lives; supplier–variant links upload from a supplier’s detail page; supplier records themselves come in through the guided Stocky import (below). 2. Choose a file (CSV / XLSX). 3. Logistified auto-detects the columns. If every required field matches a column, the mapping screen is skipped entirely and you land straight on the import’s own review screen; if something is unmatched, you map it by hand first. 4. Review what was parsed. For supplier–variant links that’s a per-row table showing which rows will be created, which will update an existing link, and which will be skipped with a reason; for the Stocky import it’s the supplier list. Both screens carry a Change mapping button if the auto-detection got a column wrong. 5. Confirm. The supplier–variant import finishes on a summary screen where you tick Confirm import and click Import N variants. If you import the same file shape regularly, save the mapping as an [import template] (/reference/glossary/#import-template) for reuse (Settings → Import Templates). ## The Product MOQ column The supplier–variant round-trip file carries two minimum-order columns, and they mean different things: - MOQ is always the per-variant number. It is written to the row you’re importing and never becomes a product minimum, whatever the supplier’s setting. - Product MOQ is the minimum for the whole product, all of its variants combined. See [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product) for what that means. Because a product has one minimum but many rows in the file, Logistified resolves the column per product: it takes the highest Product MOQ among that product’s accepted rows and stores that as the product’s minimum. If the sizes of one product disagree, the confirm screen warns you, naming each product, the values it found, and the one that wins. - A blank Product MOQ cell contributes nothing; the product keeps whatever minimum it already had. Use 0 for “no minimum”. - A file without the Product MOQ column never writes a product minimum at all, whatever the supplier’s setting; the confirm screen says so. - Rows that get skipped (missing variant, duplicate, validation error) don’t contribute their Product MOQ either. - If the supplier’s minimums currently apply per variant only, the values are still saved; they just stay inactive until you switch that supplier to per-product minimums. Both the preview table and the confirm screen restate these rules while you’re importing, and you can expand any row in the preview to review or edit its Product MOQ before committing. ## Stocky import The Stocky import dialog (launched from the Suppliers page’s create menu via Create from import) walks you through a guided multi-step flow. [anchor: step-1--upload-your-suppliers-file] ### Step 1: Upload your suppliers file Upload your Stocky suppliers export (CSV/XLSX). Logistified parses and validates it automatically. [anchor: step-2--review-suppliers] ### Step 2: Review suppliers A table shows every supplier found in the file. Tick the ones to import. Rows that match a supplier already in Logistified are flagged; you can import them as new suppliers or update the existing ones. [anchor: step-3--add-variants-to-suppliers] ### Step 3: Add variants to suppliers After confirming which suppliers to import, choose one of three ways to populate them with their product variants: Upload a variants file: the classic path. Logistified will ask you to upload your Stocky supplier-products export, then lets you review which variants map to which supplier before confirming. Match vendors to suppliers by name: the file-free path. Logistified reads your Shopify product vendors and auto-matches them to the suppliers you selected, based on name similarity. Three levels of strictness: Strictness What it means Exact Supplier name and vendor name are identical Contains One name is a substring of the other Partial Both names share a significant word On the matching screen you see each supplier as a card showing which vendors were matched. You can remove a vendor from a supplier or add one from the unmatched list using the Add vendor picker. Every matched vendor’s variants are assigned to the supplier when you click Create N suppliers (the button counts the suppliers you selected). Suppliers with no match are still created; they just start with no variants attached. Note Changing the match strictness re-runs the auto-match and clears any manual adjustments you made below. Finalize the strictness level first, then fine-tune individual supplier cards. Create suppliers only: skip variant assignment for now. The suppliers are created with no variants attached and you add them to each supplier later. ### Result screen After a successful import you’ll see a summary: Suppliers created, Variants assigned, and (when using the vendor-matching path) Vendor connections, the number of supplier–vendor links that were created. These connections also appear under Manage connections on each supplier’s detail page, where you can refresh them as your Shopify vendor list changes over time. Note A Province / State column in your suppliers file fills the supplier’s dedicated State / Province address field. Imports run before this field existed appended the value to the supplier’s notes as a Province: … line instead; PO PDFs still read that line as a fallback, but the supplier list and exports only read the address field, so re-save affected suppliers with the state/province filled in to fix it everywhere. ## Variant ID flexibility Both the full Shopify global variant identifier (e.g., gid://shopify/ProductVariant/12345) and the bare numeric ID (12345) are accepted. Logistified normalises. ## SKU case sensitivity Within a single file, dedupe by Variant ID or SKU is case-insensitive; rows for “ABC-001” and “abc-001” are flagged as duplicates of each other. Matching a row against your Shopify catalogue is case-sensitive, though: a row whose SKU reads abc-001 will not find a variant stored as ABC-001, and is reported as not found. Keep the casing identical to Shopify, or map the Variant ID column instead. ## Partial-failure behavior Supplier–variant links import as a bulk upsert: every valid row is created or updated, and rows that failed validation are skipped and reported individually with a reason: missing Variant ID or SKU, a duplicate of an earlier row, or a variant that isn’t in your catalogue. One bad row never rolls back the rest. The preview step marks each row’s outcome before you commit, so you can fix the file and re-upload rather than importing a half-mapped batch. Tip Always start with a small import (10 rows) to validate your column mapping before running a 10,000-row file. Note An import never deletes supplier–variant links; to remove one, do it manually. It can still blank fields, though: by default every column present in your file is written, so an empty cell overwrites whatever was there. On the confirm screen, tick Only update cells with values to have empty cells ignored instead. ## See also - [Guides → Import data (CSV/XLSX)] (/guides/import-data-csv-xlsx/): the canonical walkthrough. - [Settings → Data import & templates] (/features/settings/data-import-and-templates/): saved column-mapping presets. - [Supplier directory] (/features/suppliers/directory/): where imported suppliers appear. - [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#defaults-for-new-links): the supplier-level defaults an import falls back to. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/suppliers/exports/ # Exporting suppliers Bulk CSV/XLSX export from the supplier list, plus the export templates that shape it. Export your Logistified suppliers or their items to a spreadsheet, in a column layout you control. ## On this page - Exporting from the supplier list - Choosing what to export - Export templates - See also ## Exporting from the supplier list Select one or more suppliers on the [supplier list] (/features/suppliers/directory/) (or use Select all N matching), then open Actions → Export suppliers. A three-step dialog walks you through what to export, then the file format: 1. What: pick Supplier level or Supplier items (see below). 2. Format: pick XLSX or CSV, and optionally a saved export template. If you have no saved templates for that export type, the dialog skips the picker and uses the built-in default columns. 3. The file downloads automatically once it’s ready. Your selection stays in place afterward, so you can export both levels back to back without reselecting. Note If every selected supplier has no items, a Supplier items export reports “The selected suppliers have no items” instead of downloading an empty file. A Supplier level export always produces one row per supplier, even for suppliers with no items; their item count just reads 0. ## Choosing what to export Export type Rows What’s in it Supplier level One row per supplier Contact, address, currency, payment terms, tax ID, minimum order value, plus a “Supplier summary” block: item count, primary-item count, default To/CC email recipients, and connected vendor names. Supplier items One row per supplier item (a supplier–variant link) The supplier header repeated on every row, plus supplier SKU/name/cost, MOQ, pack size, lead time, primary-supplier flag, tiered pricing, and live product/variant data (title, current inventory totals, ABC tier). A Supplier Product MOQ column is available in the picker for the whole-product minimum, which is blank when the product has none. Both exports respect your current [data exclusion] (/features/settings/data-exclusion/) settings; archived products are left out by default, the same way they’re left out everywhere else supplier items are counted or listed. Note Supplier item exports don’t include stock figures for a specific location; a supplier item isn’t tied to one. For inventory at a particular location, export from a purchase order’s line items instead (see [Purchase Orders → Exports] (/features/supply-orders/purchase-orders/exports/)). ### This is different from the detail page’s “Export variants” An individual supplier’s detail page has its own Export variants download (under the Variants tab’s upload/download menu). That file always uses the same fixed columns, because it’s built to be re-imported: it’s the round-trip file the [supplier-variant importer] (/features/suppliers/importing/) accepts back for bulk updates. It carries both minimum-order columns (MOQ for the per-variant number and Product MOQ for the whole-product minimum), so you can set product minimums in bulk by editing the download and uploading it again. See [The Product MOQ column] (/features/suppliers/importing/#the-product-moq-column) for how those values are resolved on the way back in. The list-page export described on this page is template-driven and not guaranteed to re-import; use it for reporting and downstream systems, not as an edit-and-reupload workflow. ## Export templates Manage saved column layouts at Settings → Logistics → Suppliers → Export templates. Two independent template families exist, one per export type above, each with its own default template (“Default Supplier Level XLSX/CSV” and “Default Supplier Items XLSX/CSV”) that Logistified creates automatically the first time you visit the settings page or open the export dialog. - Column selection: search and check the columns you want, in any order. The Available columns list groups by source (Supplier, Supplier summary, Supplier item, Product, Product variant, plus live inventory and metrics on item templates); see [Settings → Data export templates → Finding a column] (/features/settings/data-export-templates/#finding-a-column) for how the picker works generally. - Set as default: mark one template per family as the default; it’s preselected in the export dialog (still changeable per export). - Suppliers have no PDF documents and no per-supplier template assignment, so those controls don’t appear on this settings page, unlike Purchase Orders or Return Orders, which have both. You can save as many templates as you need (e.g. one column set for accounting, another matched to a downstream system’s import format) and pick between them each time you export. ## See also - [Supplier directory] (/features/suppliers/directory/): the list page and its other bulk actions. - [Importing suppliers] (/features/suppliers/importing/): the reverse direction (CSV/XLSX → suppliers). - [Settings → Data export templates] (/features/settings/data-export-templates/): the general export-template concept shared across features. - [Purchase Orders → Exports] (/features/supply-orders/purchase-orders/exports/): location-scoped inventory exports. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/suppliers/accounting-contacts/ # Accounting contacts Link suppliers to their Xero contact record so purchase-order bills sync to the right place. Once [Settings → Accounting] (/features/settings/accounting/) is connected, each supplier can be linked to a matching contact in your accounting system. The link is what tells Logistified which record a purchase order’s bill should be created against. This page covers linking one supplier at a time, and the two bulk flows for linking many at once. ## On this page - Linking one supplier - What happens without a link - Importing suppliers from your accounting system - Matching existing suppliers in bulk - See also ## Linking one supplier Open a supplier and click Edit. When accounting is connected, an Accounting section appears in the edit dialog (and in its section jump-navigation). It shows: - A Connected badge if the supplier is already linked. - A search field (placeholder “Connect to accounting…”) for picking a contact. Search by name; each result shows the contact’s name, email, and a supplier badge if your accounting system already flagged that contact as a supplier. - A Disconnect button once linked, and a Clear mapping option inside the picker. Picking or clearing a contact saves immediately; you don’t need to click the dialog’s Save Changes button for this field. The helper text under the field tells you the current state: “Linked to [Contact Name] in accounting” or “Link this supplier to its accounting contact so purchase orders sync to the right record.” ## What happens without a link A supplier doesn’t have to be linked before its first bill push. When a purchase order syncs and its supplier has no linked contact: 1. Logistified looks for a Xero contact whose name exactly matches the supplier’s name. If one exists, it’s adopted; the bill posts to it, and the supplier is linked to it from then on. 2. If no contact matches, a new contact is created in Xero with the supplier’s name, and the supplier is linked to it. An explicit link always wins over name matching; once a supplier is linked (by any of the flows on this page, or by the auto-adopt above), the name is irrelevant and renaming either side changes nothing. Suppliers that can’t produce a usable contact at all (an unnamed supplier, or the “Default Supplier” placeholder) can’t sync, and the order’s Accounting card says so. Tip If your Xero contact is named differently from the supplier (“ACME GmbH” vs “Acme”), link it explicitly before the first push; otherwise that push creates a second, duplicate contact under the supplier’s name. ## Importing suppliers from your accounting system Rather than creating suppliers first and linking them one by one, you can import contacts straight from Xero as new suppliers, already linked. On the Suppliers page, open Create supplier → Import from Xero. You’ll see a checklist of contacts from your accounting system: name, email, and a supplier badge where applicable. Contacts already linked to an existing supplier show a greyed-out linked badge and can’t be selected again. 1. Search or scroll to find the contacts you want. 2. Use Select all / Deselect all, or tick individual rows. The header shows a running count. 3. Click Import [N contacts]. Import runs one contact at a time with a progress indicator. When it finishes, a summary breaks results into Created, Linked, Skipped, and Failed, with the reason for each. Every successfully imported contact becomes a new supplier, automatically linked. Note If your accounting system has more contacts than fit in one page, the dialog notes that only the first batch is shown; refine your accounting data if a contact you expect is missing. ## Matching existing suppliers in bulk If you already have suppliers in Logistified and want to link them to existing accounting contacts, the linking process runs through the supplier list’s selection actions instead of linking one at a time: 1. On the Suppliers page, mark the suppliers you want to link; tick their rows, or use Select all matching to mark every supplier in the current view. 2. In the selection toolbar, open Actions → Match to Xero: “Link each selected supplier to its Xero contact (auto-matched by name).” Logistified auto-suggests matches by comparing supplier and contact names (ignoring case and extra whitespace) and shows how many of the selected suppliers it matched automatically. Each row lists one supplier with a contact picker pre-filled with the suggested match, or Skip (no match) if nothing matched. Review and override any row before applying; only rows with a chosen contact are linked; skipped rows are left untouched. Click Link [N suppliers] to apply. Linking runs sequentially with a progress indicator, then shows a result per supplier (Linked or an error) with a summary count. ## See also - [Settings → Accounting] (/features/settings/accounting/): connecting Xero in the first place. - [Purchase Orders → Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/): a purchase order with a missing, unnamed, or “Default Supplier” supplier can’t sync; this is where you’d see that error. - [Accounting → How bill sync works] (/features/accounting/how-bill-sync-works/): where the linked contact ends up on the bill. - [Supplier directory] (/features/suppliers/directory/): the supplier list and detail page these dialogs are launched from. Last updated: 21 July 2026 --- Source: https://docs.logistified.app/features/supply-orders/overview/ # Supply Orders Purchase orders, transfer orders, supplier stock releases, return orders, and manufacturing orders: every flow that moves stock in or out lives here. Tour of Logistified’s Supply Orders section: the order types (PO, TO, Supplier Stock Releases, RMA, Manufacturing Orders), their lifecycles, and how they interact with Shopify inventory. ## What’s on the Supply Orders page The hub itself opens on a set of cards, one per order type, each showing how many are currently open and linking to that list: - [Purchase orders] (/features/supply-orders/purchase-orders/overview/): buy stock from a supplier. - [Transfer orders] (/features/supply-orders/transfer-orders/overview/): move stock between your own locations. - [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/): bring supplier-held stock into a warehouse. Elevate plan. - [Return orders] (/features/supply-orders/return-orders/overview/): send stock back to a supplier and track the credit. Elevate plan. - [Manufacturing orders] (/features/supply-orders/manufacturing-orders/overview/): plan builds and track production. Elevate plan. Below the cards are two tabs: - Continue Where You Left Off: the documents of each type you touched most recently. - [Orders] (/features/supply-orders/orders-tab/): your Shopify customer orders, with filters and the actions that turn a selection into a purchase, transfer, or return order. --- Source: https://docs.logistified.app/features/supply-orders/orders-tab/ # The Orders tab Browse your Shopify orders inside Supply Orders, filter them by payment, fulfillment, state, tags and date, and turn a selection into a purchase, transfer, or return order. Logistified’s Supply Orders hub has an Orders tab that lists your Shopify customer orders. It’s the demand-side view of the section: find the orders you need to buy, move, or return stock for, and start the matching supply order straight from them. ## On this page - What the tab lists - Searching - Filters - Filtering by tag (Include / Exclude) - Save Filters - Creating orders from a selection - From the Shopify admin - See also ## What the tab lists Open Supply Orders and switch from Continue Where You Left Off to Orders. Every Shopify order Logistified has synced appears here, newest first, 50 per page, with: Column What it shows Order The Shopify order number. Date When the order was placed. Status Its fulfillment state, plus a cancelled or return indicator where one applies. Payment Paid, partially paid, unpaid, refunded, or partially refunded. Items How many units the order contains. Total The order total in its own currency. Linked Orders Badges for every supply order already raised from this one: PO:, TO:, RMA:. Click a badge to open it. Two linked badges show inline; any beyond that collapse into a +N button that lists the rest on hover. An order with nothing raised from it shows a dash. ## Searching The search box matches the order number; type 1042 or #1042. It doesn’t search customers or products; for those, use the filters below or Shopify’s own order search. ## Filters Each control is a multi-select: pick as many values as you like, and the list narrows to orders matching any of them. - Payment: Paid, Partially paid, Unpaid, Refunded, Partially refunded. - Fulfillment: Fulfilled, Partially fulfilled, Unfulfilled. - State: Active or Cancelled, plus the return states: No return, Unreturned, Return requested, Return in progress, Inspection complete, Returned, Return failed. - Linked: Has Purchase Order, Has Return Order, Has Transfer Order, or No linked orders. Handy for “which orders have I not ordered stock for yet?” - Tags: your store’s own order tags, with an include / exclude switch. See below. - From / To: an order-date range. Either bound works on its own, and the small × on the button clears just that date. Clear all appears as soon as anything is active and resets the search and every filter in one click. ## Filtering by tag (Include / Exclude) The Tags picker lists the order tags in use in your store and searches as you type. Above the list is a two-way switch: - Include (the default): show only orders carrying at least one of the tags you picked. - Exclude: hide orders carrying any of them. The picker’s footer says so explicitly: “Hides orders carrying any selected tag.” Untagged orders are still shown; excluding a tag removes only the orders that have it. The mode does nothing until at least one tag is selected. While Exclude is active, the closed picker reads Not in front of the selected tags, so it’s obvious from the toolbar which way round the filter is. ## Save Filters Save Filters stores the current state of this toolbar (the search term, all five pickers, the tag mode, and both dates) as your personal default for the Orders tab. Next time you open it, the tab comes back the way you left it. To remove the default, press Clear all and then Save Filters again: saving an empty toolbar is what clears it. Note This default is stored in your browser, for this shop and your staff account, so it doesn’t follow you to another computer and doesn’t change what your colleagues see. It’s deliberately different from the named, shop-wide presets on the purchase order, transfer order, and return order lists; see [Search, filters & saved views] (/features/supply-orders/purchase-orders/search-and-filters/#saving-a-filter-set-as-a-preset). ## Creating orders from a selection Tick the checkbox on one or more rows and use the Actions menu at the right of the toolbar: - Create PO from selected orders: opens the [sales-orders purchase order wizard] (/features/supply-orders/purchase-orders/creating/#sales-orders-wizard-choosing-a-destination) with those orders already picked, so you can aggregate their items onto a new PO, an existing Draft PO, or a split across suppliers. - Create TO from selected orders: opens the equivalent [transfer order] (/features/supply-orders/transfer-orders/creating/) flow, for covering the demand from another one of your locations. Every row also has its own actions menu for working with a single order: Create PO from Order, Create TO from Order, and (on the Elevate plan) Create RMA from Order, which starts a [return order] (/features/supply-orders/return-orders/overview/) from the items on it. ## From the Shopify admin You can start a purchase order straight from your Shopify admin, without opening Logistified first: from one order’s page, or from several orders on the orders list. ### One order, from its page On the order’s page in your Shopify admin, open More actions and choose Create purchase order. [Image: A Shopify order page with the More actions menu open, filtered to the Create purchase order entry under Apps] (/_astro/13-shopify-order-more-actions.Cxo9MQum_1JO7pY.webp) More actions on a Shopify order: Create purchase order. Logistified opens on this Orders tab with the Create PO from Customer Orders window already open and filled with that order’s items. It’s the same [sales-orders wizard] (/features/supply-orders/purchase-orders/creating/#sales-orders-wizard-choosing-a-destination) that Create PO from Order opens. From there: 1. Check the items, adjust quantities or remove the ones you don’t need, then press Next. 2. Choose where the items go: Dropship, to have the supplier ship straight to your customer, or one of your locations. Then pick the supplier. 3. Create the purchase order. [Image: The Create PO from Customer Orders window on Review items, listing the three lines of order #12897 with their quantities] (/_astro/14-shopify-order-wizard.DeS5TEz__Z2fdXiK.webp) The wizard opens on Review items with the order's lines already in the cart. ### Several orders, from the orders list On your Shopify admin’s Orders list, tick the orders you want, open the … menu in the bar that appears above the list, and choose Create purchase order under Apps. [Image: The Shopify orders list with three orders selected and the bulk actions menu open on Create purchase order under Apps] (/_astro/15-shopify-orders-list-bulk-action.BczoDous_ZhYf1b.webp) Select orders, then … → Create purchase order. The same wizard opens with every selected order’s items in the cart. An item that several of the orders contain becomes one cart row with the quantities added up, and the row shows which orders it came from. Choosing Dropship still creates one purchase order per order, each shipped to that order’s customer; choosing a location creates one purchase order for all of them. A few things to know: - The order hasn’t reached Logistified yet. A brand-new order usually arrives within a minute. If you click before it has, the wizard opens empty and a message says the order isn’t in Logistified yet. Wait a moment, then use Add more orders to find it by its number. Orders older than the [years of order history] (/getting-started/onboarding-wizard/) you chose during onboarding can’t be used. - Logistified can’t tell which order you clicked. Now and then Shopify opens Logistified without naming the order, or Logistified can’t look it up. The wizard then opens empty with a message; use Add more orders to pick the order. - Up to 50 orders at a time. That’s one page of the Shopify orders list. If more arrive, the first 50 are added and a message says how many were left out; add the rest with Add more orders. - Some of the selected orders aren’t in Logistified yet. The wizard opens with the ones that are, and a message says how many are missing. - It opens once. Closing the wizard, reloading the page or going back doesn’t open it again. Start again from the Shopify order if you need to. ## See also - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): the wizard these actions open, and every other way to start a purchase order. - [Transfer orders → Creating] (/features/supply-orders/transfer-orders/creating/): the transfer-order side of the same flow. - [Search, filters & saved views] (/features/supply-orders/purchase-orders/search-and-filters/): the shop-wide preset mechanism used on the supply order lists themselves. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/line-item-views/ # Line-item column views Choose, reorder and save the columns on a supply order's line-item table, on purchase orders, transfer orders, returns and supplier stock releases. Every Logistified supply order (purchase order, transfer order, return, supplier stock release) shows its line items as a table. Views let you decide which columns that table shows, in which order, and save the result so it comes back the next time you open any order of that type. ## On this page - What a view is - Built-in views - The view tabs - Choosing and reordering columns - Sorting - Cost basis for the margin columns - Saving your own view - Renaming, duplicating and deleting - Your default view - What views do and don’t change - See also ## What a view is A view is a named set of columns, plus the order they appear in, plus a sort and a cost basis. Views are saved per store and per order type: a view you save on a purchase order is available on every purchase order, but not on transfer orders. Views only change what you see. Nothing about the order itself (quantities, costs, statuses) depends on which view is active. ## Built-in views Each order type ships with read-only built-in views. They carry a small lock icon and can’t be edited or deleted, but you can start from one, change what you like, and save the result as a view of your own. Order type Built-in views What they show Purchase orders Standard, Inventory, Sales Standard is the operational set (SKU, barcode, quantity, constraints, cost, landed cost). Inventory and Sales replace the old sub-tabs of the same names. Transfer orders Standard SKU, barcode, quantity, stock at the origin and destination locations, line status. Returns (RMAs) Standard SKU, barcode, supplier mapping status, requested and approved quantities, unit cost, credit, reason. Supplier stock releases Standard SKU, barcode, requested / shipped / received / open quantities, sync status, line status. Note If you used the Inventory and Sales tabs on the purchase-order line-item table, they are now built-in views with the same columns. Pick them from the view tabs instead of the old sub-tabs. ## The view tabs Above the line-item table sits a row of tabs: 1. The built-in views first, each with a lock icon. 2. Then your saved views, default first and the rest alphabetically. 3. Then, on purchase orders and supplier stock releases, the fixed layouts Schedules and Receipts behind a thin divider. Those aren’t views; they’re separate read-only layouts of the same lines. Clicking a tab switches to it. Clicking the tab you’re already on (or right-clicking any other view of your own) opens its options menu. Built-in views have no menu; they’re locked. When you change something about the active view (columns, order, sort, cost basis), a small dot appears on the tab and a Save button appears at the end of the row. To throw the changes away, use Discard, next to Save on a built-in view, or in the view’s own menu on one of yours. Switching to another tab discards them too. ## Choosing and reordering columns The Columns button opens the picker: - Visible columns is the list at the top. Drag a row to move it; that list’s order is the table’s column order. - Below it, the columns you can add, grouped by theme: Product, Order, Pricing, Costs & Margin, Inventory, Sales, and on transfer orders [Manufacturing (Assemblified)] (/features/supply-orders/transfer-orders/assemblified-materials/). Which groups appear depends on the order type. - The search box filters both lists. - At least one column must stay visible. Columns that don’t apply to a line still show up; they just render a dash with a short explanation on hover. Custom items and lines without a Shopify product behind them do that for every product-backed column, for example. Every column header explains itself too: hover a header, or focus it with the keyboard, to see what that column means and how it’s calculated, the same wording shown in the Columns picker. Clicking still sorts; the explanation doesn’t get in the way of that. ## Sorting Click a column header to sort by it. Clicking again reverses the direction; a third click clears the view’s own sort and returns the table to the page’s default order. Some headers offer a choice of sort key; the SKU header can sort by your Shopify SKU or by the supplier’s SKU, and Barcode does the same. Use the supplier-side key when the receiving workflow needs to match the order your supplier uses. The row order you see is the row order used by the order’s exports and supplier-facing documents. ## Cost basis for the margin columns Some columns (Margin, Markup, Gross Profit / Unit, Gross Profit / Line) need a unit cost to divide by. A Cost basis control appears next to the Columns button whenever one of those columns is visible, and offers: Basis What it uses Direct The unit cost recorded on the line. Landed The unit cost including allocated charges. Falls back to Direct until charges allocate. Shopify cost The cost per item stored on the variant in Shopify. All of these calculate in your shop currency, and the choice is saved with the view. If your shop has [tax-exclusive retail prices] (/features/settings/tax-rates/#margins--retail-prices) turned on, Margin, Markup, and Gross Profit divide out the tax before comparing price against cost, and the column header gains an “excl. tax” suffix alongside the basis name, for example Margin (Landed, excl. tax). A few pages narrow this: - On transfer orders and returns, nothing allocates charges, so Landed always equals Direct. - On supplier stock releases, release lines carry no unit cost of their own, so Direct and Landed can never resolve; the picker marks both “not available here” and those columns show a dash. Use Shopify cost instead. ## Saving your own view - Change the columns, order, sort or cost basis on one of your own views, then press Save. The same button’s menu offers Save as copy… if you’d rather keep the original. - Change them on a built-in view and the button reads Save as… instead; built-in views can’t be overwritten, so the edit becomes a new view of your own. - + Create view at the end of the tab row saves what’s currently on screen as a new view without touching the one you started from. - View names can be up to 120 characters. Saved views are shared across your store: everyone who opens an order of that type sees them. ## Renaming, duplicating and deleting Open one of your views’ menus (click its tab while it’s active, or right-click it) for Rename, Set as default and Delete. The active view’s menu also offers Duplicate…, which forks what’s currently on screen. Built-in views have no menu. Deleting the view you’re currently on drops you back to your default view, or the first built-in one if you haven’t set a default. ## Your default view Set as default marks one view per order type as the one those pages open on. There can only be one at a time; setting a new default clears the previous one. Clear default view removes the mark, and pages fall back to the first built-in view. ## What views do and don’t change - Views change columns, their order, sorting and the cost basis, nothing else. - They do not change what’s editable; what you may edit still depends on the order’s status. On purchase orders, Bulk Edit keeps your view’s own columns and order, adding any operational fields (like the quantity breakdown or Notes) your view doesn’t already show; on other order types, Bulk Edit still shows its own fixed set of editable columns regardless of the active view. - They do not change totals, receipts, or anything that syncs to Shopify. The one exception is the price columns, which are directly editable; see [Editing retail prices] (/features/supply-orders/editing-prices/). - If a saved view refers to a column that no longer exists, that column is quietly dropped and the page tells you which ones went. Save the view again to make it stick. Tip Build one view per job rather than one big one. A short “Receiving” view with quantities and barcodes reads far faster on a warehouse screen than a twenty-column table. ## See also - [Editing retail prices] (/features/supply-orders/editing-prices/): the price columns write straight to Shopify. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): what each purchase-order column means, and how Bulk Edit works. - [Purchase order exports] (/features/supply-orders/purchase-orders/exports/): where the on-screen row order ends up. - [Saved views on the forecast] (/guides/create-and-save-custom-views/): the same idea on the forecast table, with filters. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/editing-prices/ # Editing retail prices Change a variant's retail and compare-at price straight from a supply order's line-item table, one cell at a time, or many at once. The Retail price and Compare-at price columns on a Logistified supply order’s line-item table aren’t a snapshot; they’re the live values from Shopify, and you can edit them in place. It’s the fastest way to reprice while you’re already looking at what a product costs you. Caution These edits change your storefront. A confirmed price is written to Shopify immediately and is visible to customers straight away. ## On this page - Where you can edit prices - Editing one price - Clearing a compare-at price - Editing many prices at once - When a price can’t be edited - When something goes wrong - See also ## Where you can edit prices On all four supply-order types: purchase orders, transfer orders, returns and supplier stock releases. The columns aren’t shown by default: open Columns and add Retail price, Compare-at price, or both, then save the view if you want them to stay. See [Line-item column views] (/features/supply-orders/line-item-views/). Adding the columns is also what enables editing. If neither is visible, the price cells aren’t there to click. ## Editing one price Click a price cell, type the new amount, and press Enter. Escape cancels. Before anything is written, Logistified asks “Change the live price?” and shows the old value struck through next to the new one. Confirm with Update price. The dialog carries a Don’t ask again this session checkbox. Ticking it skips the confirmation for the rest of your session; closing the tab brings it back. Amounts accept both decimal separators: 1,50 and 1.50 are the same thing. The retail price has to be zero or more. ## Clearing a compare-at price Leave the Compare-at price cell empty and confirm; that removes the compare-at price on the variant, which removes the “was” price from your storefront. The retail price can’t be cleared the same way. Emptying that cell just cancels the edit. ## Editing many prices at once On purchase orders, the price columns are also available in Bulk Edit, but only when the active view actually shows them. A price isn’t purchase-order data, so the editor only offers it when you’ve put it on screen. If a Margin, Markup, or Gross Profit column is also visible, each price cell shows a small live percentage as you type: the margin your staged amount would produce, not the one still live in Shopify. The retail input previews the margin at the retail price you’re typing; the compare-at input previews it at the compare-at price. It updates as you type and disappears for an empty, invalid, or zero amount. Hover or focus the cell for the full sentence, including which cost basis it used. Stage as many price changes as you like, then press Save all changes. You get one confirmation listing every row that will change, headed “Change N live prices?”. Note Confirming that dialog also commits the other staged edits on the table: quantities, costs, notes. It’s one save, not two. While a save is running, the table stays open and locked: Exit Edit and the other editable cells are unavailable until it finishes, and starting a second save does nothing. The window is short and ends on its own; nothing is lost by waiting. If the price check couldn’t reach Shopify for this page, the save is blocked rather than attempted: the save bar says so and offers Retry the price check. Your staged changes stay exactly where they are. ## When a price can’t be edited A greyed-out cell explains itself: hover it, focus it with the keyboard, or tap it on a touch device: What you see Why “Custom item with no Shopify variant behind this line.” Custom line items aren’t Shopify products, so there’s no price to change. “This line has no Shopify product.” The line isn’t linked to a product in Shopify. “Shopify returned no live price for this variant…” Shopify didn’t return a price for that variant, usually a deleted variant. “Prices could not be checked against Shopify…” The live price check failed. Editing stays off until it succeeds; use the Retry offered on the save bar. “Add the Retail price or Compare-at price column to edit prices.” Neither price column is in the active view. ## When something goes wrong Each row settles on its own, so a partial failure is normal and safe: - Rows that saved show their new value. - Rows that failed stay marked in red with the reason on the row. - The summary toast tells you how many updated and how many failed. If Shopify accepted a change but Logistified couldn’t confirm it locally, you’ll see a warning rather than an error, and the prices are re-checked automatically. The value in Shopify is the one that counts. ## See also - [Line-item column views] (/features/supply-orders/line-item-views/): adding the price columns and saving the view. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): Bulk Edit on the purchase-order table. - [Product & variant attributes] (/features/settings/product-and-variant-attributes/): the other variant fields Logistified reads from Shopify. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/assemblified-sub-assemblies/ # Sub-assemblies from Assemblified Buy, transfer, return, release and count the sub-assemblies Assemblified builds, with every stock change sent to Assemblified. If your store uses Assemblified, its sub-assemblies (pre-built components it keeps on a shelf, SKUs starting with ASM-) appear in Logistified like any other item. You can put them on purchase orders, transfer orders, return orders, supplier stock releases, stock takes and stock adjustments. Assemblified stays in charge of their stock: every change a document makes is sent to Assemblified, and the quantity you see in Logistified updates when Assemblified confirms it, usually within seconds. ## On this page - Adding sub-assemblies to documents - How their stock changes - Purchasing sub-assemblies - Transfers - Stock takes and adjustments - Returns and supplier stock releases - When a sub-assembly can’t be added - See also ## Adding sub-assemblies to documents Add a sub-assembly the same way as any item. The Virtual materials picker lists them after the virtual materials, each marked Assemblified sub-assembly. Imports, the forecast and the Reporting bulk actions accept them too. ## How their stock changes A sub-assembly’s quantity in Logistified always mirrors Assemblified’s shelf. When you receive a purchase order, send or receive a transfer, apply a stock take or move a return, Logistified sends that change to Assemblified instead of to Shopify. While it is on its way the line shows that it is syncing to Assemblified, and the quantity stays where it was until Assemblified’s update arrives. Nothing is ever sent to Shopify for a sub-assembly. ## Purchasing sub-assemblies - Map a supplier first. Logistified never assigns a sub-assembly to a supplier on its own, not even the default supplier. Add it to a supplier on the supplier’s page (or through a supplier import) with its supplier cost, like any variant. - Generating a purchase order for one supplier (from the forecast, min-max or sales history) orders the sub-assemblies mapped to that supplier. A sub-assembly the run would have ordered but no supplier is mapped to is named in the dialog with “No supplier is mapped to this sub-assembly. Map one in Suppliers to purchase it.” A forecast filtered by supplier doesn’t show sub-assemblies no supplier is mapped to. - Receiving sends the received quantity to Assemblified, together with the unit price when the order is in your store’s currency or has an exchange rate set on it. Otherwise the price follows when you complete the order. Unreceiving, cancelling or deleting a received line takes the quantity back out of Assemblified. - Unit cost. A sub-assembly’s cost belongs to Assemblified. Completing the order (with automatic cost sync) or using Update unit cost sends Assemblified one purchase price per sub-assembly for the order (its price per unit over the units received, in your store currency) as the sub-assembly’s purchase cost. Assemblified uses it when the sub-assembly’s cost method is Purchase cost and sends the resulting cost back; a moving average is not changed by it, because it takes each purchase at the price on its receipt. A sub-assembly with nothing received on the order yet is not sent; the result names it. The dialog marks such rows Sub-assembly and notes: Sent to Assemblified as the sub-assembly’s purchase cost, which the Purchase cost method uses. It does not change a moving average, which takes each purchase at its receipt’s price. Your supplier’s catalogue cost is updated as usual. Logistified never writes a sub-assembly’s cost itself. - Minimum order quantities and pack sizes from supplier terms don’t apply to sub-assemblies, the same as for virtual materials. ## Transfers Sending a transfer takes the sub-assemblies out of the source location in Assemblified, receiving adds them at the destination, and cancelling after sending puts them back. Note A transfer that contains a sub-assembly can’t be handed to Floormode for execution yet. The Floormode panel on the transfer shows “Floormode cannot execute transfers of Assemblified sub-assemblies yet.” and each sub-assembly line repeats it. You can still create, send and receive the transfer in Logistified. See [Floormode execution] (/features/supply-orders/transfer-orders/floormode-execution/). ## Stock takes and adjustments - A counted sub-assembly is sent to Assemblified as the quantity you counted, once per apply, even when the count matches what Logistified already shows. Assemblified takes the count as the physical quantity on the shelf and works out what is available from it after the orders it already holds stock for. - An adjustment sends the amount you add or remove. Caution Count sub-assemblies after open orders are fulfilled, or adjust afterwards. The Review Changes dialog shows this reminder when a stock take contains sub-assemblies: a count replaces whatever Assemblified did with that stock between the moment you counted and the moment you applied. ## Returns and supplier stock releases Move Inventory on a return order and receiving a supplier stock release send their sub-assembly lines to Assemblified the same way. Reversing a return’s restock sends the opposite change. ## When a sub-assembly can’t be added Logistified support can pause sending sub-assembly changes to Assemblified. While it is paused, documents refuse sub-assemblies with “Sub-assembly write-back to Assemblified is paused.”, the other items on the same request are still saved, and the dialog names the ones left off. Changes already on their way still reach Assemblified. ## See also - [Stock on hand with Assemblified] (/features/reporting/stock-on-hand-assemblified/) - [Adding line items to a PO] (/features/supply-orders/purchase-orders/adding-line-items/) - [Stock takes] (/features/inventory/stock-takes/) - [Supplier variant mapping] (/features/suppliers/supplier-variant-mapping/) Last updated: 16 October 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/overview/ # Purchase orders Order stock from a supplier, track it through its lifecycle, and reconcile against your books. A [purchase order] (/reference/glossary/#purchase-order) records what you’re buying from one supplier (variants, quantities, prices, due dates) and the lifecycle of that order from draft through received and closed. POs are the single largest workflow in Logistified; this section breaks the surface into focused pages. A purchase order is not a transfer order. POs go to a supplier and bring inventory in. Transfer orders move existing stock between your own locations. ## On this page - What a purchase order is - Supplier PO reference - Shipping cost - When to use one - What you can do here - Key concepts - Where to next ## What a purchase order is A PO has a single supplier and many line items. Each line is one variant with its quantities (ordered, confirmed, received, cancelled, rejected), unit cost, and any per-line metadata. The header tracks status, dates, currency, tax rate, and totals. Under the order’s title, a byline records who raised it (Created by First Last · 7 Sep 2026, 14:32) with that person’s email address on hover. Orders created before Logistified started recording this show only the date. The same information is available as a Created by column and filter on the purchase order list; see [Search, filters & saved views] (/features/supply-orders/purchase-orders/search-and-filters/#available-filters). POs are stateful: status changes (Draft to Sent to Confirmed to Received to Completed) trigger side effects in Shopify, the supplier’s inbox, and elsewhere in Logistified. The [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/) page is the full list. Receiving is quantity-based. You can record a full receipt or receive the same PO in multiple passes as stock arrives. Separately, you can track each physical delivery (carrier, tracking number, status, dates, and which line items are in it) as [shipments] (/features/supply-orders/purchase-orders/shipments/) on the order. ## Supplier PO reference In Order Information, click the reference beneath Supplier to edit it, or choose Add supplier PO reference… when it is empty. Enter the supplier’s reference and select Save reference. To remove it, clear the field and save. Cancel keeps the saved reference. The separate copy icon copies the full reference. Editing follows the same rules as Edit Details: it is unavailable while an order is On Hold, Disputed, Completed, or Cancelled, but an existing reference can still be copied. [Image: Supplier PO reference dialog with one reference field, Cancel, and Save reference] (/_astro/13-supplier-po-reference.BUtJtgo1_Z1vLnse.webp) Update the supplier’s reference directly from Order Information. ## Shipping cost In Order Information → Financial Summary, click the amount beside Shipping, even when it is zero. Enter the cost in the order currency shown above the field and select Save shipping cost. Clear the field or enter 0 to remove the shipping charge. Cancel keeps the saved amount. Shipping follows the same editing rules as Edit Details: it is unavailable while the order is On Hold, Disputed, Completed, or Cancelled. Tax, totals and landed costs follow your existing settings. Use Add cost / discount for other charges. [Image: Shipping cost dialog showing the order currency, amount, Cancel, and Save shipping cost] (/_astro/14-shipping-cost.CcwK26qS_gcCna.webp) Change shipping directly from Financial Summary. ## When to use one - Replenishing stock from your supplier. - Recording an order you’ve already placed elsewhere (manual creation; Mark as Sent (Manual) without emailing). - Generating supplier-facing documentation (the PO PDF). - Recording full or partial receipts as stock arrives over one or more deliveries. ## What you can do here [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/) The 11 statuses, what changes at each transition, the mutability matrix. [Search, filters & saved views] (/features/supply-orders/purchase-orders/search-and-filters/) Search the list, filter by status/supplier/destination/payment/date, and save shop-wide presets. [Creating a PO] (/features/supply-orders/purchase-orders/creating/) All the ways to start a PO and what gets prefilled. [Dropship POs] (/features/supply-orders/purchase-orders/dropship/) Ship straight to a customer's address instead of a location, no Shopify inventory movement. [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) Have a second supplier take delivery and hold the goods as your stock. Elevate-plan feature. [The Orders tab] (/features/supply-orders/orders-tab/) Browse your Shopify orders, filter them, and start a PO, TO, or RMA from a selection. [Line items & costs] (/features/supply-orders/purchase-orders/line-items/) Per-line columns, bulk edit, metafields, constraint badges. [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/) Every way to put a row on a PO: picker, import, custom item, raw-materials split. [Sending the PO] (/features/supply-orders/purchase-orders/sending/) Send via Logistified or mark manually sent, plus confirmation. [Shipments] (/features/supply-orders/purchase-orders/shipments/) Track one or more physical deliveries: carrier, tracking, and which line items are in each. [Receiving stock] (/features/supply-orders/purchase-orders/receiving/) Full and partial receipts, inventory effects, discrepancies. [Payments & 'marked as paid'] (/features/supply-orders/purchase-orders/payments/) Recording payments and the operator-set paid flag. [Additional costs & discounts] (/features/supply-orders/purchase-orders/additional-costs/) Surcharges and discounts: fixed or percentage, any currency, each with its own purchase tax. [Documents] (/features/supply-orders/purchase-orders/documents/) Uploading and downloading PO-related files. [Exports] (/features/supply-orders/purchase-orders/exports/) CSV, XLSX, PDF, and label sheets, all template-driven. [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/) Configure MOQ, pack size, Product MOQ, capacity, group, and ratio rules. Elevate-plan feature. [Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/) Build additive Fill gaps plans against your configured rules. Elevate-plan feature. [Applying supplier credits] (/features/supply-orders/purchase-orders/credits/) Use a supplier credit against a new PO. [Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/) Push a bill to Xero, read its sync status, and fix common errors. [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/) What fires automatically when you act on a PO. [Preferences] (/features/supply-orders/purchase-orders/preferences/) Runtime toggles that change how POs behave day-to-day. [Settings] (/features/supply-orders/purchase-orders/settings/) Where every PO-related setting lives. ## Key concepts - [Purchase order] (/reference/glossary/#purchase-order): the artifact itself. - [Line item] (/reference/glossary/#line-item): one variant on the PO. - [Ordered] (/reference/glossary/#ordered-quantity), [confirmed] (/reference/glossary/#confirmed-quantity),[received] (/reference/glossary/#received-quantity) , [pending] (/reference/glossary/#pending-quantity) quantity: four ways to count units across the lifecycle. - [Originating forecast view] (/reference/glossary/#originating-forecast-view): the saved view a PO was created from. - [Archived] (/reference/glossary/#soft-delete): a PO removed from the active list but kept for audit. - [Constraint Studio] (/reference/glossary/#constraint-studio): Elevate-plan editor for PO rules. - [Constraint optimizer] (/reference/glossary/#constraint-optimizer): Elevate-plan tool that proposes additive quantity changes. - [Supplier credit] (/reference/glossary/#supplier-credit): a balance with the supplier, applicable to future POs. ## Where to next - [Guides → Create a purchase order] (/guides/create-a-purchase-order/): end-to-end walkthrough. - [Forecast → Creating a PO from the forecast] (/features/forecast/create-po-from-forecast/): turn selected reorder rows into draft POs. - [Guides → Configure purchase-order constraints] (/guides/configure-purchase-order-constraints/): Product MOQ and CBM examples. - [Guides → Receive inventory] (/guides/receive-inventory/): the full and partial receipt flow. - [Forecast → Reorder suggestions] (/features/forecast/reorder-suggestions/): how the suggested quantities are built. - [Suppliers → Supplier–variant mapping] (/features/suppliers/supplier-variant-mapping/): the supplier links, cost, MOQ, and primary supplier data that PO creation can use. - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): fix drift between expected incoming and Shopify’s incoming counter. - [Reports → Purchase Order Report] (/features/reports/report-types/#purchase-order-report): scheduled summaries for overdue and arriving POs. - [Purchase Orders → Preferences] (/features/supply-orders/purchase-orders/preferences/) and [Settings] (/features/supply-orders/purchase-orders/settings/): runtime toggles and configuration pages. - [Settings → Accounting] (/features/settings/accounting/): connect Xero to sync bills automatically. Last updated: 27 October 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/lifecycle/ # Lifecycle & statuses The 11 purchase order statuses, what changes at each transition, and what you can edit at each stage. In Logistified, a purchase order moves through up to 11 statuses. Each transition can stamp a date, apply or remove product tags (if you’ve configured them), push to Shopify, and queue an email. This page is the canonical reference for what changes when. ## On this page - The 11 statuses - Status flow - What each transition does - What you can edit at each status - Going backwards (undo & Reopen) - Merging POs - Deleting a PO - See also ## The 11 statuses Status What it means Typical entry Draft You’re composing the PO. No supplier-side effect yet. New PO created. Sent The PO is submitted to the supplier. You click Send to Supplier or Mark as Sent (Manual). [Partially Confirmed] (/reference/glossary/#confirmed-quantity) The supplier confirmed some lines, not all. First per-line confirmation. Confirmed All lines confirmed. The last line flips to confirmed. In Progress The supplier is fulfilling. Manual click, Quick Confirm (confirms every line and jumps straight here), or first receipt. Partially Received At least one line received; others outstanding. First receipt. Received Every line fully received. Last receipt. Completed Closed; no further activity expected. You mark done after receipt + payment. On Hold Paused, usually for a dispute or finance hold. Manual. Disputed A formal dispute is open. Manual. Cancelled Order cancelled. Manual. ## Status flow The happy path runs top to bottom: ``` Draft │ Send to Supplier / Mark as Sent (Manual) ▼ Sent │ per-line confirmation (Quick Confirm skips ahead to In Progress) ▼ Partially Confirmed │ last line confirmed ▼ Confirmed │ start shipping ▼ In Progress │ first receipt ▼ Partially Received │ last receipt ▼ Received │ operator-marked done ▼ Completed ▲ │ Reopen Order │ (lands in Received / Partially Received / │ In Progress depending on what was received) └──── (return to flow) ``` Side states can be entered from most in-flight statuses (Sent, Confirmed, In Progress) and exit back into the flow or to Cancelled: ``` [in-flight PO] ────► On Hold ◄────► Disputed │ │ │ │ │ ▼ └────────────────┴────────► Cancelled ``` The straight arrows are the normal happy-path transitions. Side-state arrows are operator-initiated; Resume Processing brings an On Hold or Disputed PO back to the previous in-flow status it came from. Reopen Order is the way to walk a Completed (or Cancelled) PO back into the receive flow. ## What each transition does This is the side-effects matrix. The [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/) page has the full prose explanation; here’s the at-a-glance table. To Date stamped Tag effect Shopify “incoming” Email Log Sent Sent date tag applied (if a tag is configured to fire on Sent) pushed as ordered quantity, only if incoming tracking is on supplier email queued (or none, if you chose “Mark as Sent (Manual)”) yes Partially Confirmed Not applicable (depends on your tag config) re-synced to confirmed − received − cancelled − rejected none yes Confirmed Confirmed date (depends on your tag config) re-synced to confirmed − received − cancelled − rejected none yes In Progress In-progress date; shipping date auto-set if missing (depends) unchanged unless line quantities change none yes Partially Received Not applicable (depends) local receipt saved; Shopify incoming is reconciled when sync runs none yes Received Received date (depends) once synced, pending incoming for fully received lines is cleared none yes Completed Closed date tag removed (if a tag is configured to remove on Completed) unchanged none yes Cancelled Cancelled date (depends on your tag config) rolled back to zero for this PO none yes On Hold On-hold date unchanged unchanged none yes Disputed Disputed date unchanged unchanged none yes Resumed (off On Hold) Not applicable (depends on returning status) (depends) none yes Reopen Order (from Completed) Not applicable (depends; tag may be re-applied if your config covers the new status) re-pushed for any outstanding pending units none yes Note Tag triggers are operator-configured, not hard-coded. The Sent / Completed / Cancelled rows above show the typical default config; your shop may have apply / remove on different statuses. See [Settings → Product tags on transition] (/features/supply-orders/purchase-orders/settings/#product-tags-on-transition). Note When [Incoming inventory tracking] (/features/supply-orders/purchase-orders/preferences/#incoming-inventory-tracking) is on (it is off by default), Shopify’s “incoming” inventory starts populating as soon as a PO becomes Sent (using the ordered quantity). Confirmation and receipt activity tell Logistified what should remain incoming, but Shopify reflects the receive-side change when a sync runs. Your Shopify storefront sees “available” change accordingly after that sync. The exact behavior depends on the [Incoming Inventory and Auto-sync] (/features/supply-orders/purchase-orders/preferences/) preferences. Note If a PO’s shipping date passes while it’s still Draft, Sent, Partially Confirmed, or Confirmed, the order information card shows a red “Overdue shipment” badge below the Shipping Date. The badge clears once the PO reaches In Progress (where the shipping date is auto-set if it was never filled in) or any later status, and it never shows on On Hold, Disputed, or Cancelled POs. ## What you can edit at each status Each quantity column has a status window where it’s editable; there isn’t a single “everything locks after Draft” verdict. The matrix below shows which quantity column is in play at each status. Status Ordered qty Confirmed qty Received qty Cancelled / rejected qty Unit cost Add / remove lines Draft editable n/a n/a n/a editable editable Sent editable via the confirmation dialog n/a n/a editable editable Partially Confirmed editable confirmation dialog or Bulk Edit n/a n/a editable editable Confirmed editable Bulk Edit n/a locked editable editable In Progress / Partially Received editable Bulk Edit editable (receive dialog or Bulk Edit) editable (Bulk Edit) editable editable Received editable Bulk Edit editable for receipt corrections editable (Bulk Edit) editable editable On Hold / Disputed editable Bulk Edit locked locked editable editable Completed read-only read-only read-only read-only read-only read-only Cancelled read-only read-only read-only read-only read-only read-only Ordered quantity and unit cost are not frozen when a PO is sent; they stay editable until the PO is Completed or Cancelled. The confirmed-quantity column is locked outright when the [Auto-confirm quantities] (/features/supply-orders/purchase-orders/preferences/#auto-confirm-quantities) preference is on, because Logistified keeps confirmed equal to ordered for you. If you use the Logistified API, you can correct a line’s plain ordered quantity or unit cost on any open PO, including one that has received goods, without first unreceiving it. The quantity can never be lower than goods already received, rejected, or cancelled. For these API line edits, currency, original-cost, and explicit line-discount fields still require a Draft PO; changing a plain unit cost removes that line’s discount. To enable inline editing on a line-items table, click the Bulk Edit button (top-right of the table). See [Line items & costs → Editing inline] (/features/supply-orders/purchase-orders/line-items/#editing-inline-bulk-edit) for the details. Note Three surfaces stay editable even on Completed and Cancelled POs: the [Documents] (/features/supply-orders/purchase-orders/documents/) card, [supplier instructions] (/features/supply-orders/purchase-orders/sending/#supplier-instructions), and the [Payments] (/features/supply-orders/purchase-orders/payments/) card; you can still add, edit or delete payments and tick “Mark as fully paid” on a closed PO. Everything in the table above is locked once a PO is terminal. ## Going backwards (undo & Reopen) Walking back to a previous status is supported in a few specific ways: - Revert actions: the Actions menu offers Revert to Draft (from Sent), Revert to Sent (from Confirmed), and Revert to Confirmed (from In Progress). Each resets the work the forward step recorded (confirmations, tracking) and asks you to confirm first. The status stepper at the top of the page is a read-only progress indicator; it isn’t clickable. - Reopen Order: from Completed, the Reopen Order action returns the PO to one of Received, Partially Received, or In Progress. Logistified picks the right target automatically based on what has actually been received: fully received → Received; some lines received → Partially Received; otherwise → In Progress. After reopening, you can record more receipts or push remaining incoming back to Shopify. Reopen Order is also offered on a Cancelled PO: it restores the order to the status it was cancelled from (falling back to Received / Partially Received / Sent based on what was received) and re-adds the incoming quantity. - Resume Processing: from On Hold or Disputed, this returns the PO to the previous in-flow status it had before the hold or dispute. Receipt corrections are supported while the PO is still Received or otherwise in the receiving flow. Use Receive for additional arrivals, Unreceive where available for reversals, or Bulk Edit to correct the received quantity. Once a PO is Completed or Cancelled, receiving and line data are locked (documents, supplier instructions, and payments remain editable; see [What you can edit at each status] (#what-you-can-edit-at-each-status)). ## Merging POs You can merge POs while they are still before receipt: Draft, Sent, Partially Confirmed, Confirmed, and In Progress. POs that are Partially Received, Received, Completed, or Cancelled are blocked from merge. All merged POs must also have the same status, and lines with actual stock movement (received quantity, posted receipts, Shopify on-hand sync, or Assemblified sync) cannot be moved. Lines that have only pushed incoming quantity to Shopify can still be merged; Logistified refreshes Shopify incoming for the affected POs after the merge. All selected POs must use the same supplier and location. You choose one target PO, and Logistified moves the source lines into it. [Dropship POs] (/features/supply-orders/purchase-orders/dropship/) can never be merged (each one ships to a different customer’s address), and neither can POs [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/), since merging would change who holds the goods. Merge is only offered for POs at a real location. If the target already has the same variant with matching commercial, supplier, fulfillment, and date fields, the quantities are combined into the existing target line rather than creating a duplicate row. If those fields differ, Logistified shows you the differing values side by side and asks you to resolve them before the merge goes through: pick one occurrence to supply the combined line’s shared values (quantities are summed), or keep the occurrences as separate lines on the target PO. Quantities, metafields, reservations, and delivery schedules are preserved either way. Custom items stay on their original source PO because they are one-off PO-scoped lines. Note Delivery schedules follow their own rule during a merge: they only consolidate onto one line when every schedule detail matches across occurrences. Otherwise each occurrence’s schedules stay separate regardless of which values you pick for the combined line. When a source PO has no lines left after its movable lines leave, Draft sources are deleted. Non-Draft sources are cancelled and archived so the audit trail stays available. Note If a merge touches POs that already affected Shopify incoming, Logistified recalculates incoming for the source and target POs. If a Shopify sync is already in progress, wait for it to finish before merging. ## Deleting a PO - Draft: hard delete. Gone from history. - Cancelled: [archived] (/reference/glossary/#soft-delete). Stays in the database for audit but is removed from the active PO list. - Other statuses: cancel the PO first in the normal workflow so the audit trail remains clear. Cancel is offered from Sent, Partially Confirmed, Confirmed, In Progress, Partially Received, On Hold, and Disputed. A Received PO cannot be cancelled directly (move it back to Partially Received or In Progress first), and a Completed PO has to be reopened before it can be cancelled. Caution The status actions trust you. Nothing validates “did the supplier actually confirm?” before you move the PO to Confirmed. Be careful not to mark a PO as Received before you’ve actually received it, and remember that Reopen Order is available if you want to come back. ## See also - [Dropship POs] (/features/supply-orders/purchase-orders/dropship/): the same lifecycle, shipped to a customer instead of a location. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): the same lifecycle, received and held at a second supplier. - [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): the full prose of what fires when. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): what the mutability matrix protects. - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): the receipt-driven transitions. - [Preferences] (/features/supply-orders/purchase-orders/preferences/): toggles that change how incoming and Shopify sync behave. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries, and how they behave in a merge. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/search-and-filters/ # Search and filter purchase orders Search the purchase order list, add filters, and save named filter sets that the whole shop can reuse. Logistified’s purchase order list has a search box, a set of filters, and named presets that save a filter set (including the search term) for everyone in the shop to reuse. ## On this page - Searching the list - AI search - Deep search - Adding and editing filters - Available filters - Saving a filter set as a preset - Setting a shop default - Renaming and deleting presets - Edge cases & current behavior ## Searching the list Type into the search box to match against the PO name, ID, supplier, SKU, reference, or supplier instructions. The list updates shortly after you stop typing; clearing the box (the × inside it) updates immediately. The search term is shareable; it’s reflected in the page’s URL, so a bookmarked or copied link reproduces the same search. If the normal search can’t find what you’re after, use Deep search beside the search box; see below. ## AI search Instead of building filters by hand, you can describe the orders you want. Click into the search box and press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English and press Enter. A preview shows the filters it understood (status, supplier, destination, created by, payment status, tags and a date period on a date you name), and nothing changes until you click Apply. For example: - “unpaid draft or sent POs from Acme going to Berlin, created last month” - “urgent unpaid orders from Kessler” The applied filters are ordinary chips you can edit or save as a preset. If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/) for how to write requests, review the preview, and what it doesn’t handle yet. ## Deep search Deep search looks in the places the list search never touches. Click it next to the search box and the Search all purchase order data dialog opens: “Find references across orders, products, documents, shipping, invoices, payments, and optional manual comments.” - Search term: a PO number, SKU, tracking number, invoice number, and so on. Three characters minimum (two for a purely numeric term), and one pass looks at up to 200 matching orders. - Also search comments: off by default. Ticking it additionally reads the manual comments on each order’s Notes & Activity Log. That’s slower, so it runs with a Checked N of M progress bar you can stop at any time, and it’s limited to the 1,000 most recent matching orders (the dialog says when it’s capping). Results found before you cancel are kept. - Use current list filters: shown only when the list already has filters, and ticked by default. It scopes the search to the current status, supplier, payment, and date filters. Results come back as a table of Purchase order, Supplier, Status, and Matched in, with the matching text quoted underneath and your term highlighted inside it. Matched in names the area that matched (PO number, PO name, Supplier reference, SKU, Barcode, Product, Supplier instructions, Document, Tracking number, Carrier, Invoice number, Payment notes, Comment, and more) with a “+N areas” badge when an order matched in several places. Orders whose number or name match the term exactly are ranked first, then partial matches on those, then product, supplier-instruction, document, shipping, and payment matches. Click the arrow on any row to open that order. ## Adding and editing filters Click + Filter to open the filter picker: choose a field, then set its value. Each active filter appears as a chip below the toolbar; click a chip to edit it, or the × on the chip to remove it. Clear all removes every filter and the search term in one step. ## Available filters - Status: one or more PO statuses (Draft, Sent, Partially Confirmed, Confirmed, In Progress, Partially Received, Received, Completed, On Hold, Disputed, Cancelled). - Supplier: one or more suppliers. - Destination: one or more Shopify locations, plus two pinned entries for the orders that have no location of their own: Dropship, matching every [dropship PO] (/features/supply-orders/purchase-orders/dropship/), and At supplier, matching every PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/). Both pinned entries work on any plan, so you can always find these orders even if your plan no longer lets you create them. - Created by: one or more of the people who have created purchase orders in your shop. The list is built from the orders themselves, so it only offers names that actually appear on one. The purchase order list also has a Created by column; orders created before this was recorded show a dash. - Payment status: Paid or Unpaid. See [Payments] (/features/supply-orders/purchase-orders/payments/) for how a PO’s paid status is determined. - Date: a date range, with quick choices for Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month, alongside custom from/to dates. Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. ## Saving a filter set as a preset Once your filters or search term differ from whatever preset is currently active (or from All, the unfiltered default), a Save button appears next to the filter bar: - Save overwrites the currently active preset with your current filters and search term. - Save as… prompts for a name and creates a new preset, which becomes the active one. A preset saves the whole query: every active filter and the search box’s contents. Selecting a preset later applies both; selecting All clears both. Note Presets are shared by the whole shop, not private to your account. Anyone who saves, renames, stars, or deletes a preset changes it for every staff account viewing the purchase order list. ## Setting a shop default Open the preset switcher and use the star action on a preset to make it the shop’s default. The starred preset’s filters and search term are applied automatically the next time anyone opens the purchase order list with a plain, unfiltered link; a link that already carries filters or a search term (a bookmark, a shared link) always takes priority over the default. Only one preset per shop can be starred at a time; starring a different one clears the previous default. ## Renaming and deleting presets Both actions are available from the preset switcher. Deleting the preset you currently have selected drops the switcher back to All, but leaves your current filters and search term exactly as they were; only the saved preset itself is gone. ## Edge cases & current behavior - A shared link can name a preset that’s since been deleted. The link still applies whatever filters and search term it carried; the switcher just falls back to showing All since the preset it pointed at no longer exists. - The purchase order list no longer supports the older, browser-only “Save Filters” default. Filter presets are now saved to the shop, not to your browser, so they’re the same for you on any device and for every other operator. The [Supply Orders → Orders tab] (/features/supply-orders/orders-tab/#save-filters) still uses that older browser-local mechanism, so a Save Filters button there behaves differently from the presets described on this page. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/creating/ # Creating a PO Every way to start a purchase order and what gets prefilled when you do. Logistified has several distinct entry points for starting a purchase order. Each one prefills a different amount of information based on where the signal came from. Pick the one that fits how you decided what to buy. ## On this page - Creation paths - The min/max creation flow - What gets prefilled - Expected Shipping Date - Addresses on a new order - Sales-orders wizard: choosing a destination - Multi-supplier selection - Custom items (variants not yet in Shopify) - Importing from Stocky - Operator preferences that affect creation - See also ## Creation paths Path Where it starts Prefilled From the Forecast page Select rows on the Forecast page → Actions → Create PO. Quantities from the displayed [Reorder Forecast] (/reference/glossary/#reorder-quantity) (including EOQ uplift where shown), unit cost where available, MOQ + pack size info, originating forecast view. You choose a supplier or leave supplier blank to review supplier grouping. From Forecast (in-app) Supply Orders → Purchase Orders → Create Purchase Order → Create from Forecast. A supplier (required; the run is limited to its variants) and a location, then either a saved forecast view used as-is or a one-off forecast configuration (model, history period, lead time, variant filters). Logistified runs the forecast itself and orders each variant’s Reorder Forecast; note this path does not apply the EOQ uplift the Forecast page shows. The view it ran is stamped on the PO. From Min/Max Supply Orders → Purchase Orders → Create Purchase Order → Create from Min/Max. Variants at or below their [Reorder Point] (/reference/glossary/#reorder-point) or [Min Inventory] (/reference/glossary/#min-inventory) (counting incoming stock on open POs) with quantities to refill toward [Max Inventory] (/reference/glossary/#max-inventory) or [Target Inventory] (/reference/glossary/#target-inventory). Supports variant filters, an editable preview with per-line removal, and an optional back-order split. See [The min/max creation flow] (#the-minmax-creation-flow) below. From Sales History Supply Orders → Purchase Orders → Create Purchase Order → Create from Sales History. A supplier is required, and the run covers only that supplier’s linked variants. Each quantity is the units sold in the window you pick; no MOQ or pack-size rounding is applied here. You can restrict the sales to the PO’s location and optionally include zero-sales items at quantity 0. From Sales Orders Supply Orders → Purchase Orders → Create Purchase Order → Create from Customer Orders, or Supply Orders → Orders → select orders → Actions → Create PO from selected orders, which opens the same wizard with those orders already picked. The order picker lists every synced Shopify order; there is no unfulfilled-only filter. Variants on selected orders, quantities aggregated. You then choose a destination: a new PO, an existing Draft PO, or a multi-supplier split. See below. Manually (blank) Supply Orders → Purchase Orders → Create Purchase Order → Create Empty PO. A blank Draft PO. You can start without a supplier, but pick a real supplier before you rely on supplier email, supplier defaults, supplier currency, supplier-specific pickers, or supplier-credit workflows. From CSV / XLSX import Supply Orders → Purchase Orders → Create Purchase Order → Import from CSV/XLSX. Bulk upload through the unified import parser. All line items from the file, mapped to variants by SKU / barcode. Optional Original Unit Cost, Discount Type, and Discount Value columns carry [line discounts] (/features/supply-orders/purchase-orders/line-items/#line-discounts) in with the file. From Stocky import Supply Orders → Purchase Orders → Create Purchase Order → Import from Stocky. Stocky-format file mapped to Logistified PO fields. Rows are matched to existing variants: Shopify ID first, then SKU; unmatched rows can optionally be imported as custom items. See [Importing from Stocky] (#importing-from-stocky) below. Tip Every path above creates a purchase order; a file that repeats a PO number starts a second order rather than changing the first. To push new delivery dates, quantities, costs or shipping details onto orders you already have, use [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/) instead. The Forecast path is the most common; it’s what most operators use day-to-day. The Sales-orders wizard is the most powerful for inbound-demand-driven replenishment. Tip Every path above can also create a dropship PO, one that ships straight to a customer’s address instead of one of your locations. Marking delivered doesn’t change Shopify inventory; optional Compensate Inventory can offset stock deducted by Shopify fulfillment. Pick Dropship wherever you’d otherwise pick a location. See [Dropship POs] (/features/supply-orders/purchase-orders/dropship/). Tip On the Elevate plan, Create Empty PO offers a third destination: Deliver to a supplier (held as your stock): a second supplier takes delivery and holds the goods for you until a supplier stock release brings them into a warehouse. It’s offered there and when editing a Draft order’s destination, not on the other creation paths. See [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/). Tip For a complete tour of how to put rows onto an existing PO (picker, custom items, raw-materials split, imports) see [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/). Tip Whichever destination you pick in the sales-orders wizard (a new PO, an existing PO, or a supplier split) a Linked sales orders banner appears on the PO detail page listing every Shopify order the PO was sourced from. In a supplier split, each PO lists the orders whose items it carries. Click any order chip to open it in Shopify, or hover to preview the order’s status, payment, and total. ## The min/max creation flow Create from Min/Max walks through three steps: Supplier, Location & Details, and Min/Max Settings, then calculates a preview before anything is created. - Supplier (optional): pick a supplier to limit the run to its linked variants and pull unit cost, supplier SKU, lead time, [MOQ] (/reference/glossary/#moq), and [pack size] (/reference/glossary/#pack-size) from the [supplier ↔ variant links] (/reference/glossary/#supplier-variant-link) (order quantities are rounded up to meet MOQ and pack size). Or choose Skip (all suppliers) to scan every variant; MOQ and pack size are then treated as 1, so nothing is rounded. - Location: trigger and refill thresholds are always read for the location you pick. If your shop has exactly one location, it’s selected automatically. - Trigger: which variants qualify: Below Reorder Point (the default) or Below Minimum Inventory. The comparison is At or below threshold (≤) by default, or Strictly below threshold (<). It counts on-hand stock plus outstanding incoming units on open purchase orders, so a shortfall an open PO already covers doesn’t trigger. - Refill: how high to top up: Up to Max Inventory (the default) or Up to Target Inventory. - Variant filters (optional): narrow the run by vendor, product type, tags, and more before previewing. A Location-Specific Inventory switch (on by default) decides whether on-hand and incoming quantities are counted at the selected location only, or across all locations combined. Trigger and refill thresholds still come from the selected location either way. With the switch off, the preview is badged Global inventory and its On hand / Incoming columns are relabeled (all locations). Note Min, max, target, and reorder point must be configured per variant and location; see [Variant constants] (/features/forecast/variant-constants/). If no variant at the selected location has the chosen threshold set, the dialog blocks the preview and offers a Configure thresholds shortcut to that settings page. Preview shows up to two tables: in Split Into Back Orders mode, Will be ordered is replaced by separate Main PO and Back Order PO tables: - Will be ordered: one row per variant with available stock, incoming, the threshold, and the order quantity. Every row has a remove (trash) button; removed variants are left out of the created PO entirely. - Skipped. Already covered by open POs: variants below the trigger on available stock alone, whose shortfall existing open purchase orders already cover. Each row links to the covering PO(s). These rows are informational only; they aren’t part of the PO and can’t be removed. The PO only ever contains variants that were in the preview, with quantities (and the single/back-order split) recalculated against current stock at creation, so they can differ from what was previewed. An Order mode control decides how the order is written: - Single PO (the default): everything on one purchase order. - Split Into Back Orders: a main PO that refills stock from 0 up to your target/max, plus a separate [back-order] (/reference/glossary/#back-order) PO for the oversold portion (variants whose available stock is below 0, more units sold than you have) that brings available stock back up to 0. The back-order PO reuses your PO name with “(Back Order)” appended and the main PO’s number with “-1” appended. If everything you’re ordering is oversold, only the back-order PO is created (with a normal PO number); if nothing is oversold, you get a single PO. The create button tells you what you’ll get: Create 2 POs, or Create PO with the line count in brackets. Caveats: - Removals only apply to the current preview. Going back a step and previewing again restores every removed row. - Removing every row disables creation; run a new preview to start over. - In a split, if the main PO is created but the back-order PO fails, you’ll see a Back order PO not created warning; the main PO still exists, so only the back-order portion needs recreating. ## What gets prefilled For Create from Sales History, sales dates use your Shopify store’s timezone, shown beside the period controls. Last N days includes today in that timezone, and a custom range can cover a single day. Create keeps the preview’s dates if you confirm after midnight. Changing the sales settings requires a fresh preview, as does a changed store timezone detected by Logistified. If the timezone cannot be loaded, choose Retry; your supplier and order details are kept. When the PO opens after creation: - Supplier: set when you choose one, or set per PO when you use a split-by-supplier path. Forecast-created POs do not automatically choose a supplier just because selected rows have primary suppliers. - Currency: inherited from the chosen supplier. If there is no supplier yet, choose one before sending or using supplier-specific finance workflows. - Tax rate: inherited from the supplier’s default when a supplier is chosen; otherwise it uses your purchase default until you change it. - Payment terms: inherited from the supplier’s default when a supplier is chosen (for example “Net 30”). With no supplier (or a supplier that has none) it starts at No Payment Terms. - Carrier: not a purchase-order field at all. Carriers are recorded per shipment on the PO’s Payment & Delivery tab; see [Shipments] (/features/supply-orders/purchase-orders/shipments/). - Originating forecast view: stamped automatically when created from the Forecast page. - Line item quantities, cost, supplier SKU: from the supplier ↔ variant link when available. - Billing and delivery addresses: copied from the supplier’s default [address profiles] (/features/supply-orders/purchase-orders/settings/#address-profiles) when it has them. See [Addresses on a new order] (#addresses-on-a-new-order) below. Everything is editable while the PO is still Draft. ## Expected Shipping Date Every Create-Purchase-Order dialog (Create Empty PO, Create from Forecast (where it’s marked Optional), Create from Min/Max, Create from Sales History, and Create from Customer Orders) carries an Expected Shipping Date field for when the supplier is expected to ship. Filling it in at creation is worth the extra second: it becomes the order’s Shipping Date, and because the order hasn’t been sent yet, it also re-derives the payment Due Date from the supplier’s payment terms counted off that date (see [Payments → Due Date] (/features/supply-orders/purchase-orders/payments/#due-date-and-the-payment-due-badge)). It’s what the Overdue shipment badge on the detail page later measures against. You can always set or change it afterwards while the order is Draft. ## Addresses on a new order A purchase order carries its own billing address and delivery address, printed on the supplier-facing PDF and available as export columns. You don’t have to type them each time: - If the supplier has default [address profiles] (/features/supply-orders/purchase-orders/settings/#address-profiles) assigned, the new order starts with those addresses already copied in. (The delivery default applies to orders going to one of your locations; a dropship or deliver-to-supplier order takes its ship-to from the customer or the receiving supplier.) - On the order itself, Edit Billing Address and Edit Delivery Address offer a Copy from address profile picker, alongside the existing Copy from Shop Settings, Copy from Shopify Location, and Copy from Supplier shortcuts. Either way the order keeps its own copy of the address: later edits to the profile never rewrite orders that already exist, and you can freely adjust the address on one order without affecting the profile or any other order. ## Sales-orders wizard: choosing a destination After you pick orders and review the aggregated items, the wizard’s last step asks where those items should go: - Create a new purchase order: pick a supplier (optional) and a name, then create a fresh Draft PO for the items. - Add to an existing PO: search for and select a Draft PO at the same location. The items are always added as new lines; quantities are never merged into a line already on that PO. The source Shopify orders are linked to it alongside whatever was already linked. - Split across suppliers: items are auto-grouped by their recommended supplier, with a chance to reassign unassigned or misgrouped items first. By default each group creates its own new PO, but you can instead point a group at one of that supplier’s existing Draft POs; where a line for the same variant is already on that target you choose Combine (quantities added) or Replace (quantity overwritten). This is the only destination where quantities can merge into a line that already exists on the target PO. Each PO is linked only to the sales orders whose items it carries; an order none of whose items is in the wizard (for example, only custom items) is linked to every PO of the split. Only Draft POs at the matching location show up as “existing PO” targets. ### From the Shopify admin You can also open this wizard from your Shopify admin: - One order: on the order’s page, choose More actions → Create purchase order. - Several orders: on the Orders list, tick the orders, then choose … → Create purchase order (under Apps). Logistified opens with those orders’ items already in the wizard, so you only choose the destination and the supplier. See [The Orders tab → From the Shopify admin] (/features/supply-orders/orders-tab/#from-the-shopify-admin) for what happens when an order hasn’t reached Logistified yet. ## Multi-supplier selection When the rows you select span multiple primary suppliers (common in the Forecast and the Sales Orders wizard) the safest path is to split into one PO per supplier. In the Forecast dialog, choosing one supplier creates a single PO using that supplier and its defaults. Treat that as a supplier choice, not a strict supplier filter: review the line items before sending, especially if the selected rows originally pointed to different suppliers. The split path creates the supplier-specific POs in one operation. Each PO gets stamped with the same origin (forecast view or sales-order batch). Assemblified sub-assembly items (SKUs starting with ASM-) are ordered like any item once they are mapped to the PO’s supplier. A sub-assembly the forecast would order but no supplier is mapped to is left off, and the dialog names it so you can map it in Suppliers. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#purchasing-sub-assemblies). ## Custom items (variants not yet in Shopify) You can add a line for a product that doesn’t yet exist as a Shopify variant, a [custom item] (/reference/glossary/#custom-item). Once the PO reaches In Progress (and while it is Partially Received, Received, or Completed) each custom-item line gets an Add as product to Shopify action that creates a real Shopify product (as a Draft product) and attaches the reference to the line. The PO line remains a custom-item line with that Shopify reference attached; it is not identical to a normal Shopify-linked line. Used when you’re ordering something you haven’t yet decided to sell, or a one-off batch. See [Adding line items → Custom items] (/features/supply-orders/purchase-orders/adding-line-items/#custom-items). ## Importing from Stocky Import from Stocky reads your Stocky purchase items report (CSV/XLSX). Multiple POs in one file are grouped automatically, and suppliers and locations are auto-matched where possible. Each row is matched to a variant in your Logistified catalog, first by the file’s Shopify ID column, then by SKU. Because the Shopify ID is tried first, a row with no SKU at all can still match; such rows show the ID as #12345… in the preview’s SKU column. A Shopify ID cell that is blank, 0, or mangled by Excel into scientific notation (e.g. 4.94515E+13) is treated as missing, and the row falls back to SKU matching. Rows with no identifier at all (no SKU, no Shopify ID, and no product or variant title) are dropped, as are rows whose quantity is zero or negative and rows that fail validation (a missing Purchase Order value, for example); the preview notes how many rows were skipped and why. Rows that resolve to the same variant are merged, with their quantities summed. The preview’s summary bar counts the matched items; when at least one row matched by Shopify ID, hovering the items matched badge shows the Shopify-ID vs. SKU split. If any rows match nothing, a second badge counts them (“unmatched (will be skipped)” or “unidentified → custom items”, depending on the checkbox below) next to a Remove all unmatched button (each expanded PO also has its own Remove unmatched). Every line’s status icon has a tooltip explaining how that line matched. When at least one row matches no variant, a Create unidentified items as custom items checkbox appears under the summary. It’s off by default: unidentified rows are simply skipped and the import proceeds without them. Tick it, and those rows are imported as [custom items] (/reference/glossary/#custom-item) instead; title, SKU, and cost come straight from the file. The Cost origin selector doesn’t apply to these lines: even with Shopify / Supplier selected, custom items always take the file’s cost, since there’s nothing else to fall back to. When custom items were created, the result screen adds a Custom Items tile counting them. Custom items created this way work like custom items added by hand (see [Custom items] (#custom-items-variants-not-yet-in-shopify) above) with one difference: they land in whatever status the imported PO carries, so a delivered Stocky PO arrives with its custom items already Received. Each PO in the preview has its own editable Name, Location, Supplier and Status, with Set all statuses / suppliers / locations controls above the list. The status is prefilled from the file: every line received → Received, some → Partially Received, otherwise Draft. A PO whose status is anything other than Draft must have both a supplier and a location; otherwise it is dropped from the run and the footer warns that those non-draft POs “need a supplier and delivery target”. Draft POs missing those details still import, with a softer reminder to fill them in before sending. Partially Received is also rejected when nothing (use In Progress) or everything (use Received) in the file is marked received. Note Matching runs against Logistified’s synced copy of your catalog, so a variant created in Shopify moments before the import may not match until it has synced. If the variant lookup itself fails, the preview shows a “Variant lookup failed” alert and disables the import until you click Retry lookup and it succeeds. ## Operator preferences that affect creation These defaults live elsewhere in the app; this is the reference for what gets used at PO creation. Preference Where set What it does Default payment terms Suppliers → Supplier detail. Stamped on the PO header. Editable per PO. Default currency Suppliers → Supplier detail. Inherited at creation. Default tax rate Settings → Tax Rates, then linked from the supplier row. Inherited at creation. Carrier list Settings → Carriers. Fills the carrier picker on a PO’s shipments. Supplier–variant link Suppliers → Supplier detail → Variants tab. Drives MOQ, pack size, lead time, unit cost at creation. Originating forecast view Forecast page state at creation time. Stamped automatically for audit. Note If your supplier’s defaults are wrong, fix them on the supplier row first. New POs inherit the corrected values; existing POs need to be edited individually. Caution Supplier and location can only be edited while the PO is in Draft. If you picked the wrong supplier on a PO you’ve already sent, use Actions → Revert to Draft, change it, and send again; you don’t have to cancel or recreate the order. ## See also - [Dropship POs] (/features/supply-orders/purchase-orders/dropship/): shipping straight to a customer’s address instead of a location. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): having a second supplier take delivery and hold the goods for you. - [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/): every way to add a row, including the Assemblified raw-materials split. - [Forecast → Creating a PO from the forecast] (/features/forecast/create-po-from-forecast/): the Forecast-side cross-link. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): what happens after Draft. - [Settings] (/features/supply-orders/purchase-orders/settings/): all the operator preferences. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/dropship/ # Dropship purchase orders Create a purchase order that ships straight to a customer's address instead of one of your locations, with optional inventory compensation. In Logistified, a dropship purchase order ships directly from your supplier to a customer’s address instead of to one of your own locations. Use it whenever a supplier fulfills a customer order on your behalf. The order runs through the same statuses as any other PO, but it never adds stock to your warehouse. Shopify inventory changes only if you choose Compensate Inventory to offset stock deducted when the customer’s order was fulfilled. ## On this page - What makes a PO a dropship PO - Creating a dropship PO - Delivery details from a Shopify order - The customer delivery address - Where dropship POs show up - Sending and marking delivered - What never touches inventory - Compensating Shopify inventory - Exports - Merging, splitting, and returns - Limits - See also ## What makes a PO a dropship PO Every purchase order has a destination: one of your Shopify locations, Dropship (customer address), or (on the Elevate plan) [another supplier who holds the goods for you] (/features/supply-orders/purchase-orders/deliver-to-supplier/). You choose between them on the same picker you’d use to pick a location; Dropship is always offered as an extra option alongside your real locations. A dropship PO carries a customer shipping address instead of a location. Its line items are never counted as warehouse stock, so it behaves like a normal order for tracking and paying a supplier, but like a pass-through for inventory purposes. ## Creating a dropship PO The destination picker is available everywhere you can create or edit a PO: - Create Empty PO, Create from Forecast, Create from Min/Max, and Create from Sales History all let you pick Dropship instead of a location. When you pick it in one of the replenishment flows, thresholds and quantities fall back to shop-wide values. Per-location min/max overrides don’t apply to a dropship order, since there’s no location to read them from. - Create from Customer Orders (the sales-orders wizard, and its shortcut from the Orders list) creates one dropship PO per customer order, carrying that order’s items. Choose Dropship (customer’s order address) in the destination picker. The PO doesn’t copy the customer’s address: it reads the name and delivery address from the Shopify order whenever its PDF is generated (see [Delivery details from a Shopify order] (#delivery-details-from-a-shopify-order)), so the review step lists order names only. Each order gets its own PO; there’s no option to combine several orders into one dropship PO. Orders mirrored from a [connected store] (/features/settings/multi-store/) can’t be used here: the wizard names them and asks you to remove them or pick a location instead (create the dropship PO in the store that owns the order). Dropship destinations here always create brand-new POs; adding items to an existing PO isn’t offered for them. - Import from CSV/XLSX and Import from Stocky auto-detect a dropship shipment when the file’s row carries a deliverable customer address and no location resolves for it. Each detected group is counted as a dropship PO that “will ship to the imported customer address” in the preview, with a per-PO override if you’d rather assign it to a location (or vice versa). ## Delivery details from a Shopify order A dropship PO created from a Shopify customer order keeps no copy of the customer’s details. Instead, the Supplier & Location card shows: - Delivery address from Shopify order #1001 with a Dropship badge, - Read from Shopify when the PDF is generated., - a View order in Shopify link, and - an Enter address manually instead button. No customer name or address is shown anywhere in Logistified. Each time you download the PDF or email it to the supplier, Logistified reads the customer’s name and delivery address (never their email or phone number) from the order in Shopify at that moment, so the PDF always carries the order’s current address. The PDF preview in the export dialog shows a placeholder (Delivery address from Shopify order #1001. Read from Shopify when the PDF is generated.) instead of the address. Enter address manually instead replaces the Shopify order with an address you type, in the usual address dialog (titled Enter Delivery Address Manually). From then on the PO is an ordinary dropship PO with a stored address; later changes to the order in Shopify no longer apply. The button is available in every status except Completed and Cancelled, so you can still switch if the order’s address can’t be read after the PO was sent. While the PO reads from the order, that order stays linked: Manage linked orders shows it locked with Delivery address source: enter the address manually to unlink this order. [anchor: before-shopify-approves-access-to-customer-addresses] ### If the customer’s address can’t be read Logistified now has Shopify’s approval to read customer names and delivery addresses for these PDFs. No setting needs to be enabled in Logistified. If an address still can’t be read, the PDF isn’t generated and the email isn’t sent. The message explains whether the order was deleted, has no shipping address, or your Shopify staff account lacks access to its customer details. If Shopify denies the app access to the protected address fields, you may see: Shopify has not yet approved this app’s access to customer delivery addresses. Enter the address manually instead, or try again after approval. Use Enter address manually instead to send the order with an address you type, or resolve the access problem and try again. ### Sending, documents, and exports - Sending: Send via Logistified and Re-Send Email always attach a PDF (spreadsheet attachments aren’t offered), built at send time with the current address from Shopify. Logistified doesn’t keep a copy: the file exists only until the email is delivered, and Use existing attachment isn’t offered on Re-Send. Every resend builds a fresh PDF. If the address can’t be read, the email isn’t sent. A first send leaves the order in Draft; a failed resend leaves its status unchanged. See [Sending the PO] (/features/supply-orders/purchase-orders/sending/). - Documents: Attach printout to my documents is unavailable in the export dialog for these POs, because the printout carries the customer’s address. - Spreadsheet exports: the eight Delivery columns export blank. ### Protected data access in the Log Every PDF download and every email send of such a PO adds an entry to the Protected data access section of the PO’s Log card (on the Progress and All tabs): who it was, when, and Downloaded the PDF with the customer’s delivery address or Read the customer’s delivery address to email the PDF. The entries never show the customer’s details, and they can’t be edited or deleted. ## The customer delivery address This section is about dropship POs whose address is stored on the PO (typed in, imported, or entered with Enter address manually instead). The address is editable while the PO is in Draft. On the detail page, the location card shows the customer’s address and a Dropship badge in place of a location. If the address is missing, the card’s empty state reads No customer delivery address with an Add the customer’s delivery address so this order can be sent prompt, and an Add customer delivery address task tile appears right there in the Delivery Location column. Note Imports carry only the geographic fields: company, address lines, city, province, ZIP, and country. Contact person, phone, and email aren’t pulled in automatically, but you can add them by editing the delivery address on the PO; they then print on the PDF and export in the Delivery columns. Caution The destination (Dropship vs. a location) can only be changed while the PO is Draft, same as changing the supplier. Once sent, the destination is locked for the rest of the order’s life. ## Where dropship POs show up - PO list: a Dropship badge appears next to the order, and the location filter gains a pinned Dropship entry alongside your real locations. - Detail page: the location card shows the customer address and the Dropship badge instead of a Shopify location, and inventory columns show an explicit “not applicable” hint instead of blank cells, since there’s no location to read stock from. - Reporting and the supply-orders dashboard: wherever purchase orders are grouped by location, dropship orders get their own Dropship group, separate from [deliver-to-supplier orders] (/features/supply-orders/purchase-orders/deliver-to-supplier/) and from orders that simply have no location assigned yet. ## Sending and marking delivered Sending a dropship PO requires a deliverable customer address instead of a location; the Send to Supplier action is disabled with an Add the customer’s delivery address before sending message until one is set. A PO that reads its address from a Shopify order needs nothing more: the order is its destination. Once a dropship PO reaches In Progress, receiving is relabelled to match what’s actually happening. The supplier is shipping to your customer, not to you: - Receive Quantities becomes Mark Delivered, and Receive Manually becomes Mark Delivered Manually. - Quick Complete reads Mark every remaining quantity as delivered, with a note that marking delivered doesn’t update Shopify inventory. - The status stepper’s “Received” description reads All items have been delivered to the customer. Marking a dropship PO delivered works exactly like receiving any other PO (full or partial, one pass or several). It’s the same action with different labels and no Shopify inventory push. Note Dropship POs are left out of the list page’s Auto-receive bulk action (both Full and Partial receive); mark them delivered individually from the order’s own detail page instead. ## What never touches inventory Sending, confirming, marking delivered, and Quick Complete don’t change Shopify on-hand stock. Dropship POs are also excluded from: - Shopify incoming counts. - Forecast’s incoming-on-order figures. - Min/max reorder-point coverage (an open dropship PO is never counted as “already covers this shortfall”). - [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). Converting a custom item on a dropship PO into a real Shopify product stays blocked, since that action would activate inventory at a warehouse location rather than record a direct delivery to the customer. ## Compensating Shopify inventory Shopify may deduct stock at a location when you fulfill the customer’s order, even though your supplier shipped the goods directly. Use Compensate Inventory on the dropship PO to add the delivered quantities back at that location and offset the deduction. 1. Mark the quantities delivered on the PO. 2. Choose Compensate Inventory. 3. Choose the Shopify location whose stock was reduced. If the linked orders were fulfilled from a single location, it is suggested for you; otherwise, choose the location yourself. 4. Review the items and quantities, then confirm the compensation. Compensation is optional and always manual. Marking delivered and completing the PO never run it automatically. Only delivered quantities that haven’t already been compensated are available. The action changes on-hand stock, never Shopify incoming or forecast incoming-on-order figures. The compensation location is locked once any quantities have been compensated. Block sync to Shopify in Settings → Purchase Orders → Preferences also blocks compensation. You can compensate a Completed dropship PO, but you must reopen it to unreceive and reverse the compensation in Logistified; otherwise, correct it in Shopify. On a PO that still allows unreceiving, unreceiving compensated quantities reverses the corresponding inventory adjustment. ## Exports Bulk CSV/XLSX exports gain eight ship-to columns for the customer address: Delivery Company Name, Delivery Address 1, Delivery Address 2, Delivery City, Delivery Province, Delivery ZIP, Delivery Country, and Delivery Phone. They’re not in the default column set; add them from a [purchase-order or line-item export template] (/features/supply-orders/purchase-orders/exports/#custom-column-sets-and-export-templates) the same way you’d add any other column. These columns follow the same two-tier rule as the [PDF’s Delivery address block] (/features/supply-orders/purchase-orders/exports/#addresses-on-the-pdf): the PO’s own shipping address first, falling back to the Shopify location, so they’re correct for both dropship POs and warehouse POs that carry an address override. For a dropship PO that reads its address from a Shopify order they stay blank; the customer’s address never goes into a spreadsheet. ## Merging, splitting, and returns - Merging: two POs can’t be merged if either one is a dropship PO, since each dropship order ships to a different customer. This applies even between two dropship POs. [Deliver-to-supplier POs] (/features/supply-orders/purchase-orders/deliver-to-supplier/) are blocked from merging too, for their own reason. - Splitting or duplicating: the customer’s delivery address is copied along with the rest of the order, so a split dropship PO keeps its ship-to address on both halves. A PO that reads its address from a Shopify order keeps reading it from the same order on both halves. - Returns (RMAs): creating a return from a dropship PO uses the PO’s own customer address as the return’s origin, since that’s where the goods are physically coming back from; there’s no warehouse location to fall back to. A PO that reads its address from a Shopify order has no stored address to copy, so add the origin address on the return. ## Limits - Dropship destinations can only be set or changed while the PO is Draft. - Creating from customer orders always creates new POs, one per order; there’s no “add to an existing PO” option and no way to combine orders for a dropship destination. - Orders mirrored from a connected store, and imported or historical orders, can’t supply a dropship PO’s address from Shopify; create the dropship PO without the order and enter the address by hand. - Line handling on a dropship PO offers Ship to customer and Buy and hold at supplier; the warehouse options don’t apply, since there’s no location to deliver or consign to. - Custom items on a dropship PO can’t be converted into a real Shopify product. - Replenishment flows (Min/Max, Sales History) fall back to shop-wide thresholds for a dropship destination; per-location overrides don’t apply. ## See also - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): the rest of the creation paths this page’s destination picker slots into. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): the 11 statuses a dropship PO moves through, same as any other. - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): full detail on the receive flow that “Mark Delivered” reuses. - [Exports] (/features/supply-orders/purchase-orders/exports/): export templates and the PDF’s ship-to address rule. - [Return Orders (RMAs)] (/features/supply-orders/return-orders/overview/): creating a return from a delivered PO. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): the other location-less destination, where the goods do become your stock. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/deliver-to-supplier/ # Deliver to another supplier Buy from one supplier and have the goods delivered to a second supplier, who holds them as your stock until a supplier stock release brings them into a warehouse. [Elevate plan] (/reference/subscription-plans/) A Logistified purchase order normally arrives at one of your own locations. It can instead be delivered to another supplier, who receives the goods and holds them for you: you buy from Supplier A, Supplier B takes delivery, and the stock is yours from the moment you receive it; it just sits at B until you call it in. Use it for contract manufacturing, finishing, kitting, or pre-positioning, anywhere a second company handles your goods before they ever reach a warehouse of yours. ## On this page - What makes a PO a deliver-to-supplier PO - Creating one - The receiving supplier and its delivery address - Line items are always held at the supplier - Where these POs show up - Sending - Receiving at the supplier - Reversing a receipt - Getting the stock into a warehouse - What this does to your inventory numbers - Documents and exports - Merging, splitting, and returns - Limits ## What makes a PO a deliver-to-supplier PO Every purchase order has a destination. There are three kinds: Destination Where the goods go Whose stock it becomes One of your locations Your warehouse or store Yours, counted in Shopify at that location Dropship Your customer’s address Never yours: see [Dropship POs] (/features/supply-orders/purchase-orders/dropship/) Deliver to a supplier A second supplier’s address Yours, held at that supplier until you release it into a location You pick between them on the same destination picker you’d use to choose a location. Deliver to a supplier (held as your stock) appears there as a pinned entry alongside your real locations, with Another supplier receives and holds the goods for you underneath it. Note This destination needs the Elevate plan, because the goods land as supplier-held stock, an Elevate capability. On a lower plan the option isn’t offered, and switching an order onto it is refused. Orders you already have stay fully visible and workable: you can still find them, edit them, send them, receive them, and take the destination back off them. ## Creating one Open Supply Orders → Purchase Orders → Create Purchase Order → Create Empty PO, pick the supplier you’re buying from, then choose Deliver to a supplier (held as your stock) as the destination. A Receiving supplier block appears right below the picker; choose the supplier that will take delivery. You can also switch an existing order onto this destination while it’s still Draft: open the PO, edit its header, and pick the same entry. The receiving supplier block appears there too. Those two places are the only ones. The replenishment flows (Create from Forecast, Create from Min/Max, Create from Sales History), the customer-orders wizard, the CSV/XLSX and Stocky imports, and bulk actions from the Forecast page all keep the ordinary location-or-dropship picker; a deliver-to-supplier order started anywhere else is refused with a message pointing you back to the purchase orders list. Copying or splitting a deliver-to-supplier PO into a new order carries the destination, the receiving supplier, and the delivery address across, so the copy behaves like the original. ## The receiving supplier and its delivery address The Receiving supplier picker lists your suppliers, and the one you’re buying from stays in the list; buying from a supplier and having that same supplier hold the goods is a supported setup. Two entries are never selectable: the placeholder default-supplier row, and suppliers you’ve deleted. When you pick a receiving supplier, its address is copied onto the purchase order as the delivery address. From then on it belongs to the order; edit it on the PO if this shipment goes somewhere other than the supplier’s main address, and it stays as you left it. If the receiving supplier has no address on file, the dialog warns you up front, and the order’s destination panel shows No supplier delivery address with an Add the receiving supplier’s delivery address so this order can be sent prompt. The panel itself is headed Deliver to supplier rather than Delivery Location, and it names the receiving supplier with an At supplier badge. Caution The destination and the receiving supplier can only be set or changed while the PO is in Draft, the same rule that governs changing the supplier. Once the order is sent, both are locked for the rest of its life. ## Line items are always held at the supplier On an ordinary PO each line carries a [fulfillment mode] (/features/supply-orders/purchase-orders/line-items/#fulfillment-mode-per-line): deliver to warehouse, hold at supplier, or warehouse consignment. On a deliver-to-supplier PO every line is Held at supplier, and the per-line control is locked with the explanation “This order is delivered to a supplier, so every line is held at that supplier.” That’s the whole point of the destination: there is no warehouse on this order for a line to be delivered to, and consignment would mean the goods aren’t yours, which they are. ## Where these POs show up - PO list: an At supplier badge sits next to the order, and the Destination filter gains a pinned At supplier entry. Deliver-to-supplier orders have no location of their own, so that entry is the only way to filter them in. It stays available on every plan, so a shop that moves off Elevate can still find the orders it has. - Detail page: the destination panel names the receiving supplier and the delivery address instead of a location, and the per-location inventory columns read n/a rather than blank, since there’s no location to read stock at. - Reporting and the supply-orders dashboard: wherever purchase orders are grouped by location, these orders get their own At supplier group, separate from dropship orders and from orders that simply have no location assigned yet. - The receiving supplier’s page: once received, the stock appears under Suppliers → the receiving supplier → Variants → My stock at supplier, because that’s where it physically is. Each row links back to the purchase order that brought it in, which belongs to the supplier you bought from; that’s the provenance of the goods, not a mistake. A supplier that has never sold you anything can hold stock this way. ## Sending Send to Supplier needs both halves of the destination before it will run: - No receiving supplier yet → Choose the supplier that receives and holds the goods before sending. - No delivery address yet → Add the receiving supplier’s delivery address before sending. Both appear as tasks in the order’s destination panel, so you can fix them without hunting. The order goes to the supplier you’re buying from, as always; the receiving supplier isn’t emailed and doesn’t get a login. ## Receiving at the supplier The goods really do become yours on receipt, so the wording stays “receive”: it just says where: - Receive Quantities reads Receive at Supplier, and confirming reads Confirm Receiving at Supplier. The dialog explains that received quantities are recorded as your stock at the receiving supplier, not in Shopify. - Quick Complete receives every outstanding confirmed quantity and completes the order, with a Stock is recorded at the receiving supplier note explaining that the quantities are yours and a supplier stock release is what moves them into a location. - The status stepper’s receive step reads Received at supplier: “All items have been received and are held at the receiving supplier.” Partial receipts, several passes, over- and under-receiving all work exactly as they do on any other order. Sync to Shopify is switched off for these orders, with the reason shown on the disabled action: “Stock is held at the receiving supplier; move it into a location with a Supplier Stock Release.” Nothing is missing; the stock is recorded, it just isn’t in Shopify yet, because it isn’t in a Shopify location yet. Note Deliver-to-supplier orders are left out of the list page’s bulk Auto-receive (full and partial) and out of the Shopify POS receiving flow, both of which work per location. Receive them from the order’s own detail page instead. ## Reversing a receipt Unreceive works normally, and the dialog says what it’s reversing: the quantities are your stock at the receiving supplier, not Shopify inventory, and reversing removes them from that position. The one thing that can’t be undone is quantity that has already moved on; units reserved or released by a supplier stock release are refused, with a message saying so. Release-free quantities reverse cleanly. ## Getting the stock into a warehouse A received deliver-to-supplier PO leaves you holding buyer-owned stock at the receiving supplier. To bring it into one of your locations (and into Shopify’s on-hand), raise a [Supplier Stock Release] (/features/supply-orders/supplier-stock-releases/overview/) against the supplier that holds it, not against the one you bought from. That’s the step that turns this stock into Shopify inventory, and the only one that does. ## What this does to your inventory numbers - Shopify on-hand and incoming never change from this order, at any status, through any action. The stock reaches Shopify only when a supplier stock release lands it in a location. - Your forecast counts the units as on order. They’re yours from receipt, so an open deliver-to-supplier PO suppresses a repeat reorder for the same shortfall, exactly like an ordinary “hold at supplier” line, and unlike a dropship order, whose goods never become your stock at all. - Per-location figures are untouched. There’s no location on the order, so location-filtered forecasts, per-location min/max thresholds, and [incoming reconciliation] (/features/inventory/incoming-reconciliation/) all skip it. - Custom items can’t be converted into real Shopify products on these orders; that step activates Shopify inventory at a warehouse location, which this destination deliberately never does. ## Documents and exports The supplier-facing PDF ships to the receiving supplier’s address, and its Ship To block gains one line (Deliver to: , receiving on our behalf), so the supplier you’re buying from can tell at a glance that the address belongs to another business receiving for you, not to one of your own warehouses. Bulk CSV/XLSX exports need nothing special: the eight Delivery columns (company name, two address lines, city, province, ZIP, country, phone) carry the receiving supplier’s address on these orders, the customer’s on a dropship order, and the location’s on an ordinary one. Add them from a [purchase-order or line-item export template] (/features/supply-orders/purchase-orders/exports/#custom-column-sets-and-export-templates) like any other column. ## Merging, splitting, and returns - Merging: a deliver-to-supplier PO can’t be merged with another order, in either direction: merging would change who holds the goods. - Moving lines to an existing PO: also blocked, for the same reason. Each order is held by a single supplier, so lines can’t cross between them. Splitting into a new order is fine; the copy carries the destination, the receiving supplier, and the address. - Returns (RMAs): a return raised from a deliver-to-supplier PO uses that order’s delivery address as the return origin, since the receiving supplier is where the goods are physically coming back from. ## Limits - Elevate plan required to create one or to switch an order onto this destination. - Only Create Empty PO and editing a Draft order offer it; replenishment flows, the customer-orders wizard, imports, and bulk actions don’t. - The destination and the receiving supplier are Draft-only, and locked once the order is sent. - Every line is held at the receiving supplier; the per-line fulfillment mode can’t be changed. - The whole order goes to one receiving supplier. Splitting some lines to a warehouse and others to a supplier on one order isn’t supported; use separate orders. - No Shopify sync, no bulk auto-receive, no POS receiving, and no custom-item conversion. ## See also - [Transfer orders → Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): the transfer-order sibling: moving stock you already own out to a supplier, instead of buying it and having it delivered there. - [Dropship POs] (/features/supply-orders/purchase-orders/dropship/): the other location-less destination, and how it differs. - [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/): bringing the held stock into a warehouse. - [Line items & costs → Fulfillment mode per line] (/features/supply-orders/purchase-orders/line-items/#fulfillment-mode-per-line): what “held at supplier” means on an ordinary order. - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): the rest of the creation paths. - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): the receive flow this destination reuses. - [Suppliers → Directory] (/features/suppliers/directory/): the My stock at supplier sub-view where the held stock appears. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/line-items/ # Line items & costs Per-line columns, Bulk Edit, metafields, and constraint badges on a purchase order. A Logistified purchase order’s body is a table of line items: one row per variant. This page covers the columns you can put on it, how editing works, line-level metafields (both snapshot and write-back), constraint badges, and currency. ## On this page - Views and layouts - Fulfillment mode per line - Per-line columns - Received column - Sorting by SKU and barcode - Editing the Shopify SKU and barcode - Editing inline (Bulk Edit) - Applying a cost change to other variants - Line discounts - Supplier price tiers - Adding lines - Moving items to another PO - Snapshot metafields (Shopify → PO) - Write-back metafields (PO → Shopify) - Constraint badges - Cost calculation - Currency - See also ## Views and layouts The tabs above the line-item table are column views: you pick which columns each one shows, and you can save your own. Three are built in: - Standard: the operational columns (quantities, cost, landed cost, constraints). This is the view you edit from. - Inventory: current Available / On Hand / Incoming per line, at this PO’s location. - Sales: recent sales velocity, sell-through rate, capital tied up. Useful for sanity-checking what you’re about to order. After those come any views you’ve saved, and then two fixed layouts behind a divider: - Schedules: when a line has more than one planned delivery, whether that came from splitting it yourself or from a supply plan behind the scenes, each delivery shows here with its own quantity, requested and expected dates, lead time, and fulfillment mode. See [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/) for how to split a line and what it changes. - Receipts: the receipt log for each line. One row per receipt, with the destination, fulfillment mode, and Shopify sync status. Editing happens on a view, not on Schedules or Receipts; those two are read-only context. For how to add columns, reorder them and save your own view, see [Line-item column views] (/features/supply-orders/line-item-views/). ## Fulfillment mode per line Each line carries a fulfillment mode that determines where its receipt lands: Mode UI badge What receipt does Deliver to warehouse Warehouse (green) Standard receipt: records stock for the PO’s destination warehouse. Shopify on-hand updates through Quick Complete, Auto-sync, or manual Sync to Shopify when the destination is Shopify-backed. Hold at supplier Supplier Held (amber) Receipt creates buyer-owned supplier-held stock; does not push to Shopify on-hand. Release later via a [Supplier Stock Release] (/features/supply-orders/supplier-stock-releases/overview/). Warehouse consignment Consignment (indigo) Stock arrives in your warehouse but ownership stays with the supplier. Shopify on-hand is updated, exactly like a warehouse delivery; the supplier-owned position is tracked separately in Logistified. The mode is inherited from the supplier–variant link’s Default fulfillment mode at the time the line is created. You can override it per line in Bulk Edit, except on a PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/), where every line is Hold at supplier and the control is locked. When a line has multiple schedules with mixed fulfillment modes, the line shows a primary badge and each schedule shows its own; open the Schedules sub-tab to see the breakdown. ## Per-line columns The columns that appear depend on the active view and whether Bulk Edit is on. The tables below list what the built-in views show; the Columns picker offers many more, grouped as Product, Order, Pricing, Costs & Margin, Inventory and Sales. [anchor: standard-view--read-mode] ### Standard view: read mode Column What it shows Image Variant image from Shopify. Product Product title + variant title. Shopify-backed variants also show an external-link action that opens the variant in Shopify Admin; custom items and Assemblified raw materials do not show that action. SKU Variant SKU, with sorting options for Shopify SKU or supplier SKU. Barcode Variant barcode, with sorting options for Shopify barcode or supplier barcode. Quantity Ordered / confirmed / received progress with a small progress bar. Constraints ✓ / ⚠ / ✗ badges from the constraint engine. Cost Per-unit cost in the PO’s currency. Landed Cost (When Landed Cost is enabled in settings.) Per-unit landed cost including configured surcharges. Actions Row-level actions menu (edit row, delete row, etc.). ### Bulk Edit’s operational fields Bulk Edit works on whichever view you’re currently on; it keeps that view’s own columns and order rather than switching to a fixed layout. Any of the fields below that your view already shows (Quantity and Cost) become editable right where they are; any it doesn’t show are appended after your own columns for the duration of the edit, and disappear again once you exit. On the Standard view, that means only Fulfillment, the four extra quantity breakdowns, and Notes get appended, since Quantity and Cost are already columns there: Column What you can change Fulfillment Per-line mode: Deliver to warehouse / Hold at supplier / Warehouse consignment. Qty Ordered What you asked for. Qty Confirmed What the supplier agreed to ship (also editable via the confirm flow). Qty Received Actual receipts (also editable via the receive dialog). Qty Rejected Lines / units the supplier refused at confirmation. Qty Cancelled Operator-decided cancellations. Cost Per-unit cost. Notes Free-text notes per line. ### Inventory view Column What it shows Available Shopify’s available count for this variant. On Hand Shopify’s on-hand count. Incoming Units on order at this PO’s location, from open purchase and transfer orders, the same number the [Forecast] (/features/forecast/overview/) uses for this variant. ### Sales view Column What it shows Total Sales / Avg Sales Sales over 30 / 60 / 90 days. Sell-Through Rate What share of stock is selling. Sales Velocity Daily sales rate. Capital Tied Up Estimated cost basis of current stock. ### Received column The Order group in the Columns picker also offers Received: the line’s total received quantity as its own column, separate from the progress bar in Quantity. Hover the number for a breakdown of every receipt booked against the line, newest first (a reversal shows as a negative quantity), with the total underneath. This is the same information as the [Receipts sub-tab] (/features/supply-orders/purchase-orders/receiving/#the-receipts-sub-tab), without switching tabs. If your view already shows Received when you turn on Bulk Edit, the Qty Received input reuses that same column instead of adding a second one. Lines also carry supplier-specific data such as supplier SKU, supplier barcode, and supplier product name. These values come from the supplier-variant link and are visible in the row’s edit panel when you open a line. The Shopify SKU and Barcode shown in the table are also editable from that same panel; see [Editing the Shopify SKU and barcode] (#editing-the-shopify-sku-and-barcode). ## Sorting by SKU and barcode The SKU and Barcode headers are compact display columns, but their sort menus let you choose which identifier drives the row order: - SKU can sort by Shopify SKU or supplier SKU. - Barcode can sort by Shopify barcode or supplier barcode. Use the supplier-specific sort when the document or receiving workflow needs to match the order used by your supplier. The same row order is used by PO exports and supplier-facing documents where line-item sorting is applied. ## Editing the Shopify SKU and barcode Open a line with the row’s Edit action (in the Actions menu) to get its full edit panel: a different surface from Bulk Edit, covering fields Bulk Edit doesn’t. Under Product Information you’ll find editable Shopify SKU and Barcode fields: the actual values on the Shopify variant, separate from the supplier’s own SKU and barcode shown further down the same panel. Tip A line with no Shopify variant behind it (an Assemblified virtual material or a custom item) shows the same two fields, but a note explains that the values are stored on this purchase order only, since there’s no Shopify variant to push them to. Saving the panel always saves your change to the purchase order line first. If you changed the Shopify SKU or barcode, Logistified then asks Update Shopify variant?, listing each changed field with its old and new value and a checkbox next to it: - Save & Update Shopify: pushes every checked field to the Shopify variant. - Save without updating Shopify: keeps the change on this line only; the Shopify variant is untouched. Dismissing the prompt any other way (Escape, clicking outside, or its close control) cancels the whole edit instead of choosing one of those two: nothing on the line is saved. Clearing a field (leaving it blank) is a valid change too, and pushing it removes the SKU or barcode from the Shopify variant. If Shopify turns down a field (a SKU already used on another variant, for instance), the prompt shows Shopify’s own reason next to that field. Retry failed only appears when trying again could help; a value Shopify has already rejected won’t succeed on a second attempt, so no retry is offered for those. ## Editing inline (Bulk Edit) Cells in the line-item table are read-only by default. To enable inline editing, click the Bulk Edit button at the top-right of the line-item card. Once active: - Your current view’s columns stay put (Bulk Edit doesn’t switch you to a different layout), and a note above the table reminds you that additional order fields appear to the right while editing. - The quantity cells (Ordered / Confirmed / Received / Rejected / Cancelled) become editable text inputs. Whichever of these your view doesn’t already show are added after your own columns. - A Notes column is added if your view doesn’t already have one. - The Cost cell becomes editable. - If the active view shows the Retail price or Compare-at price columns, those become editable too, and they write straight to Shopify. See [Editing retail prices] (/features/supply-orders/editing-prices/). - Click Exit Edit (same button) to return to read-only mode. If you have unsaved changes, you’ll be asked to discard them first. Bulk Edit is mutually exclusive with row selection (the checkboxes for bulk-delete clear when you enter edit mode), but you can still remove lines without leaving Bulk Edit. Set a line’s Ordered quantity to 0, or click the trash icon in its Actions column, and the line is marked Removed on save: struck through, nothing deleted yet, no confirm per line. Typing a quantity again, or clicking the undo arrow that replaces the trash, keeps the line. When you click Save all changes, you’re asked once to confirm removing the marked lines (Save and remove); the dialog lists them by name, so you can spot one you marked by accident. Your other edits are saved first, then every marked line is removed in one go. If you leave Bulk Edit without saving, the marked lines stay on the order. If only part of a save goes through (for example a line was removed in another tab, or a value was refused), Bulk Edit stays open and tells you exactly what was not saved, such as “Not saved: SKU-2 (unit cost): Unit cost cannot be negative. Those changes are still in the editor.” The changes that did save leave the editor; the ones that didn’t stay staged, so Save all changes sends only what is still missing. Each cell respects the current PO status; the [lifecycle mutability matrix] (/features/supply-orders/purchase-orders/lifecycle/#what-you-can-edit-at-each-status) is the authoritative reference for what’s editable when. The [API] (/features/agent-access/operating-purchase-orders/) and Update lines from CSV/XLSX can also correct a plain ordered quantity or unit cost on any open PO, including a received one, without unreceiving stock. For these API line edits, currency, original-cost, and explicit line-discount fields still require a Draft PO; a changed plain unit cost removes the line discount. Tip On Received POs, Bulk Edit remains available for receipt corrections to received quantities. Completed and Cancelled POs are locked. ## Applying a cost change to other variants If a purchase order carries more than one variant of the same product, changing one line’s Cost in Bulk Edit and moving on prompts you to apply the new cost to the others as well; one price negotiation with a supplier usually covers every size or color, not just the line you happened to edit first. The prompt lists each other line with its current cost and the new cost side by side. Choose Apply to N line items to spread the change, or Only this item to keep it limited to the line you edited. Either way, the change is staged like any other Bulk Edit edit; nothing saves until you use the save bar, and Discard clears it along with everything else. The prompt only appears once per line per value: if you tab back through a cost you already answered for, or edit it back to what it started as, Logistified stays quiet. Changing it to a different cost prompts again. ## Line discounts A discount can also sit on a single line, separately from the [costs and discounts that adjust the whole order] (/features/supply-orders/purchase-orders/additional-costs/). Use it when a supplier prices one product down (a promotion on one style, an allowance for a damaged batch) rather than discounting the invoice as a whole. Tick the lines you want and click Discount selected (N) above the table, or use the tag action on a single row (Edit line discount). The Line discount (N items) dialog asks for: - Discount type: Percentage or Amount per unit. - Discount (%) or Discount per unit in the line’s currency: a percentage between 0 and 100, or an amount that may not exceed any selected line’s original unit cost. A preview table lists every selected line with its currency, Original / unit, and Net / unit, so you see the result before committing. Apply discount writes the net cost onto each line; Remove discount (offered when at least one selected line already carries one) clears it again. Two rules worth knowing: - Discounts never compound. Every calculation starts from the line’s original (list) cost, so applying a new discount replaces the previous one instead of stacking on top of it. - A mixed-currency selection can only take a percentage. If the lines you picked are in different currencies, Amount per unit is disabled; select lines of one currency, or use a percentage. A discounted line shows its original cost struck through above the net cost, and the discount beside it (“20% off”, or the amount per unit taken off). The PO PDF prints the same detail. Everything downstream uses the net cost: line totals, the order’s subtotal and totals, exports, and any cost pushed to Shopify or the supplier. Typing over the net cost in Bulk Edit removes that line’s discount. Discounts stop being editable once goods have arrived: the actions are disabled on Received, Partially Received, Completed, and Cancelled orders, and as soon as any line has a posted receipt (“Discounts cannot change after a receipt or once the order is closed”). Line discounts travel through imports and exports as well. A CSV / XLSX import can carry Original Unit Cost, Discount Type (Percentage or Amount per unit), and Discount Value columns, and line-item export templates offer the matching Line Item Original Unit Cost, Line Item Discount Type, and Line Item Discount Value columns, with Line Item Unit Cost always carrying the effective net cost. ## Supplier price tiers If the supplier has price breaks configured for the variant (a minimum quantity → unit cost table), a small tag icon appears in the line’s quantity cell. Hover it to see all tiers and which one Logistified recommends at the current ordered quantity: - applied (green badge): your current unit cost matches the recommended tier. - manual override (amber badge): you’ve kept a different unit cost than the tier recommends. Tiers are managed per supplier on the supplier detail page (Supply tab → Price Breaks). When the line’s quantity crosses a tier threshold, the recommendation updates live in Bulk Edit; the unit cost is not auto-rewritten; it remains your decision. ## Adding lines The detail page has a separate Add line items dropdown (above the line-item table). It offers a picker, a CSV/XLSX upload, a barcode-scan flow, a custom-item creator, and (when Assemblified is connected) Virtual Materials and a Split into Raw Materials action, or (when the [bundles.app integration] (/features/settings/integrations/) is on) a Split into Bundle Components action. For the full walkthrough, see [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/). ## Moving items to another PO The actions menu’s “Split by Item / Quantity” lets you move whole line items (or a partial quantity from a line) off this PO: - New PO: moved items land on a freshly created Draft PO (or a draft copy of this one). - Existing PO: moved items land on another Draft PO at the same location. The supplier doesn’t have to match: the target picker groups eligible POs into “Location & supplier match” and “Location match” (a different supplier), so you can consolidate items across suppliers at one location. A PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) can’t take part on either end; its lines are held by one specific supplier, so they can’t cross to another order. Moving them to a new PO works normally. When you move items into a PO with a different supplier, moved lines pick up that PO’s supplier pricing and details (or your shop’s defaults if the target supplier doesn’t carry the variant); a warning appears before you confirm. If a moved item’s variant already has a matching line on the target PO, the quantities are combined into that existing line instead of creating a duplicate row. If the matching line’s commercial, fulfillment, supplier, or date fields differ from the item you’re moving, Logistified shows you the differing values and asks you to resolve them first: pick one occurrence to supply the combined line’s shared values, or keep the occurrences as separate lines on the target PO. Split by Supplier creates separate Draft POs for the suppliers selected for the items. A newly created PO uses that supplier’s purchase-tax rate when one is set; otherwise it keeps the source PO’s rate. If neither has a rate, the new PO has no purchase tax. A configured 0% rate is kept as 0%, rather than being replaced. POs you select as existing targets keep their own tax rate. If the split reuses the original PO for a supplier, that PO also keeps its saved rate. ### What a split keeps When items move to another PO with Split by Supplier or Split Purchase Order, the order information that belongs to those items moves with them: - Linked sales orders. Each PO that receives items is linked to the sales orders whose items it carries, so the Linked sales orders banner and the Orders tab still show where every order is being bought, even after you delete the original PO. A sales order none of whose items are on the original PO (for example, only custom items, or a kit that the PO orders as its components) is linked to every PO of the split, so no link is lost. The original PO keeps all of its links, and an existing PO you move items into keeps its own links and gains the new ones. - Keep linked sales orders. When the original PO is linked to sales orders, the dialog shows Keep linked sales orders (N), ticked by default: beside Create as Draft in Split Purchase Order (when you split into a new PO), and on the Confirm step of Split by Supplier. Untick it and the POs that receive items get none of the original PO’s links. A PO that reads its delivery address from a Shopify order always keeps that order linked. - Dates and forecast view. A PO created by Split by Supplier keeps the original PO’s due date, expected delivery date, requested delivery date, shipping date and forecast view; it’s a Draft, so you can change them. Split Purchase Order starts the new PO without the forecast view, and without the dates when you tick Create as Draft. - Tags. A new PO created by either split carries the original PO’s tags. An existing PO you move items into keeps its own tags. - Inventory plans. If the original PO is listed on an inventory plan, the POs that Split by Supplier moves items to (new or existing) and the new PO that Split Purchase Order creates are listed on that plan too. Moving items into an existing PO with Split Purchase Order doesn’t add that PO to the plan. The split doesn’t change POs you split before this update; to link one to its sales orders, open Edit Details and choose Manage under Sales Orders. Moving items into an existing PO with Split Purchase Order combines them as a merge, which already brings the sales-order links along. ## Snapshot metafields (Shopify → PO) You can surface a selection of Shopify product / variant metafields on the PO line item. When the line is created, the current Shopify value is snapshotted onto the line, so even if the metafield later changes in Shopify, the PO carries the value it had at the time of creation. - Where you configure them: Settings → Purchase Orders → Shopify Fields tab. - Refresh: the Refresh from Shopify button re-pulls definitions when you’ve added new metafields in Shopify since last setup. - Where they show: as additional columns on the line-item table and on the PO PDF (subject to the export template). Use snapshot metafields for supplier-side identifiers (their batch number, warranty period, a compliance ID) you want stamped on the PO at the moment of ordering. A snapshot metafield that holds a money value (a price or similar amount) shows as formatted money (with its own currency) on the line-item table, on the PDF, and in the file export; the file export puts the amount in a plain number column and names the currency in the column header (e.g. “Retail price (CAD)”). If the lines carry that metafield in more than one currency, each cell shows the amount with its own currency code instead (e.g. 12.5 CAD) and the header stays plain. Update Metafields (Actions menu): turning on a snapshot metafield in settings only stamps new lines going forward; older lines on this PO won’t have a value. The Update Metafields action, available for the order in any status, fills in a value for every line that’s missing one and refreshes the value on lines that already have one, pulling current data from Shopify. It never clears a value that’s already there, so it’s safe to run at any time; a lookup that can’t be matched to a Shopify product simply leaves that line untouched. The same action is available on transfer orders and return orders. ## Write-back metafields (PO → Shopify) Logistified can also write PO-derived values back into Shopify when a PO hits a trigger status you choose. For example, you can have the total ordered quantity write to a inventory.on_order metafield on the product when the PO becomes Confirmed. - Where you configure them: Settings → Purchase Orders → Shopify Fields tab, the “Write Line Item Fields” card. - Per-rule config: trigger status, source field (e.g. line-item quantity ordered / confirmed / pending), owner type (product or variant), target metafield key. - Boolean rules: for Boolean Shopify metafields, configure TRUE and FALSE status lists. Logistified keeps the value TRUE while another active PO for the same product or variant is still in a TRUE status. - Retrospective apply: when you add a new rule, you can apply it to existing matching POs in one go. - Kits from Assemblified: date rules can also write a date onto the kits your ordered components go into. See [Settings → Writing dates to kits] (/features/supply-orders/purchase-orders/settings/#writing-dates-to-kits-assemblified). Use write-back when something downstream (a storefront badge, a 3PL integration, your own internal dashboard) needs to know what’s on order. ## Constraint badges Two kinds of checks show up in the Constraints column: two built-in checks that always run (minimum order quantity and pack-size multiples) and, when you have constraint rules configured (Elevate plan), status from your saved rules: - OK / green: the applicable checks passed. - Warning / amber: a warning or objective rule found something to review. - Error / red: an error-severity rule failed. - Missing data: the rule needs a value such as Product MOQ, Unit CBM, Unit weight, Group key, or Purchase family and the value is not available for the PO context. For a supplier whose MOQ applies to the whole product (see [Lead times & MOQ] (/features/suppliers/lead-times-and-moq/#moq-applies-to-each-variant-or-the-whole-product)), the built-in MOQ check sums ordered quantity across every variant of that product on the PO and compares it to the product’s minimum; every affected variant shows the same warning until the combined total meets it. The PO’s task list reflects this too, counting one “product MOQ issue” per under-ordered product instead of one per line. This is separate from the guided Product MOQ rule preset in [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/#presets), which compares against a mapped Product MOQ field of your own choosing. Hover or open the PO hints to see the rule details. The [Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/) can propose additive fixes for targeted rules, but it cannot reduce/remove lines in the current Fill gaps mode. [Image: Line item table with Product MOQ badges on affected product variants] (/_astro/04-po-constraint-violation-badges.BW2M_Mq1_Z21xDm9.webp) Product MOQ is a product-level rule: variants of the same product are summed before the MOQ check. If the product total is too low, every affected variant row gets the same badge. ## Cost calculation ``` Subtotal = sum(ordered quantity × unit cost) Total = subtotal + shipping + adjustments + tax − applied credits ``` Totals update on every line change. The header shows subtotal, tax, shipping, applied credits, and final due. If you’ve enabled Landed Cost in settings, each line also displays its per-unit landed cost. Where a line carries a [line discount] (#line-discounts), the net unit cost is what the subtotal uses. Sub-cent precision. Unit cost fields accept more than two decimal places, which matters when a supplier quotes fractions of a cent: a component at 0.000125 per unit, say. The stored value keeps its full precision through editing, imports, bulk updates, and cost sync. Tables, dialogs, and the activity log display a unit cost to at most four decimal places, so 12.345678 reads as 12.3457 while 12.50 is unchanged; a cost too small to show at four decimals is widened until its first significant digit appears rather than rounding to zero. Opening any cost editor shows and saves the full stored number, and line totals, the financial summary, PDFs, exports, payments, and accounting all use the currency’s normal number of decimals. To push a PO’s costs out to Shopify or to the supplier’s catalog, see [Preferences → Update Unit Cost] (/features/supply-orders/purchase-orders/preferences/#update-unit-cost). ## Currency A PO has one currency for its line items, inherited from the supplier at creation. Mixing currencies on a single PO’s lines isn’t supported. Payments, however, can be recorded in any currency and are converted with a per-payment exchange rate; see [Payments → Currency] (/features/supply-orders/purchase-orders/payments/#currency). Tip Snapshot metafields are the easiest way to integrate Logistified into your supplier-side workflow: anything they need stamped on the order, surface as a metafield and edit it inline. ## See also - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries. - [Line-item column views] (/features/supply-orders/line-item-views/): choosing columns, saving views, and the cost basis behind the margin columns. - [Editing retail prices] (/features/supply-orders/editing-prices/): the price columns write to Shopify immediately. - [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/): the picker, imports, custom items, and the raw-materials split. - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): how the fulfillment mode determines what happens to inventory on receive. - [Supplier Stock Releases] (/features/supply-orders/supplier-stock-releases/overview/): what to do with stock from “Hold at supplier” lines after the PO is received. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): what’s editable when. - [Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/): the rule engine that drives the badges. - [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/): configuring rules and field bindings. - [Settings] (/features/supply-orders/purchase-orders/settings/): configuring snapshot and write-back metafields. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/delivery-schedules/ # Delivery schedules Split a line into several dated deliveries on one purchase order, instead of one lump arrival. A supplier sometimes ships one product in portions rather than all at once: 12 units as 4 in August, 4 in September, and 4 in October. In Logistified, a delivery schedule lets you record that plan against a single line, on a single purchase order, instead of creating three separate orders or waiting to update dates one shipment at a time. ## On this page - What a delivery schedule is - Splitting a line into deliveries - The delivery schedule editor - What happens to the line’s own date - Receiving a split line - Confirmed quantities carry across a split - The supplier PDF - Viewing schedules on the Schedules tab - Things to know - See also ## What a delivery schedule is Every line on a purchase order already has one delivery: its ordered quantity, against one delivery date. Splitting a line just means giving it more than one delivery: each with its own quantity and its own date, all adding up to the line’s total ordered quantity. A line stays a single, simple delivery until you deliberately split it. Nothing changes about how an unsplit line behaves. ## Splitting a line into deliveries Two ways to open the editor: - On the line-item table, hover a row and click the Split into deliveries icon next to the edit (pencil) action. It’s hidden once the order reaches Completed, Cancelled, or Received. - From the Schedules view (see [Line items & costs → Views and layouts] (/features/supply-orders/purchase-orders/line-items/#views-and-layouts)), click the pencil next to any line. Either entry point opens the line’s edit panel scrolled straight to the Delivery schedule section. ## The delivery schedule editor The Delivery schedule section shows one row per planned delivery: Column What it is Qty How many units arrive on this delivery. Delivery date The date you expect this portion to arrive. Every delivery needs one once there’s more than one on the line. Status Scheduled, Partially received, Received, or Cancelled, tracked automatically as receipts come in. Received How many units of this delivery have actually arrived so far. Click + Add delivery to add another row. The new row starts empty and nothing is moved from the other rows; type its quantity and date yourself. The line’s total is simply what the rows add up to. Each row can be removed with its ✕, except a row that already has received, confirmed, or supplier-rejected units against it; that one is locked to protect activity that already happened. A row that’s only confirmed (nothing received or rejected yet) can still be removed. The section shows a running total, like “12 of 12 scheduled,” so you can see at a glance whether the deliveries add up to what you ordered. Once a line has more than one delivery, the line’s own Qty ordered field becomes read-only; the deliveries collectively own that number. To change the total, resize the individual deliveries instead. To change the total the old way, merge everything back down to one delivery first. Saving the section checks each delivery has a valid quantity and a date. If a delivery is missing a date, saving is blocked with Each delivery needs a date; dates are what determines the order deliveries are received in (see [Receiving a split line] (#receiving-a-split-line) below). Tip The editor is open for edits at any purchase-order status except Completed, Cancelled, and Received, including On Hold and Disputed. That’s slightly looser than the line-level delivery-date field, which is only editable through Draft. ## What happens to the line’s own date An unsplit line shows and uses its own single delivery date, exactly as before. Once you split it: - The line’s own delivery-date field becomes read-only, with a hint “Set per delivery below”; the individual deliveries now own it. - Anywhere the line’s date is shown elsewhere in Logistified (the order list, the detail page header, exports), it displays the earliest still-open delivery’s date. Once August’s portion is received, the line’s shown date automatically becomes September’s. ## Receiving a split line There’s no separate “receive this one delivery” picker. You receive a split line exactly like any other (enter the total quantity that arrived in the [receive dialog] (/features/supply-orders/purchase-orders/receiving/)), and Logistified fills the deliveries earliest date first. Receiving 4 units against a line with August, September, and October deliveries closes out August; receiving 4 more closes out September; and so on. This is also why every delivery on a split line needs its own date: Logistified sorts undated deliveries first, so a delivery with no date would receive before ones that actually have an earlier date. ## Confirmed quantities carry across a split If a line already has a confirmed quantity when you split it, Logistified doesn’t discard that promise. What happens depends on where the order is in its lifecycle: - Order past the confirmation step (Confirmed, In Progress, On Hold, Partially Received): every delivery counts as confirmed: the ones you resized and any you added. There is no confirmation step left to run, and a delivery that stayed unconfirmed here could never be received, so adding a delivery of 12 to a line confirmed at 18 gives you 30 confirmed, ready to receive. - Order still Sent: the supplier hasn’t answered yet, so Logistified spreads the line’s existing confirmed total across the deliveries, earliest first, and nothing is invented; a line confirmed 10 of 12 that you split into 4/4/4 comes out confirmed 4/4/2, still totalling 10. Either way, you don’t need to re-confirm anything just because you changed how a line is delivered. ## The supplier PDF When a line has more than one delivery, the printed purchase order shows the breakdown underneath the quantity: ``` 12 4 pcs · Aug 15, 2026 4 pcs · Sep 15, 2026 4 pcs · Oct 15, 2026 ``` The Expected Delivery date in the document header also follows the plan on such an order: it shows the earliest delivery still to come, with a small “3 schedules” badge next to it, rather than the order-level date. This is controlled by the “Show delivery schedule on split lines” toggle on your PDF export template, on by default. Turn it off if you’d rather the supplier PDF only ever show the total. It only ever adds sub-lines to a line you’ve actually split; a single-delivery line prints exactly as it always has. See [Settings → Export templates] (/features/supply-orders/purchase-orders/settings/#export-templates-csv--xlsx--pdf). Cancelled deliveries are left off the printed breakdown; they’re not something the supplier needs to plan for. ## Viewing schedules on the Schedules tab Switch the line-item table to its Schedules view (see [Line items & costs] (/features/supply-orders/purchase-orders/line-items/#views-and-layouts)) to see every line’s deliveries listed as sub-rows, each with its own quantity, requested date, expected date, lead time, and fulfillment mode. Hovering the quantity in this view also shows the requested date for each delivery. ## Things to know - “Split Delivery Date” is a different, unrelated setting. The [Split delivery date preference] (/features/supply-orders/purchase-orders/preferences/#split-delivery-date) only relabels the delivery-date column on the PO list (showing “Requested” / “Expected” / “Estimated” instead of the generic label); it has nothing to do with splitting a line into multiple deliveries. That naming collision is exactly why this feature is worded “Split into deliveries” in the app. - A bulk file update skips dates on a split line. [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/#lines-with-split-delivery-dates) can’t tell a single spreadsheet cell which of several deliveries it means, so it skips that cell with a note pointing you to the order page. - Every edit is logged. Adding, resizing, moving, or removing a delivery shows up in the order’s activity log with the before-and-after quantity and date, so you (and anyone else on the order) can see exactly what changed and when. - Deliveries survive a merge. Moving or merging lines between purchase orders preserves their deliveries; see [Lifecycle & statuses → Merging POs] (/features/supply-orders/purchase-orders/lifecycle/#merging-pos). - You can’t create a purchase order with a plan already split. Split a line after the order exists, from the line-item table. - Stocky-imported and already-received orders are locked, like everything else about those orders; there’s no plan to edit. ## See also - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): the Schedules view and general line-editing surfaces. - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): how a receipt’s total is allocated across a split line’s deliveries. - [Exports] (/features/supply-orders/purchase-orders/exports/): the supplier PDF and its templates. - [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/): why split lines skip the date columns in a bulk file update. - [Preferences → Split delivery date] (/features/supply-orders/purchase-orders/preferences/#split-delivery-date): the unrelated list-label setting. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): what’s editable at each status, and how deliveries behave in a merge. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/adding-line-items/ # Adding line items Every way to put a row on a PO: picker, supplier picker, barcode scan, import, custom items, virtual materials, and the raw-materials / bundle-components splits. Once a purchase order is created in Logistified, the Add line items dropdown above the line-item table is your single entry point for adding rows. It offers several paths depending on where the items are coming from. This page covers each, including the Assemblified raw-materials split and the bundles.app bundle-components split. ## On this page - The Add line items menu - Shopify Variants (picker) - Pick From Supplier - Scan Barcode - Upload CSV / XLSX - Custom items - Virtual Materials (Assemblified) - Split into Raw Materials (Assemblified) - Split into Bundle Components (bundles.app) - When can you add lines? - See also ## The Add line items menu On a Draft (and most in-flight) PO, click Add line items above the line-item table. (On a PO that has no lines yet the same menu sits in the empty state and is labelled Add new line items.) Some options only appear when relevant: Pick From Supplier needs a supplier on the PO, and Split into Bundle Components only appears when the [bundles.app integration] (/features/settings/integrations/#bundlesapp) is turned on. The Assemblified options (Virtual Materials, Split into Raw Materials, Create Work Order) are always in the menu, whether or not Assemblified is feeding data into your shop. ## Shopify Variants (picker) The default path. Opens Logistified’s product picker, which reads live from your Shopify catalog. Search by product title or SKU (a scope dropdown limits the search to All, Product Name, or SKU) and add Vendor or Tag filters to narrow the list further. A Product status dropdown next to the search controls which products appear: Active & draft (the default, which hides archived products), Active only, or All statuses. Draft and archived products carry a badge, and if a search finds nothing because of the status filter, a Show all statuses button appears. Stock adjustments and return orders open the picker on All statuses, since archived stock is a normal subject there. Click the Product or SKU column header to sort the list (click again to reverse, a third time to clear). Product sorting covers your whole catalog; SKU sorting applies to the products already loaded, so scroll down to load more. Pick one or many; click Select (N). Logistified opens a configuration step where you set quantity and unit cost per row (with supplier-cost pre-fill when available), then confirms. Select All selects every result matching your current search and filters, including results that haven’t loaded into the list yet. The button first pages through the remaining results (it shows Selecting all… and the list is locked until it finishes), then replaces your current selection with everything it found. On a large catalog this can take a while, so narrow your search or filters before using it. If loading fails partway through, an alert offers Retry selecting all. Once every loaded row is selected, the same button flips to Deselect All, which clears the whole selection. If your selection includes variants that haven’t synced into Logistified yet (for example, after using Select All on a recently imported or newly created product), those items are skipped and a notice tells you how many were not added and why. The rest of your selection lands on the PO normally. If the notice appears, wait for the next scheduled product sync and re-add the skipped items. Use it when you know the SKU and just want to drop it on the PO. ## Pick From Supplier Only appears when the PO has a supplier. Opens a supplier-scoped picker that lists only the variants linked to this supplier in your supplier–variant mapping. MOQ, pack size, and lead time pre-fill from the link. A stock column shows each variant’s current inventory: an in-stock count, Out of stock, Not tracked for variants that don’t track inventory in Shopify, or N oversold (highlighted) when more has been sold than is on hand. An On Other POs column shows how many units of each variant are already committed on other draft or open purchase orders (the current PO excluded), useful for spotting variants you may be double-ordering. Use it when you want to add only items this specific supplier carries, faster than typing into the general picker. ## Scan Barcode Opens a scan dialog with a single input field, built for a keyboard-wedge barcode scanner (a scanner gun that types the code and presses Enter). You can also type or paste a code. There is no camera scanning. Each scan resolves to a variant via SKU/barcode lookup and adds (or updates) a line. With the scan field empty, press Enter to add one more unit to the last-scanned item or Backspace/Delete to remove one, without leaving the scan field. Useful at the receiving station or when working from a printed packing list. If a scanned item can’t be added (it’s already on the order, or the variant hasn’t synced from Shopify yet), scanning stops with an error explaining why. Anything added before that point stays on the PO; review the order, then resume scanning. ## Upload CSV / XLSX Opens the unified import parser for bulk add. Map columns (SKU / barcode → variant, quantity, unit cost, supplier SKU, notes, etc.), preview, import. If your file contains updated unit costs for existing PO lines, you’ll be offered a follow-up supplier-sync to update the linked supplier’s default cost in one step. Duplicate rows in the file. If two or more rows in your CSV resolve to the same product variant (either the same SKU listed twice, or two different SKU values that point to one variant), the preview shows an orange Duplicate badge in the summary bar and a warning banner. The Review & Import button stays disabled until you resolve them. Click Combine duplicates to merge each group into one row with the quantities summed; or edit your file and re-upload if you need a different split. The same parser is used everywhere imports exist in Logistified; see [Settings → Data import & templates] (/features/settings/data-import-and-templates/) for column-mapping presets. Partway failures. Large files import in batches. If a batch can’t be fully added (some rows are already on the order, or reference variants that haven’t synced from Shopify yet), the import stops with an error telling you what happened. Rows from earlier batches stay on the PO; review the order, resolve the issue, and re-import the rest. Many orders at once. This upload adds rows to this PO. If your file spans several purchase orders and updates lines that already exist (a packing list with revised delivery dates and a container tracking number, say), use [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/) from the purchase-order list instead. ## Custom items Some shops order things that aren’t in Shopify yet: a one-off batch, a sample run, a product you haven’t committed to selling. Pick Custom Item and fill in title, SKU, cost, and quantity. The line can sit on the PO while you work out the real product. Once the PO reaches In Progress (and while it is Partially Received, Received, or Completed), each custom-item line gets an Add as product to Shopify action. Logistified creates the Shopify product and variant (as a Draft product, stocked with the quantity you’ve already received at the PO’s location) and attaches that reference back to the PO line. The line still remains a custom-item line on this PO; it is not added to a supplier and does not become identical to a normal Shopify-linked line. Caution Custom-item lines are skipped by the Shopify inventory- and cost-sync steps for as long as they exist; converting one does not change that, because the PO line stays a custom-item line. What conversion does do is create the Shopify variant already stocked with the quantity you received, which is why the action only appears once the PO is In Progress or further along. ## Virtual Materials (Assemblified) Virtual materials are raw inputs tracked by Assemblified but not exposed as standalone Shopify variants: fabric rolls, sheet stock, packaging components, etc. The picker lets you order them directly on a PO, with quantities and costs coming from Assemblified’s catalog. The option is always in the menu; if Assemblified isn’t feeding materials into your shop, the picker opens empty. The same picker also lists Assemblified sub-assemblies (SKUs starting with ASM-), after the virtual materials and marked Assemblified sub-assembly. Receiving them sends the quantity and price to Assemblified instead of Shopify. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/). ## Split into Raw Materials (Assemblified) Always in the menu; it does something useful when lines on the PO have a Bill of Materials (BOM) defined in Assemblified. Clicking Split into Raw Materials opens a dialog that: 1. Fetches component breakdowns from Assemblified for each line on the PO. 2. Reviews what will happen: lines with a BOM are decomposed into their raw materials; existing lines that overlap with the components are merged (quantities combined); lines without a BOM are left unchanged. 3. Replaces the PO body with the merged raw-materials view when you confirm. Use it when you want to order at the raw-material level (so the supplier gets a single roll, not five finished SKUs) while still composing the PO from end products. Note The split is destructive on the parent rows; they’re replaced by their components. If you want both views, save / export a copy of the PO before splitting. ## Split into Bundle Components (bundles.app) Only appears when the [bundles.app integration] (/features/settings/integrations/#bundlesapp) is turned on. It’s useful when the PO has bundle line items. Clicking Split into Bundle Components opens a dialog that works the same way as Split into Raw Materials: 1. Fetches the current component breakdown for each bundle line on the PO. 2. Reviews what will happen: bundle lines are decomposed into their components; existing lines that overlap with those components are merged (quantities combined); lines without a bundle breakdown are left unchanged. 3. Replaces the PO body with the merged component view when you confirm. Use it when you want to order components directly (so the supplier gets the individual parts, not the finished bundle SKU) while still composing the PO from bundle listings. Note Like the Assemblified split, this is destructive on the parent bundle rows; they’re replaced by their components. Save / export a copy first if you want both views. ## When can you add lines? The Add line items menu shows up on every status except Completed and Cancelled: Received included, so you can still correct an order after receiving it. On Completed and Cancelled the whole line-item table goes read-only and the menu disappears. The picker also enforces a “no duplicates” check: if the variant is already on the PO, the configuration step shows it as a duplicate and won’t add it again. Update the quantity inline instead. ## See also - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): the high-level entry points for starting a PO. - [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/): changing dates, quantities, costs and shipping details on lines that already exist, across many POs at once. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): what each column means and how Bulk Edit works. - [Settings → Data import & templates] (/features/settings/data-import-and-templates/): column-mapping presets for the CSV / XLSX flow. - [Settings → Integrations] (/features/settings/integrations/): turning on the bundles.app integration. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/bulk-line-update/ # Update lines from a file Push delivery dates, quantities, costs and shipping details onto existing purchase orders from one spreadsheet, keyed by PO number and SKU. Your supplier or freight forwarder sends a packing list. It covers four purchase orders from three suppliers, all in one container, and it has a new delivery date for almost every line plus the container’s tracking number. Typing that into Logistified by hand means opening four orders and editing dozens of dates. Update lines from CSV/XLSX takes that spreadsheet as-is. Each row says “on this PO, for this SKU, set these values”, and because every row names its own purchase order, one file can touch as many orders as you like. You don’t select anything on the list first. Note This updates existing lines only. It never creates a purchase order and never adds a line to one. To create orders from a file, use [Import from CSV/XLSX] (/features/supply-orders/purchase-orders/creating/); to add lines to one open order, use [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/). ## On this page - When to use it - Opening it - The columns - Blank means unchanged - Reviewing before anything is written - Fields your order’s status won’t accept - Lines with split delivery dates - Shipping date, tracking and carrier - Running the update - Downloading the results - What updates automatically - See also ## When to use it - A consolidated shipment. Several POs, one container, one packing list with dates and a tracking number. - A supplier’s confirmation spreadsheet. They reply with revised delivery dates per SKU across the orders you sent them. - A freight update. Ship date, tracking number, carrier and an estimated arrival, for a batch of orders at once. If you only need to change one or two lines, editing them on the order page is faster. ## Opening it Go to Supply Orders → Purchase Orders and click Create Purchase Order → Update lines from CSV/XLSX. It sits in the same group as the two import options, and (unlike the Actions menu items) it doesn’t care whether any rows are selected. Pick your file, and Logistified maps the columns for you. If a column was matched to the wrong field, Change mapping in the review step lets you fix it without re-uploading. Download a starter template from the same screen if you’d rather begin from Logistified’s own column names. Tip Save the mapping as a template the first time and every later file from the same supplier skips straight to the review step. Templates are managed in [Settings → Data import & templates] (/features/settings/data-import-and-templates/). ## The columns Only PO number and one of SKU / Barcode are required. Everything else is optional, and a column you leave out of the file simply doesn’t get touched. Column Applies to What it does PO number the order Required. Matched against your existing PO numbers, ignoring upper/lower case. SKU or Barcode the line At least one per row. SKU is matched against the product’s SKU and then the supplier SKU; Barcode against the barcode and then the supplier barcode. Expected delivery date the line The line’s expected delivery date. Requested delivery date the line The line’s requested delivery date. Quantity ordered the line Any open order, including Sent, receiving, On Hold, and Disputed. Must be a whole number of 0 or more. Unit cost the line Any open order, including Sent, receiving, On Hold, and Disputed. Must be 0 or more. Shipping date the order The order’s own Shipping Date. Tracking number, Carrier, Shipped at, Estimated arrival the order The order’s shipment. Carrier is matched against your configured [carriers] (/features/settings/carriers/) by name or by code. A filled example: two orders, three lines, one container: PO number SKU Expected delivery date Quantity ordered Shipping date Tracking number Carrier PO-1041 TSHIRT-BLK-M 2026-10-14 2026-09-20 1Z999AA10123456784 UPS PO-1041 TSHIRT-BLK-L 2026-10-14 2026-09-20 1Z999AA10123456784 UPS PO-1042 MUG-CER-350 2026-10-21 240 Dates are read in whatever format your file uses; the mapping step shows you which one it detected, and you can change it there. SKUs and barcodes keep their leading zeros. Caution The five order-level columns (Shipping date, Tracking number, Carrier, Shipped at, Estimated arrival) must be identical on every row of the same PO, as they are for PO-1041 above. If two rows of one order disagree, that column is left alone for that order and the review step tells you which rows clashed. The line dates on those rows still go through. ## Blank means unchanged An empty cell leaves the current value alone. There is no way to clear a value from the file; if you need a date removed, do it on the order page. This is what makes the file safe to re-upload. Logistified compares every value against what the order already holds and only writes the ones that actually differ, so uploading the same file twice reports No change on every order and touches nothing. ## Reviewing before anything is written Nothing is saved until you click Update. After the file is read, Logistified looks up every PO number you named and shows a review screen, one card per order, with Current → New for each cell that will change, plus a plain-language reason for anything it can’t do: - Order not found: no PO carries that number. - Ambiguous (2 orders): more than one PO carries that number. Logistified never guesses which one you meant; rename one of them, or edit those lines on the order page. - Not on this order: the SKU or barcode isn’t on that PO. - Ambiguous line: the same SKU appears on two lines of that order. Edit those two on the order page. - Identifiers disagree: the row’s SKU and its barcode point at two different lines. - Duplicate row: an earlier row already claimed that line. The first one in the file wins. Switch between the Orders and Rows views to read the same result grouped either way. [Image: Review step of Update purchase order lines: one card per order with Current → New per cell, the order-level shipping changes, and a rejected row] (/_astro/07-bulk-line-update-review.eQs_SUjV_PTS6Y.webp) The review step. Nothing has been written yet; each order card lists every cell that will change, the order-level shipping values, and any row it had to reject. ## Fields your order’s status won’t accept A file usually spans orders at different stages, and Logistified doesn’t refuse the whole thing because one cell doesn’t fit. It skips that cell, tells you why, and applies the rest of the row. Column Accepted while the order is… Expected / Requested delivery date Draft, Sent, Partially Confirmed, Confirmed, In Progress, Partially Received, Received Quantity ordered, Unit cost Draft, Sent, Partially Confirmed, Confirmed, In Progress, Partially Received, Received, On Hold, or Disputed Shipping date Anything except Received, Completed and Cancelled Only Completed and Cancelled orders are rejected outright; those are closed, and the file can’t reopen them. A quantity cannot be reduced below goods already received, rejected, or cancelled. If a row asks for that, Logistified reports that order as needing attention or failed; correct the quantity and upload it again. Changing a line’s Unit cost in the file removes any discount on that line. Uploading the same cost leaves its discount in place. This changes the purchase order only; it does not update the cost in Shopify or in your supplier catalogue. ## Lines with split delivery dates If a line has been split into more than one [scheduled delivery] (/features/supply-orders/purchase-orders/delivery-schedules/), each with its own date, the order page shows those schedule dates rather than the line’s, and a single cell in your file can’t say which delivery it means. Those cells are skipped, with the note “line has split delivery dates, edit on the order page”; the other date on the same line, and the order-level columns, still apply. A line that hasn’t been split is updated normally, and its delivery date stays in step with the date you supplied. ## Shipping date, tracking and carrier The order-level columns are applied after the line changes, and they follow the shipment rules you’d expect from the [Shipments] (/features/supply-orders/purchase-orders/shipments/) card: - The order has no shipment yet: one is created with whatever you supplied. It starts as Pending and carries no line assignments; add those on the order page if you need them. - The order has exactly one shipment: it’s updated. - The order has several shipments: the one whose tracking number matches the file is updated. If none matches, the shipment part is skipped with a warning and everything else still goes through. Carrier is matched by name or by code, ignoring case, spaces and punctuation. If the name isn’t one of your configured carriers, is set to inactive, or matches two of them, the carrier is left as it was and you get a warning, but the tracking number is still saved, because that’s the part you actually need on the order. Shipping date sets the order’s own Shipping Date. It does not recalculate a payment due date from your payment terms; that stays where it is, and you can adjust it on the order page. ## Running the update Click Update N orders. Logistified works through the orders one at a time, showing each result as it lands. Stop after current order finishes the order in flight and leaves the rest untouched; nothing is half-applied. You can’t close the dialog while it’s running; closing it beforehand asks you to confirm, since the review hasn’t written anything yet. Each order finishes as one of: Result Meaning Updated Everything you asked for landed. Needs attention Something was saved and a follow-up wasn’t: for example the shipment couldn’t be matched. The message says what. Already up to date The order already held every value in the file. Rejected The order couldn’t be found, was ambiguous, or is Completed/Cancelled. Nothing was written. Failed Something went wrong mid-write. The message names the step it stopped at. Not run You pressed Stop before this order started. The run keeps going past a failure; one bad order never stops the rest. [Image: Finished step: progress bar at 100%, the tally 2 updated, and one line per order saying what was applied] (/_astro/08-bulk-line-update-finished.BukwM9ZV_Z3zM2S.webp) The finished step. The tally counts every order in the file; each order's line says what landed (lines, ship date, shipment, metafields, log entry), and Download results gives you the same per row. ## Downloading the results The finished screen offers Download results, an XLSX with one row per row of your original file: the outcome, the fields that were applied, the fields that were skipped, and the reason. Extra rows per order cover the order-level parts, so a tracking number that didn’t land is visible rather than hidden. Fix the rejected rows in that sheet, delete the ones that succeeded (or don’t; re-uploading a row that’s already correct reports No change and writes nothing), and upload it again. ## What updates automatically - Line-item metafields refresh on their own. Delivery dates and quantities pushed from a file feed the same Shopify writeback as editing them on the order page; you don’t need to run Update Metafields afterwards. - Every order that changed gets an activity-log entry under your name, reading something like “Bulk line update from packing-list.xlsx: 3 lines updated (expected delivery date), shipping date set, shipment updated”. Orders reported as No change get no entry. - Nothing else fires that wouldn’t have. The file goes through exactly the same save path as the order page, so incoming-inventory figures, product tags and accounting stay in step, and nothing extra happens because the change arrived from a spreadsheet. Note A file can hold up to 5,000 rows, and one purchase order can take at most 500 changed lines per file. Larger packing lists need splitting into several files; each one is independent, so you can run them back to back. ## See also - [Adding line items] (/features/supply-orders/purchase-orders/adding-line-items/): putting new rows on one order, including its own CSV / XLSX upload. - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): creating orders from a file. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries, and why a bulk file update skips those dates. - [Shipments] (/features/supply-orders/purchase-orders/shipments/): the shipment card these columns write to. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/): what each line column means. - [Settings → Carriers] (/features/settings/carriers/): the carrier names and codes the Carrier column is matched against. - [Settings → Data import & templates] (/features/settings/data-import-and-templates/): saved column mappings. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/sending/ # Sending the PO Submit a PO to your supplier, email vs manual, prerequisites, delivery status, supplier confirmation. When you send a PO, Logistified transitions it to Sent. There are two ways to do that: via Logistified (email + PDF) or manually (status change only). This page covers both paths, what gets emailed, the delivery-status callback, resending, prerequisites, and how supplier confirmation flows back in. ## On this page - The Send button: two paths - What gets emailed (Send via Logistified) - Supplier instructions - Email delivery status - Resending - What you must have set up - Supplier confirmation paths - See also [anchor: the-send-button--two-paths] ## The Send button: two paths From a Draft PO, click Send to Supplier in the action bar at the top of the page (the progress stepper beside it is a read-only indicator). A dialog opens with two options: - Send via Logistified. Generates the PO PDF, queues a supplier email with the PDF attached, moves the PO to Sent, stamps the Sent date, logs the action. This option is greyed out if email sending isn’t configured; the dialog tells you what’s missing and offers a deep-link to fix it. A supplier email address is no longer required to open the dialog: you can type recipients by hand, or set [default email recipients] (/features/suppliers/directory/#default-email-recipients) on the supplier so the To/CC fields pre-fill automatically. - Mark as Sent (Manual). Flips the status to Sent without sending email. The PDF is still generated on demand from the actions menu; the supplier just doesn’t get it automatically. Use this when you’ve already placed the order out of band (phone, supplier portal, in person) and want Logistified to track it from here on. This manual path does not require a supplier email address. Both options move the PO to Sent; the difference is whether an email goes out. Sending via Logistified is all-or-nothing. The order moves to Sent only once the supplier email has actually been recorded. If anything goes wrong (an address the provider rejects, a failure generating the attachment) the order stays in Draft with nothing in its Email History, so you can fix the problem and simply send again. (The attachment is prepared just before the transition, so the PDF or spreadsheet the supplier receives already shows the Sent badge and today’s sent date, even though the order was technically still Draft when it was generated.) Dropship POs created from a Shopify order are always sent with a PDF, built at the moment you send it with the customer’s current name and delivery address from Shopify. Logistified keeps no copy of that PDF; it exists only until the email is delivered, so Re-Send Email builds a fresh one each time and doesn’t offer the existing attachment. Shopify has approved Logistified’s access to these names and addresses. If the address can’t be read, nothing is sent and the message tells you why. A first send leaves the order in Draft; a failed resend leaves its status unchanged. Use Enter address manually instead on the order to send it with a typed address. Each send is recorded in the Log card’s Protected data access section. See [Dropship POs → Delivery details from a Shopify order] (/features/supply-orders/purchase-orders/dropship/#delivery-details-from-a-shopify-order). If your connection drops mid-send, Logistified won’t guess: it tells you the connection dropped before an answer came back and asks you to reload the order: if it still shows Draft, send again; if it shows Sent, the email is on its way. An order somebody else has already marked as Sent can’t be sent a second time through this path; use Re-Send Email instead. ## What gets emailed (Send via Logistified) Three pieces: - Subject: from the configured email template (Settings → Purchase Orders → Email Templates). - Body: from the same template. Supports placeholders like supplier name, PO number, your shop name. You can override the template per supplier. - Attachment: the supplier-facing PDF (PO number, addresses, line items, totals, payment terms). The PDF layout comes from the export template linked to the email template; pick a column set, date-field mapping and labels, your logo, etc. via [Settings → Purchase Orders → Export] (/features/supply-orders/purchase-orders/settings/#export-templates-csv--xlsx--pdf). The To and CC fields accept multiple addresses; add or remove recipients as chips before sending. To pre-fills in this order: the recipients of the previous send (when you resend), then the per-order supplier address’s email if this PO carries a custom supplier address, then the supplier’s [default email recipients] (/features/suppliers/directory/#default-email-recipients), then the supplier’s Email field; CC pre-fills from the email template’s CC list plus the supplier’s default CC recipients. If a supplier has default To recipients beyond the single address shown, the Supplier & Location card on the PO detail page shows a “+N default recipients” hint; hover it to see the full list before you open the send dialog. ## Supplier instructions Supplier instructions is a free-text note that travels with the whole PO: your message to the supplier about the order as a whole (delivery requirements, packaging, where to call on arrival). It’s a single PO-level field, distinct from the per-line Notes column on the line-item table. - Where to edit: open the PO → Notes & Activity Log tab → Supplier Instructions. Type your note and click Save instructions. The same note also sits on the Order Information card as a Supplier Instructions row; click it to read the full text or edit it there without leaving the overview (it reads Add supplier instructions… while empty). Unlike the rest of the PO, this field stays editable even after the PO reaches a terminal status (Completed or Cancelled), useful for adding a final note (e.g. “receipt attached”) after the order is closed. - Filled automatically on import: when you create a PO from a CSV / XLSX or Stocky import, free-form fields the file carries (such as the raw shipping method and shipping terms) are captured here as plain text, one line each. - On the PDF: supplier instructions print on the supplier-facing PDF only when the linked export template has Include supplier instructions turned on. It’s off by default, so existing templates are unchanged until you enable it. See [Exports → Custom column sets and export templates] (/features/supply-orders/purchase-orders/exports/#custom-column-sets-and-export-templates). ## Email delivery status After sending, the Email History card on the PO detail page (Documents tab) shows the email’s [delivery status] (/reference/glossary/#email-delivery-status). Possible states: - Queued: accepted by Logistified, about to be sent. - Sent: handed to the email provider. - Delivered: the recipient’s server accepted it. - Delayed: delivery is temporarily delayed; the provider retries automatically. - Bounced: the recipient’s server rejected it. - Spam Report: the recipient marked the email as spam; future emails to that address may be blocked. - Failed: never accepted. The status updates automatically as the provider reports back, usually within a minute or two of sending. ## Resending Resending is done from the PO’s Actions dropdown; look for Re-Send Email. It’s available in every non-Draft, non-terminal status: Sent, Partially Confirmed, Confirmed, In Progress, Partially Received, Received, On Hold, Disputed. Each resend logs a new row in the Email History card; the PO doesn’t change status. The Email History card itself is read-only; it shows the delivery history but doesn’t have its own resend button. ## What you must have set up For Send via Logistified to be available, email sending must be configured. If it isn’t, the option is greyed out and the dialog tells you what to fix. 1. Settings → Email Sending: fully configured. The dialog checks that you have: - An email prefix (this provisions your prefix@logistified.app sender address), - At least one reply-to address, and - A sender name set. Without all three, no PO can email. Configure once per shop. 2. PO email template configured. Sensible defaults ship; customise via Settings → Purchase Orders → Email Templates. 3. An export template linked to that email template. The send dialog builds the PDF attachment from it, and blocks sending with “No export template assigned to email template” if the selected email template has none. A blank subject blocks sending too. A supplier email address is no longer a prerequisite; if the supplier has no email or default recipients set, the To field opens empty and you type an address by hand. Sending is blocked inline until every address in the To and CC fields is valid. Mark as Sent (Manual) does not require a supplier or supplier email address. It still follows the normal PO checks, such as being in a sendable status and having the required destination/location details for inventory tracking. Use it when you don’t have email sending wired up yet, or when the order was placed outside Logistified. ## Supplier confirmation paths After the PO is Sent, you need to record the supplier’s confirmation so the system can move toward Confirmed. Two paths exist today: - Confirm Manually (per-line, partial allowed). Open the line-item confirmation dialog from the Actions menu under Confirm Items. Enter the confirmed quantity per line, or untick a line to record it as unconfirmed (its confirmed quantity goes back to zero). The PO moves to Partially Confirmed automatically when the first line flips, and to Confirmed when the last one does. The dialog records confirmed quantities only; rejected and cancelled quantities are entered later, from the receive dialog or Bulk Edit, once the PO reaches In Progress. - Quick Confirm. A one-click action in the Actions menu under Confirm Items that confirms every line at its full ordered quantity (including lines you had already confirmed short, whose confirmed quantity is raised back to ordered) and moves the PO straight to In Progress. Useful when the supplier confirmed everything verbally and you don’t need to record line-by-line detail. ### Searching, sorting, and grouping the Confirm Items dialog On a PO with many lines, the Confirm Items dialog can be searched, sorted, and grouped by vendor using the same controls as the [receive dialog] (/features/supply-orders/purchase-orders/receiving/#search-sort-and-group-a-large-receive-table): - Search: type a product title, variant title, or SKU into the search box. A count beside it reads Showing 3 of 12 items while a search narrows the list (just 12 items otherwise). - Group by: a dropdown next to the search box, offering None or Vendor. Each vendor gets its own header row with the vendor name and how many visible items it holds; lines with no vendor on record land in a No vendor group at the end. Groups always list alphabetically, and whatever sort is active still applies to the rows inside each group. - Sort: click Product, SKU, or Ordered to sort ascending, click again for descending, and a third time to drop the sort and return to the order’s own line-item order. Product can be read as Product title or Variant title; use the small arrow next to the header to choose. The Confirmed and Qty columns aren’t sortable; they’re the checkbox and quantity you’re actively filling in, not fixed data. - Search, sort, and grouping reset each time the dialog opens to whatever you’ve saved under [Preferences → Dialog group and sort defaults] (/features/supply-orders/purchase-orders/preferences/#dialog-group-and-sort-defaults), or to the order’s own line-item order if you haven’t set one. Search, sort, and grouping only change what’s visible; every line’s entered confirmation still saves, whether or not a search or group is currently hiding it. ## See also - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): the Sent transition’s full effects (including the incoming push at Sent, when incoming tracking is on). - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): the next step after confirmation, including the matching search/sort/group controls in the receive dialog. - [Preferences] (/features/supply-orders/purchase-orders/preferences/#dialog-group-and-sort-defaults): saving a default group and sort for the Confirm Items and Receive Quantities dialogs. - [Settings] (/features/supply-orders/purchase-orders/settings/): email templates, per-supplier overrides, and the linked export-template-for-PDF. Last updated: 16 October 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/shipments/ # Shipments Track one or more physical deliveries against a purchase order: carrier, tracking, status, and which line items are in each. A Logistified purchase order can arrive in more than one physical delivery: a split container, a back-order, part of the order sent ahead of the rest. The Shipments card on the Payment & Delivery tab of the PO detail page records each delivery separately: carrier, tracking number, status, dates, weight, package count, and (optionally) exactly which line items (and how many units of each) are in that particular delivery. Shipments are informational. Recording one doesn’t move inventory or change the order’s status; that still happens through [Receiving] (/features/supply-orders/purchase-orders/receiving/). Shipments are available on every plan. ## On this page - Adding a shipment - Assigning line items to a shipment - Editing and deleting a shipment - Tracking and viewing items - Receiving straight from a shipment - Where shipments show up elsewhere - See also ## Adding a shipment On the Payment & Delivery tab, click Add Shipment on the Shipments card. The form covers: - Carrier: pick from your configured [carriers] (/features/settings/carriers/), or leave it as None. - Tracking Number: once you’ve picked a carrier that has a tracking-link template and entered a tracking number, the dialog shows a clickable Tracking URL Preview so you can check the link before saving. A carrier without a template (the built-in Other) never shows one. - Shipping Method: Express, Standard, Economy, Freight/LTL, or Pickup (or None to leave it unset). - Status: Pending, Label Created, Shipped, In Transit, Out for Delivery, Delivered, Exception, or Returned. A new shipment starts as Pending. - Shipped Date, Estimated Arrival, and Delivered Date. - Weight (kg) and Package Count (defaults to 1). - Notes: free text. You can add as many shipments as an order needs. They’re numbered Shipment #1, #2, … in creation order; the numbers are positions, not fixed labels, so deleting a shipment renumbers the ones after it. Shipments can be added, edited, or deleted only while the order isn’t Completed or Cancelled; on those orders the card is read-only. Note On stores set up before multi-shipment support shipped, adding a second shipment to an order can be refused with an error saying the store’s database hasn’t been migrated for multiple shipments yet. The first shipment on any order always works, and recently created stores never see this. If you hit it, contact support to have your store upgraded. Shipping details can also arrive from a file. If a freight forwarder sends you a spreadsheet covering several purchase orders, the purchase-order list’s [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/) action can carry a tracking number, carrier, shipped date and estimated arrival per order alongside the line delivery dates. An order with no shipment yet gets one created (Pending, with no line assignments); an order with one shipment has it updated; an order with several has the shipment whose tracking number matches the file updated. ## Assigning line items to a shipment The add/edit dialog’s Items in this Shipment section is optional; a shipment doesn’t need to list what it carries. When you do assign items, the table shows every line on the PO with six columns: - Product and SKU: which line it is. - Ordered: the line’s ordered quantity. - In other shipments: units of that line already assigned to the order’s other shipments. - Remaining: Ordered minus what’s assigned elsewhere (never shown below zero). - This shipment: the quantity you’re assigning here. Leave a line blank (or 0) to leave it out of this shipment. A shipment doesn’t have to cover every line, and a line can be split across shipments however you like. On longer orders (more than five lines), a search box filters the table by product, variant, or SKU. Select all fills every empty visible row with its Remaining quantity and Clear all empties them; while a search is active they act only on the matching lines and relabel accordingly (e.g. Select 3 found). Quantities must be whole numbers of 0 or more; that’s the only thing that blocks saving. Assigning more than a line’s ordered quantity across shipments is allowed: the dialog shows an Over-allocation notice instead of blocking, and the shipment carries an Over-allocated badge on its card. It’s a flag for you to review, nothing more; shipments never affect receiving. ## Editing and deleting a shipment Each shipment’s ⋯ menu offers Edit shipment and Delete shipment. Editing reopens the same dialog with all details and line-item assignments filled in. Deleting removes the shipment and its line-item assignments after a confirmation; receiving records are not affected, and a deletion can’t be undone. ## Tracking and viewing items Two buttons appear on a shipment when they have something to show: - Track: opens the carrier’s tracking page. It appears when the shipment has a tracking number and a carrier whose tracking-link template is set (see [Settings → Carriers] (/features/settings/carriers/)). The built-in Other carrier has no template, so shipments on it don’t get a Track button. - View items: appears when line items are assigned. It lists product, SKU, and quantity for every assigned line, with a total, and flags any over-allocated line. Each shipment also shows an at-a-glance summary: status, tracking number (or “No tracking”), assigned units and lines, shipped/ETA/delivered dates, weight, shipping method, and the package count when there’s more than one. ## Receiving straight from a shipment A shipment shows a Receive button when the order is in a receiving status (In Progress, Partially Received, or Received), the shipment has line items assigned, and it isn’t already marked Delivered. Clicking it opens the standard [receive dialog] (/features/supply-orders/purchase-orders/receiving/#the-receive-dialog) prefilled with the shipment’s quantities, capped per line at what’s still receivable, so you don’t re-type quantities you already recorded on the shipment. Adjust anything that differed from what actually arrived, then confirm. Confirming the receipt also marks the shipment Delivered; if that status update fails for any reason, the receipt itself still goes through. Caution Two things work differently from a plain manual receive. The prefill cap is against confirmed quantities; “still receivable” means confirmed minus what’s already received, rejected, or cancelled, so on an order whose lines haven’t been confirmed yet, the dialog opens empty; confirm quantities first. And the dialog doesn’t autosave in this mode: closing it discards your adjustments. Clicking Cancel asks you to confirm first; pressing Escape or using the × closes without asking. Because a Delivered shipment loses its Receive button, receiving against the same shipment a second time means editing its status back off Delivered first. ## Where shipments show up elsewhere - The Order Information card’s header includes a shipments tile: the first shipment’s carrier plus a count when there are more (e.g. “FedEx +2 more”), a plain count when no carrier is set, or “No shipments”. Clicking it jumps to the Payment & Delivery tab. On orders with a linked Xero bill, the accounting link takes that slot instead. - A connected AI assistant with write access can list, add, edit, and delete shipments too; see [What the assistant can read] (/features/agent-access/what-the-agent-can-read/) and [Operating purchase orders] (/features/agent-access/operating-purchase-orders/#shipment-management). ## See also - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): the receipt flow that shipments can prefill. - [Settings → Carriers] (/features/settings/carriers/): the carrier list and tracking-link templates. - [Update lines from a file] (/features/supply-orders/purchase-orders/bulk-line-update/): filling in tracking, carrier and shipment dates for many orders at once. - [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): what does and doesn’t happen automatically. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/receiving/ # Receiving stock Record stock arriving against a PO: full and partial receipts, inventory effects, discrepancies, label printing. Receiving is the most-frequent operator action on Logistified purchase orders in flight. This page covers the two ways to receive, what changes in Shopify, how to record discrepancies the right way, and how to print labels for the receiving station. Note On a [dropship PO] (/features/supply-orders/purchase-orders/dropship/), one shipping straight to a customer’s address, receiving is relabelled “Mark Delivered” and doesn’t push to Shopify inventory. The separate, optional [Compensate Inventory] (/features/supply-orders/purchase-orders/dropship/#compensating-shopify-inventory) action offsets stock deducted when the customer’s order was fulfilled. Dropship POs are also left out of the list page’s bulk Auto-receive; mark them delivered individually from the order’s own detail page. Note On a PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/), the wording stays “receive” (the goods really do become your stock) but it says where: Receive at Supplier, and a stepper that reads Received at supplier. Nothing pushes to Shopify inventory until a [supplier stock release] (/features/supply-orders/supplier-stock-releases/overview/) brings the stock into a location. These orders are also left out of bulk Auto-receive and of POS receiving; receive them from the order’s own detail page. ## On this page - Two ways to receive - The receive dialog - Receiving from a shipment - What happens to inventory - Fulfillment mode changes the receive behavior - The Receipts sub-tab - Discrepancies on receipt - Recording short shipments and refusals the right way - Labels for the receiving station - Automatic status changes - Bulk auto-receive from the list - Partial receive across several orders - See also ## Two ways to receive - Receive Manually: opens a dialog with one row per line; enter what arrived per line and confirm. Use for partial receipts, multi-day arrivals, or when you want operator control. This records the receipt in Logistified first. Shopify on-hand is updated only if Auto-sync is enabled, or when you later click Sync to Shopify. - Quick Complete: a single action that receives every confirmed quantity in full, syncs warehouse receipts to Shopify, and marks the PO Completed. Use when everything arrived exactly as confirmed and you want one click to close it out. A confirmation dialog summarizes exactly what’s about to happen (full receive, Shopify sync (or a note that sync is blocked, if that preference is on), and the Completed status) before it runs. A third button (Sync to Shopify) appears separately on the actions menu once the order is Partially Received or Received (and on a Completed order that still has unsynced lines). It is not offered while the order is only In Progress. Click it to push the current warehouse receipts to Shopify after a manual receive. This is the same sync step that runs automatically when Auto-sync is enabled. Note Quick Complete, Auto-sync, and manual Sync to Shopify require a Shopify-backed destination location on the PO. If the PO does not have a syncable location, record the receipt manually first and fix the location before syncing. Quick Complete also needs at least one line with a confirmed quantity; if nothing on the order has been confirmed yet, it’s refused with a message pointing you back to Confirm. ## The receive dialog Opens via Receive Manually as the Receive Quantities dialog. Every line appears as a row with five columns: Product, SKU, Accepted, Rejected, and Total. - Accepted and Rejected are the two quantity inputs: units you’re accepting into stock, and units you’re rejecting. Each input has an All shortcut that fills in the line’s remaining pending quantity, and shows any previously recorded amount underneath (prev. received / prev. rejected), so you only ever type this delivery’s numbers. - Total shows how many units have been processed against the confirmed quantity. Hover it for a Quantity Breakdown card listing Ordered, Confirmed, Received, Pending, Rejected, and Cancelled, including any overage. - SKU shows the shop SKU, falls back to the supplier SKU when the shop SKU is empty, and shows a dash when there’s neither. Along the bottom: Accept All Pending fills the Accepted input on every line that still has pending units, in one click. Tick Print Labels to print labels for the accepted units as part of confirming (see Labels for the receiving station below). Confirm Receiving saves the receipt; it stays disabled until at least one quantity is entered. If your entries exceed a line’s confirmed quantity, an Over-Receipt / Over-Reject Notice appears listing the affected lines; the receipt is still allowed (see Discrepancies on receipt below). Each confirmed receipt advances the line’s received quantities and, depending on whether other lines are outstanding, may transition the PO (see Automatic status changes below). Note On a line you’ve split into several [delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/), there’s still one quantity to type per line; Logistified fills the earliest-dated delivery first, then the next, and so on, the same way it always has for that line. Unsaved entries are never lost. Whatever you’ve typed (including scan counts from Scan Items) is saved automatically while the dialog is open. Closing it by accident (Escape, clicking outside, or the ×) doesn’t discard your progress: reopen the dialog and it restores what you had, with a notice offering to discard it if you’d rather start fresh. Cancel is the one close that asks first: Keep draft keeps your entries for next time, Discard draft throws them away. Confirming the receipt clears the saved progress. (One exception: when the dialog opens prefilled from a shipment, this autosave is off; see Receiving from a shipment below.) If quantities changed while the dialog was open (someone received on another device (for example POS) or in another tab), nothing is saved. The dialog says what moved, for example “Quantities changed since you opened this dialog: SKU-1 now shows 13 received. Nothing was saved. The quantities are refreshed and your entries are kept; review them and receive again.” Unreceive Quantities works the same way (“Nothing was changed.”), so it never reverses a receipt that landed after you opened it, and receiving never overwrites one. If the numbers of a line you selected for unreceiving change while the dialog is open, the dialog shows the new numbers (for example “SKU-1 now shows 15 received, 12 synced (was 10 received, 10 synced)”) and waits until you choose Use the new quantities. After receiving, the confirmation tells you when Shopify was not fully updated: Received: Shopify inventory not fully updated, with the reason per item and “The receipt is saved. Use Sync to Shopify for the items that failed.”, and keeps notes such as “Shipment marked as delivered.” on a clean receive. Scan Items turns each successful scan into a received-quantity count for that line. With the scan field empty, press Enter to add one more unit to whichever item you last scanned, or Backspace/Delete to remove one, both without leaving the scan field, so a scanner gun can keep firing. Removing the last unit un-scans the item entirely. A hint under the scan field shows these two shortcuts whenever there’s a last-scanned item to adjust. A scan matches a line’s SKU, supplier SKU, or the barcode recorded on the order, and also the current barcode in Logistified’s product data synced from Shopify, so a barcode changed after the order was placed can still scan correctly. Opening the scanner refreshes these aliases from Logistified’s catalog, and Refresh barcodes repeats that read while you work. The barcode stored on the purchasing document stays unchanged. If a scanned code matches more than one item on the order, Logistified won’t guess: the scan screen lists how many scans need a choice, with a dropdown per code to pick the right item, or a Remove button to drop that scan instead. Apply scanned stays disabled until all unresolved scans have been assigned, successfully retried, or removed. This also applies to unrecognised labels and to pending choices whose barcode matches change after a refresh. ### Search, sort, and group a large receive table On a PO with many lines, the receive table can be searched, every column sorted, and rows grouped by vendor: - Search: type a product title, variant title, SKU, or supplier SKU into the search box. The placeholder only mentions product, variant, and SKU, but the supplier SKU is matched too. Multiple words all have to match somewhere on the row, in any order, so “blue widget” finds “Widget / Blue” regardless of which field holds which word. A count beside the box reads Showing 3 of 12 items while a search is narrowing the list (just 12 items otherwise), and an × inside the box clears it. - Group by: a dropdown next to the search box, offering None or Vendor. Grouped by vendor, each group gets its own header row with the vendor name and how many visible items it holds; lines with no vendor on record are collected into a No vendor group at the end. Groups always list alphabetically, and whatever sort is active still applies to the rows inside each group. - Sort: click a column header to sort ascending, click again for descending, and a third time to drop the sort and return to the order’s own line-item order. The header row stays pinned while the table scrolls, so the controls remain reachable on a long PO. - Product, SKU, and Total each offer more than one reading; use the small arrow next to the header to choose. Product can sort by Product title or Variant title; SKU can sort by SKU shown (whatever the column displays), Shop SKU, or Supplier SKU; Total can sort by Completion (how complete the line is), Outstanding (units still to arrive), or Overall (the full confirmed quantity). Picking a different reading starts it ascending; a checkmark in the menu and the header’s hover tooltip both show which reading is active. - Hovering a product’s name shows a tooltip with the product title, variant title, and SKU together, handy when a long name is wrapped across several lines. Hovering the SKU cell shows the full SKU. Two things to know: - Sorting by quantities is a snapshot. Sorting by Accepted, Rejected, or Total won’t re-order rows underneath you as you type; click the header again to re-sort with the new numbers. - Search, sort, and grouping reset each time the dialog opens: to whatever you’ve saved under [Preferences → Dialog group and sort defaults] (/features/supply-orders/purchase-orders/preferences/#dialog-group-and-sort-defaults), or to the order’s own line-item order if you haven’t set one. You can still change any of the three inside the dialog; it just won’t be remembered for next time unless you update the preference. Search, sort, and grouping only change what’s visible. Every line you’ve entered a quantity for still saves when you click Confirm Receiving, and Accept All Pending still fills every pending line, whether or not a search or group is currently hiding it. ## Receiving from a shipment If you’re tracking [shipments] (/features/supply-orders/purchase-orders/shipments/) on the order, each shipment with line items assigned shows its own Receive button while the order is in a receiving status, until that shipment is marked Delivered. It opens the same receive dialog, prefilled with the shipment’s quantities capped at what’s still receivable per line, so you don’t re-type quantities you already recorded on the shipment. Adjust anything that differed from what actually arrived, then confirm as normal. Confirming the receipt also marks the shipment Delivered; if that status update fails, the receipt itself still goes through. Two differences from a plain manual receive: - The prefill is capped by confirmed quantities. “Still receivable” means confirmed minus what’s already received, rejected, or cancelled; on an order whose lines haven’t been confirmed yet, the prefill comes up empty. Confirm quantities first. - No autosave in this mode. Closing the prefilled dialog discards your adjustments. Clicking Cancel asks you to confirm first; pressing Escape or using the × closes without asking. ## What happens to inventory Receiving affects three inventory numbers in different ways: - Logistified received quantity updates when you save the receipt. - Shopify on-hand updates only through Quick Complete, Auto-sync, or Sync to Shopify. - Shopify incoming is reconciled when Logistified syncs with Shopify. Until then, Shopify may still show the earlier incoming amount even though the receipt is already recorded in Logistified. Event Logistified record Shopify effect PO moves to Sent Ordered quantity is now expected from the supplier. Incoming is pushed, if incoming tracking is enabled. On-hand unchanged. Lines confirmed Confirmed, cancelled, or rejected quantities are saved. Incoming is reconciled to the remaining expected quantity. Line received via Receive Manually Received quantity is saved locally. No on-hand push unless Auto-sync is on. Incoming is reconciled when Auto-sync or manual Sync to Shopify runs. Line received via Quick Complete Confirmed quantities are received in full. On-hand is pushed and incoming is reconciled as part of the completion flow. PO cancelled / line cancelled Outstanding quantities are closed out. Pending incoming is rolled back, if incoming tracking is enabled. PO Reopened (from Completed) The PO returns to the appropriate receiving status. Outstanding incoming is pushed again if there are still units expected. The difference between Receive Manually and Quick Complete is whether the Shopify sync happens as part of the action. The [Auto-sync to Shopify on receiving] (/features/supply-orders/purchase-orders/preferences/#auto-sync-to-shopify-on-receiving) preference makes Receive Manually run the same Shopify sync step after every save. If Shopify’s incoming doesn’t match what Logistified shows, run [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). Drift is usually caused by a transient sync failure. The inventory effects table above describes the Deliver to warehouse fulfillment mode, the default and most common. Lines on other fulfillment modes behave differently; see below. ## Fulfillment mode changes the receive behavior Each line item carries a [fulfillment mode] (/features/supply-orders/purchase-orders/line-items/#fulfillment-mode-per-line). The receive step does different things depending on the mode: Line mode Where the receipt lands Shopify on-hand pushed? Deliver to warehouse Warehouse stock at the PO’s destination location. Yes: via Quick Complete, Auto-sync, or manual Sync to Shopify, when the destination is a Shopify-backed location. Hold at supplier Buyer-owned supplier-held stock position. No. Shopify on-hand is not updated. To bring this stock into a warehouse later, create a [Supplier Stock Release] (/features/supply-orders/supplier-stock-releases/overview/). Warehouse consignment Warehouse stock at the PO’s destination location, plus a supplier-owned consignment stock position. Yes: consignment lines take part in the on-hand sync exactly like warehouse-delivery lines. Only supplier-held lines are held back. Mixed-mode POs are supported: a single PO can have warehouse-delivery lines, supplier-held lines, and consignment lines side by side. Each line follows its own fulfillment mode when you receive it. The one exception is a PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): every line on it is Hold at supplier, and the mode can’t be changed per line; the receiving supplier holds the whole order. ## The Receipts sub-tab Switch the line-item table to its Receipts tab and each line collapses to one summary row: last receipt date, net quantity received, available stock at this PO’s delivery location, a progress bar, an overall sync state, and the receipt count. Available reads from the same Shopify sync as the Inventory view, so a dropship or deliver-to-supplier order (no delivery location) and a custom item (no Shopify variant) both show it as not applicable. Click the receipt count to expand the line into one row per receipt. Each receipt row shows: - The date the receipt was booked - Quantity received: a reversal (unreceive) shows as a negative quantity - A fulfillment-mode badge, shown only when that receipt’s mode differs from the line’s own mode - Shopify sync status: synced, pending, syncing…, sync failed, cleared, reversed, or not needed (supplier-held lines) Use this view to audit when each receipt was booked and whether it has reached Shopify. ## Discrepancies on receipt - Under-receive. Enter the actual quantity. The remainder stays as pending; you can receive more later, or close out the difference by cancelling the missing quantity (see below). - Over-receive. Enter what actually arrived, even if it is more than the confirmed quantity. Logistified allows the receipt and flags the line as over-received so you can review the supplier invoice, cost, and follow-up decision. If the extra units should become part of the commercial order, adjust the confirmed quantity in Bulk Edit too. ## Recording short shipments and refusals the right way The cleanest way to close out a discrepancy is on the order side, not the receive side. Two operator-driven quantities exist for exactly this: - Qty Cancelled: set during the confirm flow or via Bulk Edit. Use when you decide not to take the rest of an order: the supplier delayed, you don’t need it any more, you found it cheaper elsewhere. - Qty Rejected: set during the confirm flow. Use when the supplier refused to ship the line: out of stock, MOQ not met, etc. Both quantities subtract from “pending,” so once you’ve cancelled or rejected the difference, the PO can complete cleanly without artificially under-received lines lingering. Tip Prefer recording the discrepancy at the right time: cancelled/rejected at confirmation, received during receipt. Receipt corrections are available, but the cleanest audit trail comes from separating supplier refusals, operator cancellations, and actual arrivals. ## Labels for the receiving station Print per-line labels for the boxes you’re receiving: barcode, SKU, variant title, quantity. From the PO Actions menu → Print Labels. The dialog supports: - PDF with two layout modes: Simple (rule-based, ships out of the box) and Designer (Beta) (template-based, defined in label-printing settings). - CSV / XLSX export of the same label data: one row per SKU (aggregated) or one row per label (expanded). Useful when feeding a label printer or warehouse system from a flat file. The label sheet format is configured at [Settings → Label Printing] (/features/settings/label-printing/); see also [Exports → Label sheet PDFs] (/features/supply-orders/purchase-orders/exports/#label-sheet-pdfs). Useful for warehouses where receiving is barcode-scan driven; labels go on the boxes, the receiver scans them in. ## Automatic status changes - Receiving the first line → PO moves to Partially Received. - Receiving the last line (full receipt) → PO moves to Received. - Received POs can still be corrected with Receive Manually, Unreceive Quantities, or Bulk Edit for received quantities. Bulk Edit checks received and rejected quantities the same way: if a line (or one of its deliveries) changed since you typed, those cells go back to the current numbers, the message names what moved and what you typed, and your other edits stay in the editor. - Marking Completed is an operator choice; you don’t have to. You can stay at Received indefinitely if that’s useful (e.g., before invoicing closes the loop). - Completed and Cancelled POs are locked. Reopen first if you need to continue working a Completed PO. - From Completed, you can always come back via Reopen Order; Logistified picks the right target status (Received / Partially Received / In Progress) based on what was actually received. Caution If a receipt was entered incorrectly, correct the received quantity from the receive tools instead of cancelling the PO. Use Unreceive Quantities where available, or adjust the received quantity in Bulk Edit. ## Bulk auto-receive from the list Receiving isn’t limited to one order at a time. On the purchase orders list, select one or more orders, open the selection Actions menu, and choose Auto-receive. Logistified plays each selected order forward (one at a time) without you opening every order’s detail page. Useful for a delivery that covers many POs at once. The first step asks what arrived: - Full receive: receive all remaining quantities on every eligible order. Use this when the delivery matches what you ordered. - Partial receive: build one receipt for exactly what turned up, spread across the selected orders. Use this for a truck carrying part of several orders. See [Partial receive across several orders] (#partial-receive-across-several-orders) below. ### Full receive Logistified plays each selected order forward to Received, or all the way to Completed if you choose that option. The dialog checks every selected order as soon as it opens and shows three counts: how many are ready, how many will be skipped, and how many are rejected, plus the specific reason next to any order that can’t run. Two options apply to the whole run and update every order’s preview instantly when you change them: - End state: Receive only (stop at Received / Partially Received) or Receive and complete (also complete each order, the same end state as Quick Complete). - Update Shopify inventory: pushes on-hand to Shopify for each order as it’s received, the same push Auto-sync or Sync to Shopify perform. It starts on or off based on your [Auto-sync to Shopify on receiving] (/features/supply-orders/purchase-orders/preferences/#auto-sync-to-shopify-on-receiving) preference, and is locked off with a warning if [Block sync to Shopify] (/features/supply-orders/purchase-orders/preferences/#block-sync-to-shopify) is on. Nothing is sent to any order until you click Run. ### Why an order is skipped or rejected - Skipped: the order is already fully received; there’s nothing left for auto-receive to do. - Rejected: the order fails one or more checks. Every problem is shown at once, so you can fix everything before trying again: - Not yet Confirmed (still Draft, Sent, or Partially Confirmed), or on hold, disputed, or cancelled. - Marked Confirmed overall, but has lines the supplier never actually confirmed a quantity for. - Missing a location or a supplier. - Nothing left to receive: no lines, or every unit already rejected or cancelled. - A receiving discrepancy that Logistified’s normal validation would also refuse. - With Update Shopify inventory on: a line Logistified can’t identify in Shopify well enough to push safely, or an order that already has a Shopify sync in progress. A rejected order is left completely untouched; auto-receive never partially processes an order it has flagged. ### Running, stopping, and results Orders are processed one at a time, so a problem with one never blocks the rest. Each order lands in one of these outcomes: - Received / Completed: succeeded cleanly. - Needs attention: the receipt itself went through, but a follow-up step (such as the Shopify push) failed; the summary explains what to check. - Failed: the order couldn’t be processed; the summary explains why and what status it was left at. - Skipped: already fully received. - Rejected: failed validation; nothing was changed on that order. You can click Stop after current order partway through a run; the order in progress finishes normally, and every order after it is left untouched and marked Not run so you can pick up later. Closing the dialog is blocked while a run is in progress. When the run finishes, a summary reports how many orders landed in each outcome, and the list refreshes to show every order’s current status. ### Partial receive across several orders Choose Partial receive on the first step when only part of the delivery arrived, or when one delivery covers several orders. Logistified reads what’s still outstanding on each selected order, then you build a single receipt three ways; you can mix all three: - Scan: scan a barcode or SKU with your usual scanner. Each scan adds one unit. Press Enter on an empty box to add another unit of the last item you scanned. - Browse lines: search the selected orders’ lines and type quantities straight into the table. - Upload CSV/XLSX: upload a count sheet. Each row needs a SKU or barcode and a quantity. A PO number column is optional: include it and the row goes straight to that order; leave it out and Logistified works out which order the item belongs to. An order that can’t take part (not confirmed yet, on hold, missing a location or supplier, nothing left to receive) is listed with the reason before you start, so you know what the receipt can and can’t cover. When an item could belong to several selected orders, the app asks you to pick. Those scans are held in a short “needs a purchase order” list with a button per order showing how many units it still has room for; one click assigns them. Nothing is counted for that item until you pick, and you can’t move on to the review step while anything is still waiting. If the same item appears on several lines of the same order, Logistified fills them in order automatically and never asks. Nothing is ever over-received. Quantities are capped at what each line still has outstanding: typed and uploaded quantities are trimmed to fit (uploaded rows say so), and a scan of an item where every selected order is already fully received is refused with a message rather than counted. A code that isn’t on any of the selected orders is refused too. The Review step shows each order with the units and lines it will receive and the status it will land on. Two things to check there: - Complete after receiving: a per-order checkbox that only appears when this receipt would leave that order fully received. It’s off by default; tick it to finish the order off in the same run. Orders that will only be partially received don’t get the checkbox; partial orders can’t be completed. - Update Shopify inventory: the same switch as a full auto-receive run, with the same preference defaults and the same lock when Block sync to Shopify is on. Nothing is received until you press the Receive button on the review step. Up to that point you’re only building a list, and closing the dialog asks before discarding it. The receipt is then applied one order at a time (with the same Stop after current order control) and the finished summary lists every order’s outcome, including any whose quantities were trimmed because someone else received against them while you were counting. Note Auto-receive only acts on the orders you’ve selected; there’s no “auto-receive everything matching this filter.” Selection carries across pages, so you can select orders from more than one page of the list before opening Auto-receive. ## See also - [Dropship POs] (/features/supply-orders/purchase-orders/dropship/): marking delivered and optional Shopify inventory compensation. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): receiving at a second supplier, and what to do with the stock afterwards. - [Shipments] (/features/supply-orders/purchase-orders/shipments/): tracking deliveries and receiving straight from one. - [Line items & costs → Fulfillment mode per line] (/features/supply-orders/purchase-orders/line-items/#fulfillment-mode-per-line): the three modes and where the receipt lands for each. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries, and how a receipt is allocated across them. - [Supplier Stock Releases] (/features/supply-orders/supplier-stock-releases/overview/): how to pull supplier-held stock into a warehouse after receipt. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): the receipt-driven transitions. - [Preferences] (/features/supply-orders/purchase-orders/preferences/): Auto-sync to Shopify on receiving, label export format, incoming inventory tracking, and the dialog group/sort defaults. - [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): Shopify push details. - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): fixing drift. - [Exports → Label sheet PDFs] (/features/supply-orders/purchase-orders/exports/#label-sheet-pdfs): Simple vs Designer modes + CSV/XLSX export. - [Exports → Bulk export] (/features/supply-orders/purchase-orders/exports/#bulk-export-csv--xlsx): the other selection Actions menu item. - [Guides → Receive inventory] (/guides/receive-inventory/): end-to-end walkthrough. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/payments/ # Payments & "marked as paid" Recording payments against a PO, and how the operator-set "marked as paid" flag behaves. A Logistified purchase order can carry many payments: deposit plus final payment, multiple wire transfers, mixed currencies. The “marked as paid” flag is operator-set, not auto-derived. This page is the small but important reference for payment workflows. ## On this page - Recording a payment - Multi-payment - The “marked as paid” flag - Counting payment tax and tariff toward paid status - Fully Paid Date - Due Date and the payment-due badge - Currency - See also ## Recording a payment From the Payments card on the PO detail page, click Add Payment. Fill in: - Net Amount and Currency (both required). - Exchange Rate: shown only when the currency differs from your shop currency. - Payment Method: Bank Transfer, Wire Transfer, Credit Card, Debit Card, PayPal, Cash, Check, Letter of Credit, Cryptocurrency, or Other. - Payment Terms. - Transaction Number (the bank reference or your AP system’s number) and Status: Initiated (the default), Pending, Completed, Failed, or Rejected. - Invoice Number, Due Date, and an optional link to an already-uploaded Invoice Document. - Tax and Tariff: pick a configured tax rate or a duty preset and Logistified derives the amount from the percentage, or type the amount in directly. - Notes. There is no separate “payment date” field; Logistified stamps the date from the status you save the payment with. Save. The Payments card lists every payment and shows the total underneath. Caution Only payments saved with Status: Completed count toward the paid status. A payment left at the default Initiated is recorded and listed, but it does not move the PO toward “fully paid.” On the PO detail page a completed payment also has to be in the purchase order’s own currency to count; a payment recorded in another currency shows in the list and in the totals, but is left out of the paid-status sum. ## Multi-payment Many payments per PO are supported. Useful for deposit + final workflows, or for tracking partial settlements over time. ## The “marked as paid” flag The Payments card has a [Mark as fully paid] (/reference/glossary/#marked-as-paid) checkbox (the same control appears in the PO edit dialog under Payment Status). Important to understand: - It’s operator-set, not automatic. Setting it to “paid” doesn’t validate against the recorded payments total. Setting it to “not paid” doesn’t reverse payments. - It’s a reporting marker, not a financial source of truth. Your finance team’s books are authoritative. - Useful when payment reconciliation happens outside the app, in your bank statement reconciliation or your AP system. So you can have a PO with zero recorded payments but marked as paid (because you reconciled it elsewhere), or a PO with payments summing to the total but not marked as paid (because you haven’t finished reconciling). Both are valid states. ## Counting payment tax and tariff toward paid status Besides the operator flag, recorded payments also drive the paid status: when your completed payments cover the order’s item total (unit cost × quantity across the line items, so shipping, additional costs and order-level tax are not part of the comparison), the PO reads as fully paid. Each payment row can carry a tax and a tariff amount alongside the main amount, and a setting decides whether those count: - Off (the default): only the payment Amount counts toward the total. This is the right mode when you record gross, tax-inclusive figures in the Amount field; counting the tax field on top would double-count the tax. - On: each payment counts as amount + tax + tariff. Turn this on when you record net amounts with the tax entered separately, so a net payment plus its tax still marks the PO fully paid (and stamps the Fully Paid Date) once the order total is covered. The toggle lives at Settings → Purchase Orders → Preferences → “Count recorded payment tax and tariff toward the paid status.” It affects the Paid badge, the paid/unpaid filter, and when the Fully Paid Date is auto-set; pick the mode that matches how you fill in the payment dialog. One exception: the purchase-order CSV export’s amount-paid, outstanding, and paid-status columns always sum the payment Amount fields only (net), regardless of this setting. ## Fully Paid Date The PO edit dialog includes a Fully Paid Date field. It records when full payment was actually settled. It is auto-set the first time the PO becomes fully paid (when you tick “Mark as fully paid,” when recorded payments add up to the total, or, if your shop has [Auto paid when completed] (/features/supply-orders/purchase-orders/preferences/#auto-paid-when-completed) turned on, when the PO reaches Completed), and it is never cleared or overwritten automatically. The auto-set only fills an empty field; a date that’s already there stays put. You can set, change, or correct it by hand. When a Fully Paid Date is recorded, it shows next to the paid badge: the Payments card shows a “Fully paid” badge followed by “on [date],” and the Financial Summary on the order information card shows a “Paid” badge followed by “on [date].” Note Fully Paid Date only records when payment happened; it doesn’t drive any badge. The outstanding-payment badge described below is driven by Due Date instead. ## Due Date and the payment-due badge The PO edit dialog also has a Due Date field: when payment is due. Logistified derives it from the payment terms: - Picking a supplier or payment terms fills an empty Due Date automatically. Net N terms (e.g., Net 30) add N calendar days to the base date: the day the PO was sent, or today for a PO that hasn’t been sent yet. Due on Receipt, Cash in Advance, and Cash on Delivery use the base date itself; End of Month uses the last day of the base date’s month. No terms, or Custom, derives nothing. - Changing the Shipping Date re-derives the due date from the same terms, counted from the new shipping date. - Derivation never silently overwrites: if a different due date is already set, Logistified asks before replacing it, and when the payment terms and the shipping date imply two different due dates, it asks which date to count from. Clearing the shipping date never clears a due date. You can also edit the Due Date by hand to override any derived value. It stays editable in every status (Received, Completed, On Hold, Disputed and Cancelled included), so you can still correct a payment deadline after an order is closed or reopened. (The supplier-facing requested delivery and shipping dates do lock in those statuses.) While the PO is not yet fully paid, the Due Date drives a status badge on the Payments card and the Financial Summary row of the order information card (compared by calendar day in your local timezone): Badge When it shows Outstanding payment (red) The due date has passed Pay today (yellow) The due date is today A due date in the future, or no due date at all, shows no badge; the Financial Summary falls back to its plain “Unpaid” badge, and the Payments card simply shows no payment badge at all until the date becomes actionable. The purchase order list doesn’t show this badge, but it does show the due date itself: any order that’s still open and unpaid displays a Due: line in its Dates column (shown in red once the date has passed), and a draft always shows its own planned due date regardless of paid status. The line drops off the list once the order is marked fully paid or is cancelled. Once the PO is fully paid, the badge is replaced by the paid indicator above. ## Currency The PO’s line items use one currency, inherited from the supplier. Payments are more flexible; each payment can be recorded in any currency, and Logistified converts it to your shop’s currency using an exchange rate per payment. When you add a payment in a currency different from your shop’s currency, the dialog shows an Exchange Rate input. Logistified attempts to auto-fetch the rate from the exchange-rate service; if none is found (or you disagree with it), enter the rate manually. The dialog displays the computed shop-currency equivalent in real time: ``` Exchange Rate (1 SHOP-CURRENCY = X PAYMENT-CURRENCY) ``` Each payment row stores both the original amount (in its own currency) and the converted amount (in the shop currency), so you can reconcile against either side of the books. When every payment shares one currency the Payments card totals in that currency (broken out as Net / Tax / Tariff / Total when any payment carries tax or tariff); as soon as the payments span more than one currency it switches to a single total converted into your shop’s currency. Tip When the supplier issues a single invoice but you pay in instalments at different exchange rates (common for international wires), record each payment with its actual day’s rate. Each row keeps its own currency and rate for supplier-side reconciliation, and the card’s shop-currency total keeps your books accurate. Caution Don’t rely on “Marked as paid” for financial reporting. It’s an operator flag, not an audit trail. Check the actual payment rows for what’s really been recorded. ## See also - [Applying supplier credits] (/features/supply-orders/purchase-orders/credits/): credits work alongside payments to settle the PO total. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): Completed is the natural status after payment. - [Preferences] (/features/supply-orders/purchase-orders/preferences/): where the paid-status toggles live. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/additional-costs/ # Additional costs & discounts Record any number of surcharges and discounts on a purchase order, as fixed amounts (in any currency) or as a percentage of the order value, each with its own optional purchase tax. A purchase order rarely consists of line items alone; freight surcharges, handling fees, early-payment discounts, and one-off rebates all change what you actually owe. Logistified lets you record any number of these entries per PO, each with its own reason, either as a fixed amount or as a percentage of the order’s item subtotal. A fixed entry can be entered in a currency other than the order’s own (customs, brokerage, and final-mile delivery are often invoiced separately from the supplier, in the local currency) and any entry, fixed or percentage, can carry its own purchase tax. ## On this page - Adding a cost or discount - Fixed amount vs. percentage - Entering a cost in another currency - Tax on a cost or discount - Keeping percentage entries up to date - How charges are spread across units - Where the total shows up - Costs billed separately - Order-level vs. line discounts - See also ## Adding a cost or discount On the PO detail page, the Order Information card’s financial breakdown lists each entry with its reason and amount. Click Manage costs & discounts (or Add cost / discount when the order has none yet) to open the editor. For each entry you set: - Calculation: Fixed amount or Percentage. - Amount (fixed entries) or Percentage (%): positive values add costs, negative values apply discounts. A -10 fixed entry or a -2.5 percentage entry reduces the order total. - Cost currency (fixed entries only): defaults to the order’s own currency; pick a different one to record the cost as it was actually invoiced. See [Entering a cost in another currency] (#entering-a-cost-in-another-currency). - VAT / purchase tax: an optional purchase tax rate for this entry, or No tax (the default for new costs; see [Tax on a cost or discount] (#tax-on-a-cost-or-discount) for discounts). - Reason: free text such as “Freight surcharge” or “Customs and delivery”. The reason appears next to the amount in the financial breakdown, on the PO PDF, and as the description of this entry’s line on a pushed accounting bill. You can add, edit, and remove entries from the same dialog for as long as the order is open, and every change immediately updates the order’s totals. Once the order reaches Completed or Cancelled the breakdown becomes read-only: the Manage costs & discounts button no longer appears and the warning badges described below stop being clickable. The Manage button inside the PO edit dialog locks earlier still; it’s also disabled while the order is On Hold or Disputed, even though the card’s own editor still works there. The PO edit dialog shows the combined total as a read-only field with its own Manage button. Clicking it saves any unsaved changes in the edit dialog first, then opens the cost editor. Note If your order carried an additional cost or discount from before this feature existed, it appears automatically as a single fixed entry ; nothing is lost, and you can edit or split it like any other entry. ## Fixed amount vs. percentage - Fixed amount: a signed amount, in the order’s own currency by default or in any other currency you pick. Use it for flat fees, freight, customs charges, and negotiated rebates. - Percentage: a signed percentage of the order’s item subtotal (line items only, before shipping and tax), always calculated and stored in the order’s own currency. While you type, the dialog previews the resulting amount against the current subtotal. When you save, that amount is stored with the entry. ## Entering a cost in another currency Fixed entries don’t have to be entered in the order’s own currency. This is useful for costs a different party invoices separately from the supplier; customs, brokerage, or final-mile delivery often arrive in the local currency rather than the supplier’s. Pick a currency from the searchable Cost currency picker. Once it differs from the order’s currency, an Exchange rate field appears, labeled “1 [source currency] = X [order currency]”. Logistified looks up a live reference rate (European Central Bank reference data) and fills it into the empty field automatically, showing the reference date once one loads. Not every currency has a live reference rate; when none loads, the dialog asks you to enter the agreed rate manually. You can always type over the fetched rate to use the rate you were actually charged; the dialog previews the converted amount as you type. The rate you save (stored to six decimal places) stays attached to the entry; Logistified doesn’t re-fetch or adjust it later. The PO-currency totals, PDF and exports show the saved entry in the order’s own currency. A supplier-billed entry also appears in that currency on the accounting bill. The original amount, currency, and rate stay attached to the entry and are shown alongside the converted amount (on the PO PDF, for example, as “(NZD 115.00 × 0.610000)” next to the reason), so the conversion is always traceable back to what you actually paid. Note If you enter a cost in your shop’s own currency on an order placed in a foreign currency, Logistified keeps that exact amount when it shows the order converted into your shop currency (on the order information card, and in the Shopify cost push) rather than converting it into the order’s currency and back again, which could otherwise drift by a cent or two from what you actually paid. The saved PO-currency amount and your supplier’s totals are unaffected either way. Note If a purchase order’s currency changes after you’ve saved a foreign-currency entry, that entry is flagged with a currency changed warning; the stored conversion still targets the old currency. Click the warning to open the cost editor, then edit that entry; its stored rate is cleared there so you can re-save it with a current rate against the new currency. Percentage entries always stay in the order’s own currency and can’t carry a source currency or exchange rate; for them the editor shows a disabled Snapshot currency field instead. ## Tax on a cost or discount Each entry (fixed or percentage) can carry its own purchase tax, independent of the order’s own [header tax rate] (/features/supply-orders/purchase-orders/settings/#tax-rates). Pick a rate from VAT / purchase tax, or leave it as No tax. Only rates of type Purchase, configured at [Settings → Tax Rates] (/features/settings/tax-rates/), are offered. No tax is the default for new costs (positive entries). A new discount (a negative entry) instead defaults to the order’s own header tax rate, as long as every line item currently counted in the order is taxable; a discount is usually a reduction of the same tax you’re already being charged, so leaving it untaxed can overstate the VAT and total you owe. If the order mixes taxable and tax-exempt lines, or has no header tax rate, new discounts still default to No tax and you choose explicitly. Either way, this only affects a new entry’s starting value; picking a rate yourself, or opening an existing entry, always keeps what’s actually selected. Tax is calculated on top of the entry’s amount (the amount field is always tax-exclusive), and the dialog previews the resulting tax as you type. For a foreign-currency entry, the tax is calculated on the converted amount in the order’s currency. A discount (a negative entry) carries negative tax, which reduces the order’s combined additional-cost tax; leaving a discount as No tax deliberately leaves that tax unchanged instead. The rate is snapshotted onto the entry when you save it. If the rate is later renamed, removed, or its percentage changed in Settings, the entry keeps the rate it was actually taxed at; when you edit the entry, the picker shows that saved rate labeled “· saved snapshot” in place of the live one, and simply re-saving keeps it. Re-selecting the same rate keeps the snapshot too. To move an entry onto a rate’s new percentage, set it to No tax, save, then re-open the entry and pick the rate again. Entries with tax show a rate badge in the financial breakdown (the rate’s saved name plus its percentage, for example “GST 15%”) along with their tax amount. The sum of every entry’s tax appears as its own Additional cost tax line in the order’s financial breakdown and totals whenever the combined tax is non-zero, alongside the combined additional cost / discount amount; the PO list shows it as “(incl. … additional cost tax)” under the grand total. Note Tax recorded on an additional cost is treated as recoverable input tax: it’s included in what you owe, but it isn’t added to your inventory’s landed cost. The entry’s underlying amount still is, when Include additional cost or discount is enabled on the Settings → Purchase Orders → Landed Cost tab. ## Keeping percentage entries up to date A percentage entry is calculated when you save it. If the order’s items change afterwards (lines added or removed, quantities confirmed at different numbers, or goods received, rejected, or cancelled in different numbers), the stored amount no longer matches the percentage. (The subtotal follows the same received → confirmed → ordered basis the rest of the order does, so receiving is the most common reason an entry goes out of date.) Logistified flags such entries with an outdated badge in the financial breakdown; hover it to see what the current value would be, and click it to jump into the editor. Inside the editor, the refresh action (or simply re-saving the entry) recalculates it against the current subtotal. ## How charges are spread across units Landed cost per unit is the unit cost plus the line’s share of shipping, additional costs and discounts, payment tax and tariffs, and (when enabled) purchase tax. Those charges are spread over the units the order is expected to deliver: the confirmed quantity, or the ordered quantity while nothing is confirmed, minus any cancelled or rejected units, and never fewer than the units already received. - Receiving part of an order does not change the per-unit share. With 10 units ordered, 2 received and 100 in shipping, each unit carries 10, not 50. - A landed cost is shown from Draft on, as a projection, so margins on the Landed basis mean something before the first delivery. - Once the order is Completed or Cancelled, nothing more arrives, so the same charges are spread over the units that actually arrived. Closing an order short therefore concentrates the charges on the received units. The completion dialog tells you how many units are still outstanding; if you already ran Update unit cost after an earlier delivery, run it again after completing so Shopify carries the final value. The Update Unit Costs Now button inside the completion dialog already previews on that final basis. - The Landed total under the line items is the goods expected plus every included charge. While fewer units have arrived than carry the charges, a second line shows the landed value received so far. - Purchase tax on a short-closed order is capitalised on the received goods only. Running Update unit cost again never double counts: each run recomputes the order’s valuation from the originally recorded cost and stock, so the newest run replaces the previous one. ## Where the total shows up The sum of all entries’ amounts, and separately the sum of their tax, feed the same places the single additional-cost value always did: - The Grand Total on the PO detail page and in the financial breakdown, plus an Additional cost tax line whenever the combined tax is non-zero. The Grand Total label switches to “Grand Total (incl. tax)” whenever the order carries a header tax rate or a non-zero combined additional-cost tax, and a line beneath it spells out the total tax included. On a foreign-currency order, the Grand Total and Total Due show your shop currency first with the order’s own-currency figure underneath as “PO currency total” / “PO currency due”; if any entry was invoiced in your shop currency, a “Local costs kept in [shop currency]” note appears too. - The PO PDF totals (when “Show additional costs/discounts” is enabled in [PDF preferences] (/features/supply-orders/purchase-orders/preferences/) and the export template’s Hide unit cost option is off): each entry prints its own line with its reason, converted amount, and source-currency detail when it differs from the order’s currency, plus a tax line labeled with the rate’s name for each entry that carries tax. - Exports: the purchase-order-level export includes the combined additional cost / discount column, and a separate Additional Cost Tax column is available. It isn’t in the default column set; add it to a purchase-order-level export template first (Settings → Purchase Orders → Export). Note that the export’s total-cost column excludes tax, header and additional-cost tax alike. - Reporting: the purchase-order-level report offers the combined figure as an Adjustments column. Note that Reporting’s Total cost column does include tax (header and additional-cost tax alike), unlike the export column of the same name described above. - Supplier credit limits: credits can be applied up to the supplier invoice amount, including supplier-billed entries and their tax. Separately billed entries are excluded. - Accounting: a connected accounting system receives one bill line per supplier-billed entry with a non-zero amount (using the entry’s reason as the description, or “Additional cost” / “Discount” when the reason is blank), each mapped to its own tax when one’s configured. If an entry’s tax rate can’t be matched to a rate in your accounting system, the push is blocked until you map it; see [Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/). ## Costs billed separately For a positive additional cost, select Separately billed: landed cost only when another company invoices you for it, such as a local insurer or freight broker. The cost stays in the PO’s total cost and landed-cost calculation. Supplier payable excludes it, as do credits applied to the PO supplier and the supplier Bill exported to accounting. Existing entries remain billed by the PO supplier unless you change this selection. Discounts cannot be billed separately. This option does not create another bill in Xero; record that invoice separately in your accounting system. Once accounting or settlement activity exists, changes that would alter this split may be blocked. Review the linked bill, payments or applied credits before changing the financial records. Duplicating or splitting a PO still copies its cost entries; review those copied charges so the same external invoice is not counted twice. ## Order-level vs. line discounts Everything on this page adjusts the order as a whole: a freight surcharge, an early-payment discount, a rebate on the invoice. To take money off one product instead, put the discount on the line itself: select the lines and apply a percentage or an amount per unit, and the line’s net cost flows into the subtotal that these order-level entries are then calculated against. See [Line items & costs → Line discounts] (/features/supply-orders/purchase-orders/line-items/#line-discounts). Note that a percentage entry here is measured against the item subtotal, so applying a line discount is one of the changes that leaves a saved percentage entry showing its outdated badge until you re-save it. ## See also - [Payments & “marked as paid”] (/features/supply-orders/purchase-orders/payments/): recording what you actually paid. - [Applying supplier credits] (/features/supply-orders/purchase-orders/credits/): settling part of the total with credit. - [Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/): how the order becomes a bill. - [Settings → Tax rates] (/features/settings/tax-rates/): creating and mapping purchase tax rates. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/#line-discounts): discounting an individual line instead of the order. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/documents/ # Documents Uploading and downloading files attached to a PO, quotes, invoices, receipts. Logistified stores documents alongside POs: supplier quotes, supplier invoices, signed receipts, anything else you want to keep with the order’s audit trail. This page covers the upload flow, what Logistified auto-generates, and limits. ## On this page - Uploading a document - Typical document types - What Logistified auto-attaches - Size and format limits - Attaching a document to the Xero bill - Removing a document - See also ## Uploading a document From the Documents card on the PO detail page → Upload new document. An Upload Document dialog opens: drop a file onto the zone or click to browse, then set the Document Type: an autocomplete over the types defined at [Settings → Purchase Orders → Document Tags] (/features/supply-orders/purchase-orders/settings/#document-tags), which also accepts a brand-new type you type in. Click Upload (it stays disabled until a file is chosen). A row then appears in the Documents card with filename, type, size, and upload date. To download it later, click the download icon on the row. ## Typical document types - Supplier quote: PDF, often pre-PO. - Supplier invoice: PDF, post-receipt. - Receipt confirmation: PDF, image, or any other supported format (see the limits below). - Line-item confirmation file: CSV or XLSX from your supplier, mapped to lines via the confirmation flow. ## What Logistified auto-attaches Some documents land in the Documents card without a manual upload: - The supplier-facing attachment. When you send (or resend) the PO, the file attached to the supplier email (PDF, XLSX, or CSV, depending on your attachment format) is saved to the Documents card as type Email Attachment. If the copy can’t be saved, the send fails (and on a first send the PO is rolled back to Draft), so a sent PO always has its attachment on file. - Individual PO exports, optional. The per-PO export dialog (Actions → Export) has an Attach printout to my documents checkbox. Tick it and the PDF / XLSX / CSV you download is also saved here. - Label sheets printed during receiving. Labels generated as part of the receive flow are saved automatically as type Labels. - Label sheets printed from the Actions menu, optional. The Print Labels dialog’s Settings step has a Save labels to PO documents checkbox; tick it before printing a PDF label sheet to also attach the file here (it starts unticked each time the dialog opens). See [Exports → Label sheet PDFs] (/features/supply-orders/purchase-orders/exports/#label-sheet-pdfs) for details. ## Size and format limits - 10 MB per upload. Larger files should be linked from elsewhere. - Supported formats: PDF, images (PNG, JPEG, GIF), Excel (XLS, XLSX), CSV, and Word (DOC, DOCX). The file’s contents must actually match its type; renaming an unsupported file to .pdf won’t get it through. ## Attaching a document to the Xero bill Once the purchase order is linked to a bill in Xero (pushed from the [Accounting card] (/features/supply-orders/purchase-orders/accounting-sync/), or connected to a bill that already existed), every document row gets a paperclip button: Attach to Xero bill. Click it and Logistified sends that file to the linked bill in Xero; a toast confirms “Attached to Xero bill”. This is part of the [Elevate] (/reference/glossary/#elevate-plan) plan. If the order isn’t linked to a bill yet, or the bill was voided, the button doesn’t appear. After attaching, the paperclip shows a check mark. Click it to see when the file was attached and by whom, plus two links: - View in Xero opens the bill in a new tab. - Send again sends the same document once more and replaces the copy already on the bill, so it never shows up twice. A corrected invoice you upload as a new document is a separate file with its own paperclip. The check mark refers to the bill the order is linked to right now. If you change the order’s bill, the documents show as not attached to the new one until you attach them again. If someone changes the linked bill while you are attaching, Logistified stops and tells you the linked bill changed; check it and try again. With more than one Xero organisation connected, each one gets its own paperclip, labelled with the organisation’s name. Xero accepts up to 10 files per bill, each up to 25 MB. If a bill already holds 10 files, Xero refuses the new one and the message tells you why. Note Attaching documents is available for Xero only. QuickBooks support is not available yet. ## Removing a document Click the delete icon on the row. A confirmation dialog asks you to confirm; deletion cannot be undone. Once you confirm, the file is removed from storage and the row disappears. Deleting a document that you attached to the Xero bill removes it from Logistified only; the copy on the bill stays in Xero. The confirmation dialog says so before you delete. Remove the file in Xero if you no longer want it there. Note Documents persist with the PO indefinitely. Even after the PO is closed or archived, the files stay attached and downloadable. ## See also - [Sending the PO] (/features/supply-orders/purchase-orders/sending/): the auto-generated supplier PDF. - [Exports] (/features/supply-orders/purchase-orders/exports/): the label PDF flow. - [Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/): pushing the purchase order to Xero as a bill. Last updated: 20 October 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/exports/ # Purchase order exports CSV, XLSX, PDF, and label sheets, all driven by templates you control. Logistified’s purchase orders have four flavors of export: bulk line-item data exports (CSV / XLSX), bulk purchase-order-level data exports (CSV / XLSX), the individual supplier-facing PO PDF, and label sheets for the receiving station. The data and PDF exports are template-driven; templates pick the CSV / XLSX columns and drive the PDF layout. This page covers when to use each format, how to configure templates, and the label-sheet flow. ## On this page - CSV / XLSX / PDF: when to pick each - Bulk export (CSV / XLSX) - Custom column sets and export templates - Label sheet PDFs - See also [anchor: csv--xlsx--pdf--when-to-pick-each] ## CSV / XLSX / PDF: when to pick each Format Use when CSV Bulk export into a spreadsheet or another system. Can produce one row per line item, or one row per purchase order for accounting-style summaries. Column set comes from the selected export template. XLSX Same bulk-export data as CSV, but you want preserved formatting and Excel-friendly types. PDF Individual supplier-facing PO document. Layout comes from the selected export template (date-field mapping and labels, totals visibility, which standard line-item columns show, address formatting, etc.). The PDF you generate yourself and the file attached to the supplier email are picked separately. Generating a PDF uses the supplier’s default export template, then the shop-wide default. The email attachment uses whatever export template the chosen email template links to, which can be a different PDF template, or an XLSX/CSV template, in which case the supplier gets a spreadsheet instead of a PDF. See [PO Settings → Email templates] (/features/supply-orders/purchase-orders/settings/#email-templates). ### Addresses on the PDF The billing, supplier, and delivery blocks on the PDF each print a full address, including a State / Province field on the city/postal line. The order of city and postal code follows the template’s Address formatting setting (see [export templates] (#custom-column-sets-and-export-templates) below): with the default European format the line reads 04958 North Anson, Maine; switch the template to the US format and it reads North Anson, Maine 04958. Each block falls back through fixed tiers when the PO doesn’t carry its own address: - Billing: the PO’s billing address, else the company address from Settings → Purchase Orders → General. - Supplier: the PO’s supplier address, else the supplier record’s address. - Delivery: the PO’s delivery address, else the PO’s Shopify location. A [dropship PO created from a Shopify order] (/features/supply-orders/purchase-orders/dropship/#delivery-details-from-a-shopify-order) prints the customer’s name and current address read from the order when the PDF is generated; if it can’t be read, no PDF is produced and a message explains why. On a PO [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/), the delivery block carries the receiving supplier’s address and gains one extra line (Deliver to: , receiving on our behalf), so the supplier you’re buying from can tell the address belongs to another business receiving for you, not to one of your own warehouses. Edit the state/province wherever you edit that address: the supplier record, PO settings, or the per-PO address dialogs, whose Copy from Shop Settings, Copy from Shopify Location, and Copy from Supplier shortcuts carry it across. The State / Province field is a purchase-order feature; return-order and transfer-order addresses don’t have it. Supplier state/province is also selectable as a Supplier State / Province column in export templates and as a Label Designer field (it previews blank in the designer but prints the real value). ### Quick PDF Export The individual PO’s actions menu has a Quick PDF Export entry that downloads the PDF immediately with the effective default template, no export dialog. It resolves that default the same way the dialog does: the supplier’s own default template first, then the shop-wide default, then the base PDF settings if neither is set. Template options like Include supplier instructions therefore apply consistently whether you use Quick PDF Export or the full dialog. ## Bulk export (CSV / XLSX) Select rows on the PO list page, then either click the page header’s Export button or open the selection Actions menu and choose Export N. Both open the same dialog; the header button defaults to exporting the current page when nothing is selected, while the Actions menu item always exports your selection. First choose the scope, then choose the data level: - Line item export: one row per PO line item. Use this when another system needs SKU, quantity, unit cost, product, variant, or line-level metafield data. - Purchase order level export: one row per PO. Use this when you need header and summary fields such as PO number, status, supplier, location, shipping cost, additional cost / discount, line subtotal, total cost, amount paid, outstanding amount, and paid status. An Additional Cost Tax column is also available; it isn’t in the default column set, so add it to a purchase-order-level template first ([Settings → Purchase Orders → Export] (/features/supply-orders/purchase-orders/settings/#export-templates-csv--xlsx--pdf)). Note that the total-cost, outstanding-amount, and paid-status columns exclude tax, both the order’s header tax and additional-cost tax. Then pick CSV or XLSX and the matching template. Bulk export produces one downloadable file for the selected POs. Supplier-facing PDFs are generated from an individual PO instead, such as from the PO actions menu or when sending the PO by email. The same selection Actions menu also offers Merge (see [Lifecycle → Merging POs] (/features/supply-orders/purchase-orders/lifecycle/#merging-pos)) and Auto-receive (see [Receiving stock → Bulk auto-receive from the list] (/features/supply-orders/purchase-orders/receiving/#bulk-auto-receive-from-the-list)). Caution Line-item exports fetch one PO at a time so the server is never hammered, with a progress bar as they run. Selecting hundreds of POs can take a minute or more; narrow the selection if you can. You can cancel mid-run; no file is downloaded if you do. ## Custom column sets and export templates Export templates are configured at Settings → Purchase Orders → Export (a tab inside the Purchase Order Settings page, not the general Data Export settings). The page has three template sections: - PDF export templates drive the individual PO PDF and the supplier-email attachment. They carry layout options, not a column list. - XLSX/CSV export templates drive line-item CSV / XLSX exports: bulk from the list, or a single PO. They carry a column list, not PDF layout. A template is one type or the other, never both. - Purchase Order Level XLSX/CSV export templates drive only the global bulk export from the PO list. They do not appear inside an individual PO and are not used for supplier emails or PDF attachments. Between them, the two line-item sections carry: - Column selection: which fields appear, in which order. Drives CSV / XLSX columns only. The PDF body table has its own standard line-item columns (SKU, barcode, product, quantities, costs, tax, totals), adjusted through the PDF layout config below; it does not follow the CSV / XLSX column selection. - Layout config: for PDF, things like totals visibility (shipping, additional costs), date-field mapping, the labels shown beside those mapped date slots, and a Compact layout toggle. Leaving a date label blank keeps the default label. Compact layout uses smaller fonts, tighter rows, and a condensed header to fit more content on each page, useful when paper saving matters. A separate Include supplier instructions toggle controls whether the PO’s [supplier instructions] (/features/supply-orders/purchase-orders/sending/#supplier-instructions) print on the PDF, off by default. An Include supplier notes toggle (PDF templates only) instead prints the notes saved on the [supplier’s own profile] (/features/suppliers/directory/#supplier-detail-page) (a separate, master-data field from the PO’s own supplier instructions), also off by default. An Address formatting selector chooses how city and postal code are ordered in the billing, supplier, and shipping addresses: European (Postal code before city), the default, or US (City before ZIP code). Two further options (purchase-order PDF templates only) control the pack breakdown printed after a quantity, such as 120 (10 packs): - Disable pack size breakdown: hides the pack or case count shown after quantities, leaving the plain number. - Pack unit terminology: whether that breakdown is worded Pack / packs or Case / cases. Existing templates keep saying “pack”; the selector is disabled while the breakdown is hidden. The breakdown only appears on lines whose pack size is greater than 1, and a quantity that isn’t a whole number of packs is printed with the exact figure alongside it. A separate Show delivery schedule on split lines toggle (also PDF templates only, on by default) controls whether a line you’ve [split into several dated deliveries] (/features/supply-orders/purchase-orders/delivery-schedules/) prints a breakdown of its deliveries underneath the quantity. Turn it off if you’d rather the PDF only ever show the line’s total. - Per-supplier defaults: assign a template as the default for a specific supplier. When you export or generate a PDF for a PO from that supplier, the assigned template is picked automatically instead of the shop-wide default. (Supplier emails resolve their attachment through the email template instead; see above.) - Selectable at export time: when you trigger an export or PDF generation, you can override the default template by picking a different one. Purchase-order-level templates carry only PO, supplier, location, and summary columns. They are global list templates, so they do not have per-supplier assignment controls. You can save many templates per shop (“monthly accounting export,” “supplier reconciliation export,” “shipping-PDF for Asia suppliers,” etc.) and pick at the moment of export. Defaults ship for common cases; customise when you need a specific layout for a downstream system or a different supplier’s expectations. ### Finding a column in a large catalog On CSV / XLSX templates the Available columns list is searchable and grouped by source, in a fixed order. On a line-item template the groups are: Line Item, Purchase Order, Product Variant, Product, Inventory: all locations, Inventory: at location, Planning constants, Variant metrics (ABC), Supplier, Supplier Variant, Location. Each group collapses to a header showing how many of its columns are selected, and a Select all / Clear button toggles the whole group; group-selected columns are appended to your column order without reshuffling what you’ve already arranged. The search matches column descriptions as well as names, so searching “availability” surfaces columns whose name never mentions it; while a search is active, matching groups stay expanded. Columns most shops want carry a Rec badge. The line-item catalog runs well past a hundred columns because it includes live variant data, read from your current Logistified data at the moment of export: - Inventory: available, on hand, incoming, committed, and other quantities, both at the PO’s location and summed across all your locations. The at-location figures follow each line’s destination location when one is set, falling back to the PO’s location. These mirror your Shopify inventory. - Planning constants: minimum / maximum inventory, static reorder point, and target inventory at the location. These are your Logistified planning values, not Shopify data. - Variant metrics (ABC): ABC tier, revenue contribution (as a percentage of total revenue), and total revenue, computed periodically by Logistified from your recent order history. Line-item templates also carry the three [line-discount] (/features/supply-orders/purchase-orders/line-items/#line-discounts) columns (Line Item Original Unit Cost, Line Item Discount Type, and Line Item Discount Value) for orders where individual lines were discounted. Line Item Unit Cost is always the effective net cost after any such discount. Both the line-item and purchase-order-level catalogs also carry eight Delivery columns (company name, two address lines, city, province, ZIP, country, phone) for the ship-to address, the PO’s own delivery address if it has one, else its Shopify location. These are the columns to add if you need a [dropship PO’s] (/features/supply-orders/purchase-orders/dropship/) customer address, or a [deliver-to-supplier PO’s] (/features/supply-orders/purchase-orders/deliver-to-supplier/) receiving-supplier address, in an export. They stay blank for a dropship PO created from a Shopify order, whose customer address is read from Shopify only for the PDF. None of these are selected by default; add the ones you need from their groups. The purchase-order-level catalog deliberately carries none of them; they exist only on line-item templates. Note Blank and zero mean different things in these columns. A planning constant that isn’t configured exports blank (not 0), so “no minimum set” can’t be mistaken for “minimum is 0.” Inventory quantities export 0 when the variant has no stock record, and blank when the document has no location to look at. ## Label sheet PDFs A [label sheet] (/reference/glossary/#label-sheet) is a printable artifact with one rectangle per line item: barcode, SKU, variant title, quantity. Used to label received boxes for barcode-scan receiving. Generate from the PO Actions menu → Print Labels. The dialog supports three output formats and two print modes: - Output format: PDF / CSV / XLSX. CSV and XLSX export the same label fields as flat rows (one row per SKU aggregated, or one row per individual label). - Print mode (PDF only): - Simple: rule-based labels driven by the toggles in the dialog (label size, barcode style, fields shown). Configured at [Settings → Label Printing → Simple Mode] (/features/settings/label-printing/). - Designer (Beta): template-driven layout for custom designs. Build the templates in [Settings → Label Printing → Advanced Designer] (/features/settings/label-printing/) and pick one at print time. When the output format is PDF, the dialog also shows a Page Layout section with a PDF page type toggle: One per page, Two across (no gap), Thermal 2-up, or Multi-label sheet / roll. It defaults to your shop-wide setting from [Settings → Label Printing → Preferences] (/features/settings/label-printing/#pdf-page-layout) and can be changed per print job; in Designer mode, Thermal 2-up is only selectable while the selected template is 31.75 × 25.4 mm. Pick CSV or XLSX and the section disappears; page layout only applies to PDFs. The default output format for label printing is configurable per shop, see the [Label export preference] (/features/supply-orders/purchase-orders/preferences/#label-export-preference). The dialog’s second step (Settings) also has a Document Storage section with a Save labels to PO documents checkbox (labelled Save export to PO documents when the output format is CSV or XLSX). With PDF output, tick it to keep a copy of the label sheet in the PO’s [Documents] (/features/supply-orders/purchase-orders/documents/) card in addition to the download; a “Labels saved” confirmation appears once it’s attached. The checkbox starts unticked every time the dialog opens; it is not a saved preference. Your file always downloads even if the save fails; you’ll see a single warning that the copy wasn’t attached, and you can upload the file you already have via Upload new document on the Documents card instead. Caution Saving to documents currently works for PDF output only. With CSV or XLSX output the checkbox appears, but the attachment does not go through; you’ll see an “Export not attached” warning while the download itself still completes. Upload the downloaded file from the Documents card if you need it attached. Label sheets generated as part of the receive flow are saved to the Documents card automatically, no checkbox involved. See [Documents → What Logistified auto-attaches] (/features/supply-orders/purchase-orders/documents/#what-logistified-auto-attaches). Note Bulk export is CSV / XLSX only. To download a supplier-facing PDF, open the individual PO and generate the PDF from its actions. ## See also - [Dropship POs] (/features/supply-orders/purchase-orders/dropship/): the customer delivery address these columns export. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): the receiving-supplier address these columns export, and the PDF’s extra “Deliver to” line. - [Documents] (/features/supply-orders/purchase-orders/documents/): uploading and managing attached files. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries, and the PDF breakdown that results. - [Sending the PO] (/features/supply-orders/purchase-orders/sending/): the supplier-facing PDF in email context. - [Settings → Label printing] (/features/settings/label-printing/): Simple Mode, Advanced Designer (Beta), and Test Print. - [PO Settings → Export templates] (/features/supply-orders/purchase-orders/settings/#export-templates-csv--xlsx--pdf): column presets that drive CSV / XLSX / PDF outputs. - [Preferences → Label export preference] (/features/supply-orders/purchase-orders/preferences/#label-export-preference): default format selector. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/constraints/ # Constraint Studio Configure purchase-order rules for MOQ, pack sizes, supplier minimums, capacity caps, groups, ratios, and optimizer guidance. [Elevate plan] (/reference/subscription-plans/) Constraint Studio is Logistified’s rule editor behind PO hints and the [constraint optimizer] (/reference/glossary/#constraint-optimizer). You configure business rules in a guided workflow; the technical graph is still available through Advanced graph for inspection and power-user changes. [Image: Constraint Studio with compact readiness chips for semantic roles] (/_astro/01-constraint-studio-readiness.BzyLaM0w_Z2lfLEK.webp) The readiness chips show which semantic roles are already mapped from Product Settings or Data Modeling. ## On this page - What a rule controls - Constraint readiness - Presets - Rule metadata - Field binding - Preview and save - Advanced graph nodes - Where rules appear on POs - See also ## What a rule controls A constraint rule can: - Show line or PO-level hints when a PO is below MOQ, not in pack multiples, over budget, missing a group, or missing required data. - Act as an optimizer target, so the optimizer tries to close the gap by adding eligible variants or increasing existing lines. - Add an optimizer objective, so an already-valid plan is ranked toward a better fill or capacity outcome. Rules are evaluated for Draft and Sent POs only. Other PO statuses keep their saved data, but active constraint rules do not apply there. ## Constraint readiness The readiness section checks whether common semantic roles are mapped: Role Used by Group key Group exact count, group minimum total, group coverage. Unit CBM PO max CBM, container fill, capacity blocks. Unit weight PO max weight and weight-based capacity rules. Case size Case-size and multiple-based planning. Pallet quantity Pallet or block-capacity planning. Purchase family Coverage, bundle, and family-based rules. Product MOQ Product-level MOQ summed across variants. Mapped roles can come from Product & variant attributes or from Data Modeling semantic mappings. Hover a readiness chip to see the exact field source. Missing roles do not block saving every rule, but presets that need that role ask you to bind a field manually. ## Presets Click Add rule to open the preset picker. [Image: Constraint preset picker showing MOQ and other rule presets] (/_astro/02-constraint-preset-picker.D2lZTuHb_16utY3.webp) Start from a business preset whenever possible; use Advanced graph only for special cases. The current presets are: Preset What it checks Optimizer behavior MOQ Each line meets supplier-variant MOQ. Can increase/add lines to meet MOQ. Pack size / multiples Each line is a valid pack multiple. Final suggested quantities must respect multiples. Min line quantity Every line reaches a fixed minimum. Can increase lines. Max line quantity Every line stays under a fixed maximum. Fill gaps cannot reduce lines, so this appears as a warning/limit. Supplier minimum value PO value reaches a supplier minimum. Can add/increase eligible lines. Supplier minimum units Total ordered units reach a supplier minimum. Can add/increase eligible lines. PO budget cap PO value stays under a cap. Fill gaps cannot reduce an over-budget PO. PO max units Total ordered units stay under a cap. Hard limit for additive plans. PO max CBM Ordered units times unit CBM stay under a cap. Hard limit when the rule is a target. PO max weight Ordered units times unit weight stay under a cap. Hard limit when the rule is a target. Container fill target Total capacity measure reaches a target. Adds a fill objective. Exact group count PO contains exactly the required number of groups. Evaluates group count; additive fixes depend on candidate data. Minimum units per variant Every active variant reaches a shared minimum. Can increase/add eligible variants. Minimum total per group Every active group reaches a summed minimum. Can increase/add lines in underfilled groups. Product MOQ All variants of each product are summed and compared to a product-level MOQ field. Can increase/add variants until product MOQ gaps are filled. Group coverage Active groups cover available supplier variants in the same group. Can add missing variants from uncovered groups. Ratio / bundle A numerator measure divided by a denominator measure reaches a minimum ratio. Evaluates the ratio; additive fixes depend on candidate data. Fill capacity blocks Current capacity block is underfilled and should move toward the next full block. Objective-only by default. ## Rule metadata Every guided rule has the same high-level settings: Setting Behavior Name Merchant-facing rule name shown in settings, PO hints, and optimizer reasons. Enabled Disabled rules are saved but ignored. Scope General applies to all POs. Supplier scope applies only to selected active suppliers. Statuses Only Draft and Sent are valid active statuses. At least one must be selected. Severity Controls the PO hint tone: Info, Warning, or Error. It does not by itself make a rule hard. Optimizer target Makes the optimizer treat the rule as a target/limit. Warning-only rules still show hints but are not a target. Note The active optimizer mode is Fill gaps. It only increases existing lines or adds eligible variants. Rebalance/reduce/remove planning is still locked. ## Field binding Some presets can use built-in PO fields immediately. Others need a field binding: - Product MOQ needs a product identity field, ordered units, and a product-level MOQ field. - CBM and weight rules need a per-unit Number field. - Group rules need a group key or purchase family field. - Ratio rules need two numeric fields. Constraint Studio suggests fields from semantic roles first. It does not silently bind an unsafe field when the role or type does not match; choose the field explicitly if the suggestion is missing. [Image: Product MOQ preset with product identity, ordered units, and Product MOQ field bindings] (/_astro/03-product-moq-preset.C4RQIwVl_Z2i6dlj.webp) One Product MOQ rule can use a product-level attribute value for every product instead of hard-coding thresholds per product. [Image: PO max CBM preset with a Unit CBM field and maximum CBM threshold] (/_astro/05-cbm-cap-preset.Bi5mFBvY_29DBxv.webp) Capacity rules multiply ordered quantity by a per-unit measure such as Unit CBM. ## Preview and save Before saving, preview a rule against sample data or a real PO. Real-PO preview is the best check because it uses your PO lines, supplier, fields, and current saved values. Preview and evaluation do not change PO quantities. They return pass/fail state, severity, and missing-data reasons such as missing Product MOQ, Unit CBM, Unit weight, Group key, or Purchase family. Settings saves are versioned. If another tab changes the constraint settings first, Logistified rejects the stale save and asks you to reload instead of overwriting someone else’s rules. ## Advanced graph nodes Guided presets compile to a technical graph. Most teams never need to edit it, but it is useful for debugging. ### Datasets Dataset What it contains line_items Current PO lines after data-quality exclusions. Use this for normal rule checks. all_line_items Current PO lines before exclusions. Use this when the rule itself must report missing data. supplier_variants Eligible supplier catalog variants, including variants not yet on the PO. combined_line_items Current PO lines plus simulated optimizer additions. candidate_line_items Only simulated optimizer candidate rows. ### Supported nodes Node Input -> output Main settings meta.rule None -> metadata Internal rule metadata; not needed in guided rules. source.po None -> object Current PO context: header fields, current lines, supplier variants, optimizer candidates. A normal graph has one. source.dataset None -> dataset Reads a named dataset. This is valid for legacy/advanced graphs but hidden from the normal library. source.field None -> scalar Reads one field path, for example line_item.quantityOrdered or a mapped Product Settings/Data Model field. source.value None -> scalar Static text, number, boolean, or date value. transform.extract PO object/dataset -> dataset or scalar Selects line_items, all_line_items, supplier_variants, combined_line_items, candidate_line_items, or a nested PO field. transform.filter Dataset + optional compare input -> dataset Filters rows by field path, operator, and right value. transform.map Dataset -> dataset Adds or replaces a row value. Modes: copy field, write constant, or calculate math into an output field. transform.group_by Dataset -> grouped dataset Groups rows by a field such as product ID, variant ID, group key, or purchase family. transform.aggregate Dataset/grouped dataset -> scalar or grouped values sum, count, distinct_count, min, max, avg; grouped input returns one result per group. transform.set_operation Dataset -> scalar/set/boolean distinct_values, distinct_count, cardinality_in_set, contains_all, contains_any. logic.math Scalars -> scalar +, -, *, /, min, max, ceil, floor, round, abs. Used for ratios and capacity blocks. logic.compare One or two values -> boolean >=, >, <=, <, ==, !=, contains, not_contains, in_set, before, after; pack-size presets also generate multiple_of. logic.group_compare Grouped left + grouped/right limits -> boolean Compares each group to its own limit. Missing-right behavior can fail, ignore, or use a default. Product MOQ uses this node. logic.boolean Booleans -> boolean and, or, not, xor. logic.date Dates -> scalar or boolean before, after, diff_days. logic.quantifier Dataset -> boolean Requires all, any, or none of the rows to satisfy a row comparison. Line MOQ and min/max line quantity use this. logic.coverage Current rows + universe rows -> boolean Checks whether PO groups/variants cover the available supplier universe. Can check only groups already present or the full universe. output.finding Boolean -> PO hint/badge Emits pass/fail text, severity, affected fields, affected variants/groups, and missing-data details. It never changes PO data. output.optimizer_score Scalar -> optimizer objective Adds a numeric ranking signal for candidate plans. Hard feasibility still wins over score. Malformed graphs, cycles, missing nodes, wrong input/output types, missing source.po, and finding outputs that are not driven by logic nodes are rejected. Use the guided workflow unless you need a graph-level rule. ## Where rules appear on POs Saved rules appear in three places: - The Constraints column on PO line items. - Purchase-order hints in the guided PO preview area. - The Optimize dialog, where target rules, remaining reasons, and proposed actions are explained. [Image: Purchase order line items with a failing Product MOQ constraint badge on two variants of the same product] (/_astro/04-po-constraint-violation-badges.BW2M_Mq1_Z21xDm9.webp) This Product MOQ example counts two variants of the same product together. Both rows are marked because the combined ordered units are still below that product's MOQ value. ## See also - [Product & variant attributes] (/features/settings/product-and-variant-attributes/) - define Product MOQ, Unit CBM, Unit weight, and group fields. - [Settings -> Data Modeling] (/features/settings/data-modeling/) - expose custom tables and fields through semantic mappings. - [Purchase Orders -> Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/) - run and apply optimizer plans. - [Guide -> Configure purchase-order constraints] (/guides/configure-purchase-order-constraints/) - worked examples. - [AI / Agent access -> Operating purchase-order constraint rules] (/features/agent-access/operating-constraint-studio/) - what a connected assistant can build here. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/optimizer/ # Constraint optimizer Build and apply additive PO plans against configured purchasing constraints. Elevate-plan feature. [Elevate plan] (/reference/subscription-plans/) Logistified’s [constraint optimizer] (/reference/glossary/#constraint-optimizer) checks a purchase order against configured [constraint rules] (/reference/glossary/#constraint-rule) and proposes a plan. Nothing changes until you review the plan and confirm apply. [Image: Constraint optimizer plan with status, guidance, recommended actions, and Apply Plan button] (/_astro/06-optimizer-plan.Dd5fkuYT_Z1rlAjA.webp) Optimizer plans explain status, reasons, remaining gaps, and why each action was selected. ## On this page - What the optimizer can change - Rule behavior - Modes - Forecast view - Statuses and reasons - Apply flow - Limits and missing data - Sync to Shopify - See also ## What the optimizer can change The active mode is Fill gaps. It can: - Increase an existing PO line. - Add an eligible supplier variant as a new PO line. It cannot currently: - Reduce a line. - Remove a line. - Intentionally make a hard target rule worse. - Apply a plan without your confirmation. ## Rule behavior Constraint Studio rules can be optimizer targets or warning-only rules. - Optimizer target on: the optimizer tries to satisfy the rule and treats caps/limits as hard boundaries for additive plans. - Optimizer target off: the rule still appears as a PO hint, but the optimizer does not target it directly. - Objective outputs: some rules, such as fill capacity blocks, add ranking scores so a feasible plan is ordered toward a better business outcome. - Severity: controls whether PO hints look like Info, Warning, or Error. Severity is not the same as optimizer hardness. Hard target constraints are not knowingly violated by the optimizer. Soft warnings and objectives can remain open and are reported in the plan reasons. ## Modes Mode Availability Behavior Fill gaps Active Adds new lines or increases existing lines. Rebalance Locked Reserved for future reduce/remove plans. UI and API do not allow it yet. ## Forecast view A Forecast View can be selected before running the optimizer. When a view is selected, the optimizer can use stock-day context for ranking. If no view is selected, the run can still proceed, but candidates are ranked without stock-day prioritization and the guidance explains that. If loading the Forecast View fails, the dialog shows guidance and still lets you run with the available supplier candidates. ## Statuses and reasons Status Meaning optimal The bounded search found a complete plan for the targeted rules it can solve. feasible The plan is valid and useful, but some objective or remaining rule reasons may remain. infeasible Rules conflict, required data is missing, or Fill gaps cannot solve the current violation. time_limit The bounded search stopped before finishing every branch. model_too_large The candidate pool is too large for the configured safety limits. Narrow the scope and retry. The plan can include: - Guidance - setup notes, missing view context, or source-mode notes. - Status reasons - why this status was returned. - Remaining rule reasons - target gaps that remain open. - Why selected - why each recommended action was chosen. ## Apply flow 1. Open a Draft or Sent PO. 2. Click Optimize. 3. Run Fill gaps. 4. Review actions, final quantities, reasons, and added variants. 5. Click Apply Plan. 6. Confirm the summary. Apply is one server-side request. Logistified rechecks the baseline, validates the target PO status and supplier/variant eligibility, applies the actions, reevaluates constraints, and returns refreshed audit information. If the PO changed after the plan was created, apply is rejected as stale and you should rerun the optimizer. Only Elevate users can apply plans. Apply is allowed only for Draft and Sent POs. ## Limits and missing data The optimizer is bounded and deterministic so it can run safely and quickly. It returns clear reasons instead of running indefinitely. Common limits: - Missing MOQ, pack size, Product MOQ, CBM, weight, group, purchase family, or cost data. - Missing or inactive supplier mapping. - Deleted or unavailable variant. - Candidate pool too large. - Rules that require reduce/remove actions while only Fill gaps is available. - Budget or max-cap rules already violated by the current PO. ## Sync to Shopify Apply updates the PO in Logistified. It does not send the PO, email the supplier, or push incoming inventory to Shopify by itself. Use the normal PO lifecycle action or Sync to Shopify when you want Shopify incoming inventory updated. ## See also - [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/) - configure the rules used by the optimizer. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/) - where badges and hints appear. - [Guide -> Use the constraint optimizer] (/guides/use-the-constraint-optimizer/) - step-by-step apply flow. - [Reference -> Subscription plans] (/reference/subscription-plans/) - Elevate plan access. - [AI / Agent access -> Operating purchase-order constraint rules] (/features/agent-access/operating-constraint-studio/) - applying optimizer suggestions through a connected assistant. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/credits/ # Applying supplier credits Use a credit you have with a supplier against a new PO. In Logistified, a [supplier credit] (/reference/glossary/#supplier-credit) is a balance you have with a supplier: money they owe you, either from a return order (RMA) or from a credit you recorded manually on the supplier. Each credit stores its own currency; when you apply it to a PO in a different currency, the picker prompts for an exchange rate. This page covers applying a credit to a PO. For the credit ledger and how credits are minted, see [Suppliers → Credits] (/features/suppliers/credits/). ## On this page - What a supplier credit is - When you can apply - The Apply credit dialog - Currency matching - Partial application - Reversing an application - See also ## What a supplier credit is A balance, owed to you by a supplier, available for application to future POs with that supplier. Credits keep their original currency, and applying one across currencies uses an exchange rate. Credits can originate from: - A return order (RMA): the supplier issued a credit instead of a refund. - A manual adjustment on the supplier: recorded directly on the supplier detail page (Credits tab → Add credit) for credits that didn’t originate from an RMA in Logistified. The credit lives on the supplier; the application happens here, against a PO. ## When you can apply You can apply supplier credits when the PO has a supplier and is not Completed or Cancelled. That includes Draft and Sent POs. ## The Apply credit dialog Open from the PO detail page → “Apply credit.” The dialog shows every available credit for the supplier, regardless of currency, and marks ones that don’t match the PO’s currency as cross-currency. Pick one or more. For each, set the amount to apply (≤ the credit’s available balance). Confirm. The PO’s total due decreases. Each credit’s available balance decreases by the applied amount. The dialog checks every amount with the same cent rule the order uses when it records the credit, so what you see is what gets applied: - An amount over a credit’s available balance is marked Exceeds available balance, and an amount too small to record in the credit’s currency is marked Too small to apply in …. Apply stays disabled until you fix those rows. - Typing a credit’s full available amount uses exactly its balance. - Below the list, Still due after these credits shows what the order will still owe. If a credit’s balance was used elsewhere, a credit was voided, or the order total changed while the dialog was open, nothing is applied. The dialog says “Credit balances or the order total changed in the meantime, so nothing was applied. The credits below are refreshed; review the amounts and apply again.”, reloads the credit list, keeps the amounts that still fit and clears the ones that no longer do. ## Currency matching Credits in the PO’s currency apply directly. Credits in a different currency apply with an exchange rate; the dialog fetches a live rate and shows the converted value alongside the credit’s own-currency amount, so you can see both numbers before confirming. Because the credit can only be spent in whole cents of its own currency, the amount that lands on the PO can differ by a cent or two from what you typed; the row then shows Applies … with the exact amount. Cover Full PO picks the largest amount that fits the order without going over it or over the credit’s balance. The backend records the rate used on each application, keeping the audit trail honest. If an exchange rate is missing or looks wrong, enter the rate you want to use before confirming. Cross-currency credits stay in their original currency; only the applied amount is converted onto the PO. ## Partial application You can apply less than the full credit balance. The remainder stays available for the next PO. ## Reversing an application There is no automatic reversal. Cancelling a PO does not automatically reverse applied credits. To unapply, go to the supplier’s Credits tab and remove the application manually. Caution Voiding a supplier credit is irreversible. To partially correct a credit, prefer “edit” over “void.” Void only when the credit was issued in error. ## See also - [Suppliers → Credits] (/features/suppliers/credits/): the canonical credit-ledger reference. - [Return Orders → Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/): how credits come into existence from returns. - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): what cancellation does (and doesn’t do) to applied credits. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/accounting-sync/ # Accounting sync The Accounting card on a purchase order: push a bill to Xero, read its sync status, and fix common errors. Once [Settings → Accounting] (/features/settings/accounting/) is connected, an Accounting card appears on Logistified’s purchase order detail page: “Bill sync to your connected accounting organisation.” It’s only visible on the [Elevate] (/reference/glossary/#elevate-plan) plan with at least one accounting organisation connected. ## On this page - What the card shows - Pushing a bill - Sync status - Common errors and what they mean - See also ## What the card shows Every connected organisation the order could sync to gets its own row: the organisation’s name, a provider badge (e.g. XERO), and its sync mode: Full auto, Auto-create at [status], or Manual (set in [Settings → Accounting → Purchase Orders] (/features/settings/accounting/#purchase-order-sync-settings)). ## Pushing a bill The action button’s label reflects the current state: Button label Meaning Create Bill Nothing has been pushed yet. Update Bill Local changes haven’t been pushed yet, the last push failed, or the order was connected to an existing bill that hasn’t been updated yet. Push again Already in sync: re-push anyway. While the order isn’t linked to a bill yet, a Connect existing bill action sits next to the push button; it links the order to a bill that already exists in Xero instead of creating a new one, see [Connecting existing bills] (/features/accounting/connect-existing-bills/). Once a bill is linked, that action is replaced by a ⋯ menu offering Change bill… (re-point the order at a different bill) and Disconnect bill (removes the link only: nothing in Xero is changed or deleted, and the next push creates a new bill). The refresh icon in the card header re-reads the sync state from Logistified’s own records without contacting Xero. While a push runs, the button reads Pushing… and is disabled. Afterward a toast confirms the result: “Bill synced,” “Already in sync” (nothing had changed), or an error toast naming what went wrong. If a bill already exists in Xero, a View in Xero link opens it in a new tab. ## Sync status The card’s status line tells you where things stand: - Synced ✓ · [date/time]: the bill matches the order. - Local changes not yet pushed: the order has changed since the last successful push. In Manual and Automatic-creation modes you clear it by pushing; in Full auto the next automatic push normally clears it for you. - Connected, not yet updated: the order was linked to an existing Xero bill but nothing has been pushed; the bill is still exactly as it is in Xero. - Not pushed yet: nothing has happened yet. - A red error line when the last push failed, or an amber line, either because a push was skipped, or because the order can’t currently be turned into a bill at all. That second case (a missing account or tax mapping) shows up as soon as you open the card, before you have ever pushed. See below. ## Common errors and what they mean The card explains failures in plain terms rather than raw error codes: Message What it means / what to do “No expense account is mapped” Set a default expense account in Settings → Accounting. “A purchase-tax rate cannot be matched uniquely” An [additional cost / discount entry] (/features/supply-orders/purchase-orders/additional-costs/#tax-on-a-cost-or-discount)’s purchase tax couldn’t be matched to exactly one rate in your accounting system; this also happens when two accounting rates share the same percentage. The in-app message points to Settings → Accounting, but the mapping control is the Accounting tax rate field shown when editing the rate at [Settings → Tax Rates] (/features/settings/tax-rates/#importing-rates-from-your-accounting-system); map it there, then push again. “The supplier is missing or unnamed” No Contact can be created without a supplier name. “This purchase order uses the ‘Default Supplier’ placeholder” Assign a real supplier before syncing; see [Suppliers → Accounting contacts] (/features/suppliers/accounting-contacts/). “Line items use more than one currency” A bill needs a single currency; split the order. “The purchase order has no billable line items” Add at least one line item. “The bill can no longer be modified in the accounting system (paid or locked)” Later changes on this order stay local only; they can’t reach Xero anymore. “The accounting period is locked” Xero has closed that period; the bill can’t be posted or updated. “The bill is fully paid” Paid bills never receive updates. “The bill was auto-created and is frozen” Push manually to apply later changes. A currency-not-enabled message The supplier bills in a currency your accounting organisation doesn’t have enabled. In Xero, add it under Accounting settings → Currencies (a multicurrency plan is required), then push again. “A bill with this number already exists in the accounting system” Xero already holds a bill carrying this order’s number that Logistified didn’t create. Use Connect existing bill to link it rather than creating a duplicate; see [Connecting existing bills] (/features/accounting/connect-existing-bills/). Tip Most of these are one-time setup gaps (a missing account mapping, a placeholder supplier) rather than ongoing problems; fix the underlying setting once and the next push succeeds. ## See also - [Accounting → How bill sync works] (/features/accounting/how-bill-sync-works/): what a push updates, what it never touches, and how paid bills are protected. - [Accounting → Connecting existing bills] (/features/accounting/connect-existing-bills/): the Connect existing bill action in detail. - [Documents → Attaching a document to the Xero bill] (/features/supply-orders/purchase-orders/documents/#attaching-a-document-to-the-xero-bill): sending supplier invoices and other files from the order to its linked bill. - [Settings → Accounting] (/features/settings/accounting/): connecting Xero, bill creation modes, and lifecycle mapping. - [Suppliers → Accounting contacts] (/features/suppliers/accounting-contacts/): linking the supplier this order uses. - [Payments & “marked as paid”] (/features/supply-orders/purchase-orders/payments/): payments recorded in Logistified are separate from a bill’s paid status in Xero. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/side-effects/ # Side effects & integrations What fires automatically when you act on a PO: Shopify pushes, emails, tags, log entries. When you move a purchase order through its lifecycle in Logistified, things happen automatically: Shopify gets updated, your supplier gets emailed, tags get applied, the audit log records every step. This page is the complete list. Use it when you’re trying to understand why something happened (or didn’t). ## On this page - Inventory effects - Tag effects - Email effects - Background work - Constraint engine effects - Document effects - Audit effects - Things that don’t happen automatically - Reconciling drift - See also ## Inventory effects When What PO moves to Sent Shopify’s incoming inventory for the variants is pushed as the ordered quantity. (This is where “incoming” first appears in Shopify, not Confirmed.) Lines confirmed (or PO transitions to Confirmed) Incoming is reconciled to confirmed − received − cancelled − rejected. If the supplier confirmed less, incoming goes down accordingly. Receive Manually Receipt is recorded in Logistified. On-hand is not pushed unless [Auto-sync to Shopify on receiving] (/features/supply-orders/purchase-orders/preferences/#auto-sync-to-shopify-on-receiving) is enabled. Shopify incoming is reconciled when Auto-sync or manual Sync to Shopify runs. Sync to Shopify after a manual receive Warehouse receipts are pushed to Shopify on-hand and incoming is reconciled. Quick Complete receive Confirmed quantities are received, warehouse on-hand is pushed to Shopify, incoming is reconciled, and the PO is completed. Cancel a PO Any pending Shopify incoming for this PO’s lines is rolled back to zero. Reopen Order (from Completed) Incoming is re-pushed for any outstanding pending units. Merge or split lines into another PO Incoming is recalculated for the affected source and target POs so Shopify reflects the lines’ new owner and quantities. These pushes target Shopify’s incoming inventory field when incoming tracking is enabled. The visible result in Shopify is that the location’s Incoming column rises as soon as a PO is Sent; available and on-hand do not move yet. They change only when stock is received and pushed through Quick Complete, Auto-sync, or manual Sync to Shopify. If updates don’t happen, run [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). Note Shopify on-hand sync requires a Shopify-backed destination location for warehouse-delivery and warehouse-consignment lines. Supplier-held receipts are tracked in Logistified but are never pushed to Shopify on-hand; warehouse-consignment receipts are pushed like ordinary warehouse-delivery receipts. ## Tag effects Tag triggers on POs are operator-configured, not hard-coded. In Settings → Purchase Orders → Product Tags you define, per tag: - Apply statuses: which transitions cause the tag to be applied to the linked Shopify product (or variant). - Remove statuses: which transitions cause the tag to be removed. - Removal policy: “always remove” or “remove only when no other active PO holds this product.” The “protected” policy is what you want when a product can be on several POs at once and you don’t want a per-PO removal to strip the tag prematurely. Typical defaults are “apply on Sent” and “remove on Completed / Cancelled,” but you can wire any status as a trigger. When Tag effect Any transition with Apply statuses matched Tag applied to the product or variant in Shopify. Any transition with Remove statuses matched Tag removed, subject to the removal policy. Other transitions No tag change. Useful when your storefront wants to display “shipping soon” badges on products with open POs, or when a 3PL integration keys off tags. ## Email effects When Email PO moved to Sent via Send via Logistified Supplier email queued with the PO PDF (attachment uses the linked export template). Email delivered / bounced / failed [Delivery status] (/reference/glossary/#email-delivery-status) updated on the Emails card. Manual Re-Send Email from actions menu New email queued; new row in the audit. PO moved to Sent via Mark as Sent (Manual) No email sent. The email template lives in Settings → Purchase Orders → Email Templates and supports per-supplier overrides: assign a specific template as default for a given supplier. The sender domain and signature come from Settings → Email Sending; supplier email sending is gated on those being configured. Manual Mark as Sent does not send email. ## Background work These happen invisibly after a transition: - Sync with companion apps. If you also use the Assemblified app, variants it manages are synced separately so the two apps stay aligned. - Audit log. Every state change adds an entry. The Log card shows them in order. - Local receipt records. Receiving updates Logistified first; Shopify is updated by Quick Complete, Auto-sync, or manual Sync to Shopify. - Merge and split reconciliation. When lines move between POs, Logistified refreshes the affected Shopify incoming quantities, product tags, and write-back metafields instead of treating the move as only a visual row change. - Write-back metafields. If you’ve configured PO → Shopify write-back rules, they fire on the trigger status you specified. Boolean write-back rules use TRUE and FALSE status lists and keep the Shopify value TRUE while another active PO still holds the same product or variant in a TRUE status. ## Constraint engine effects If constraint rules are configured (Elevate plan): - Constraint evaluation refreshes badges and purchase-order hints. Evaluation does not change data. - Running the optimizer builds a preview plan. It does not change data. - Applying an optimizer plan updates Logistified PO quantities/additions in one confirmed apply request, then reevaluates constraints. - Apply does not send the PO, email the supplier, or push incoming inventory to Shopify by itself. Use the normal PO lifecycle action or Sync to Shopify for Shopify inventory updates. - Apply is allowed only for Draft and Sent POs and only for Elevate users. ## Document effects - Sending a PO generates the supplier PDF on demand and queues it as the email attachment. The PDF layout comes from the linked export template. - Printing labels generates the label PDF (or CSV/XLSX) on demand and downloads it to your browser. - Uploaded documents are saved alongside the PO and persist with it. On very large POs, PDF generation can be slow. If you see a timeout, split the PO or print labels separately. ## Audit effects Every transition stamps: - A dated column on the PO header (Sent date, Confirmed date, Received date, etc.). - A log entry on the PO’s Log card. - The previous status, so undo and Reopen work cleanly. ## Things that don’t happen automatically This is the list of common surprises: actions you’d reasonably expect to be automatic but aren’t. - Credit application reversal on cancel. Cancelling a PO does not reverse applied credits. Unapply manually. - Receipt reversal on shipment delete. Deleting a [shipment] (/features/supply-orders/purchase-orders/shipments/) doesn’t reverse received quantities on the lines; receiving records are unaffected. Edit the line directly. - Per-line tax override. Tax applies at the PO level. Workaround: split the PO when some lines need different tax treatment. - Auto-apply credits on PO creation. Available credits aren’t pre-applied; you choose when. - “Marked as paid” validation. The flag is operator-set; it doesn’t compare against the recorded payments total. - On-hand push on manual Receive. Without [Auto-sync to Shopify on receiving] (/features/supply-orders/purchase-orders/preferences/#auto-sync-to-shopify-on-receiving) enabled, Shopify on-hand changes only after you click Sync to Shopify (or use Quick Complete). Shopify incoming may also continue to show the earlier amount until that sync or an incoming reconciliation runs. ## Reconciling drift If you notice Shopify’s incoming doesn’t match what Logistified shows, run [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). Drift is usually caused by a transient sync failure; the reconciliation flow catches and fixes it. Note All these side effects are best-effort. If your network connection fails mid-update, the local PO is correct but Shopify might not be. The reconciliation workflow catches and fixes that lag. ## See also - [Lifecycle & statuses] (/features/supply-orders/purchase-orders/lifecycle/): the at-a-glance matrix. - [Preferences] (/features/supply-orders/purchase-orders/preferences/): Auto-sync, incoming tracking, label default format. - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): drift detection. - [Settings] (/features/supply-orders/purchase-orders/settings/): every setting that influences the side effects. - [Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/): optimizer apply behavior and limits. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/preferences/ # Preferences Runtime toggles that change day-to-day PO behaviour: Shopify sync, incoming tracking, label format, PDF totals. Preferences are the runtime toggles for PO behaviour: the dials your operator flips to adjust how Logistified syncs, what’s tracked, and which defaults are pre-selected. They live alongside the rest of the PO settings but get their own page here because picking the wrong combination has visible effects on Shopify and the receive flow. For the configuration surfaces (tax rates, templates, tags, etc.), see [Settings] (/features/supply-orders/purchase-orders/settings/). ## On this page - Where preferences live - Auto-confirm quantities - Split delivery date - Auto paid when completed - Count payment tax and tariff toward paid status - Label export preference - Auto-sync to Shopify on receiving - Block sync to Shopify - Auto sync costs on completion - Update Unit Cost - Incoming inventory tracking - PDF totals - Default line-item sort - Dialog group and sort defaults - See also ## Where preferences live Settings → Purchase Orders → Preferences (a tab inside the PO settings page). All toggles are saved per shop. ## Auto-confirm quantities Default Off What it controls Whether confirmed quantity is kept equal to ordered quantity for you. When enabled, the confirmed quantity always matches the ordered quantity and per-line confirmation is skipped: the Confirm Items menu offers only Quick Confirm, which sets confirmed = ordered and moves the PO straight to In Progress. After confirmation, changing an ordered quantity updates the confirmed quantity automatically, and the confirmed-quantity column in Bulk Edit is disabled (“Auto-confirm is enabled. Confirmed quantity always matches ordered”). Turn it on when your suppliers always ship what was ordered and per-item confirmation is noise. Leave it off when you need to record short confirmations and rejections line by line. ## Split delivery date Default Off Where it shows PO overview table and detail page’s order information card When enabled, the PO list and detail page show the source of the delivery date (“Requested,” “Expected,” or “Estimated”) instead of the generic “Delivery Date” label. The displayed value still follows the same precedence (Requested → Expected → lead-time estimate); only the label changes. The edit dialog is unaffected. Use it when your team needs to distinguish at-a-glance between dates the supplier promised, dates you asked for, and dates derived from lead-time math. Note Despite the similar name, this has nothing to do with [splitting a line into several dated deliveries] (/features/supply-orders/purchase-orders/delivery-schedules/); that’s a separate feature reached from the line-item table’s Split into deliveries icon. ## Auto paid when completed Default Off Where it shows The Paid badge, the paid/unpaid filter on the purchase orders list, and the export’s Paid Status column. When enabled, a purchase order is treated as fully paid the moment it reaches Completed, regardless of recorded payments. The Paid badge, the list filter (All Payment States / Paid / Unpaid), and the Paid Status column in data exports all report it as paid; the export’s Amount Paid and Outstanding Amount columns are unaffected and keep summing actual payments. The [Fully Paid Date] (/features/supply-orders/purchase-orders/payments/#fully-paid-date) is stamped on completion if it isn’t already set. On a Completed PO with this preference on, the [“Mark as fully paid”] (/features/supply-orders/purchase-orders/payments/#the-marked-as-paid-flag) checkbox on the Payments card shows as checked and disabled (“Auto-paid. PO is Completed”); Completed alone forces the paid state. When disabled (the default), paid status follows only the “Mark as fully paid” flag and recorded payments covering the order total; a Completed PO with no payments recorded shows as unpaid until you record one or mark it paid by hand. Turn it on when your team treats “Completed” as the signal that payment is settled (e.g., payment is handled entirely outside Logistified before you close the order). Leave it off when payment and receiving are tracked independently. Note Reopening a Completed PO flips it back to unpaid (unless payments or the manual flag cover it), but the Fully Paid Date it stamped stays ; the date is never cleared automatically, and re-completing later won’t overwrite it. ## Count payment tax and tariff toward paid status Default Off Where it shows The Paid badge, the paid/unpaid filter, and when the Fully Paid Date is auto-set. The full toggle name is “Count recorded payment tax and tariff toward the paid status.” When off, only each payment’s Amount counts toward covering the order total; when on, each payment counts as amount + tax + tariff. Pick the mode that matches how you fill in the payment dialog; see [Payments → Counting payment tax and tariff toward paid status] (/features/supply-orders/purchase-orders/payments/#counting-payment-tax-and-tariff-toward-paid-status) for the full behaviour, including the export exception. ## Label export preference Default PDF Options PDF / CSV / XLSX Where it shows Pre-selects the output format in the label print dialog (on POs and TOs). Also determines the format used when quick-printing labels from the receiving dialog. Picking PDF opens the browser print dialog. CSV and XLSX trigger a file download. Pick whichever matches your physical-label workflow: sheet printer (PDF) or flat-file ingestion into a label-printer system (CSV/XLSX). See [Exports → Label sheet PDFs] (/features/supply-orders/purchase-orders/exports/#label-sheet-pdfs) for the format details. ## Auto-sync to Shopify on receiving Default Off What it controls Whether Receive Manually also runs the Shopify sync step automatically. This is the most impactful preference for the receive flow. With Auto-sync off (default): - Receive Manually records the receipt in Logistified, but does not push Shopify on-hand. You click Sync to Shopify when ready. - Shopify incoming is reconciled when that sync runs, so Shopify may still show earlier incoming until you sync. - Quick Complete still pushes on-hand (its whole purpose is one-click receive + sync + complete). With Auto-sync on: - Receive Manually also pushes on-hand to Shopify and reconciles incoming after every save. - Behaves the same as Quick Complete’s push step, but on a per-receipt basis. When to turn it on: Your team trusts the receive numbers entered in Logistified and you want Shopify to reflect on-hand the moment you save. Common for warehouses that receive in real-time at the dock. When to leave it off: Receivers enter rough numbers first and reconcile later. You want a final review step before Shopify’s on-hand changes. Cross-team accountability matters and you want Sync to Shopify to be a deliberate action. Caution When Auto-sync is off, on-hand in Shopify does not update until you click Sync to Shopify. Skipping that step leaves Shopify under-reporting your stock until the next sync. Note Quick Complete, Auto-sync, and manual Sync to Shopify require a Shopify-backed destination location on the PO for warehouse-delivery lines. ## Block sync to Shopify Default Off What it controls Whether Logistified is allowed to push available (on-hand) quantity to Shopify from purchase orders at all. When Block sync to Shopify is on: - The Sync to Shopify button on a PO is disabled and shows an explanatory tooltip. - Quick Complete still completes the order and records received quantities, but it skips the Shopify on-hand push. - Auto-sync to Shopify on receiving is automatically turned off (the two settings conflict; enabling Block sync prompts a confirmation before disabling Auto-sync). - Reversals (unreceiving quantities or deleting a line) still correct Shopify’s on-hand. Only the forward sync is blocked. - Shopify incoming tracking is not affected; PO status changes still update Shopify’s incoming field as usual (unless you’ve also turned off incoming tracking separately). When to use it: your warehouse uses a 3PL, a separate WMS, or another integration that owns Shopify’s available inventory. Blocking the sync from Logistified prevents double-counting or conflicts with that other system. You still get the benefit of tracking PO progress and receiving quantities inside Logistified. Caution While Block sync is on, Logistified does not push on-hand to Shopify; your Shopify available inventory will only reflect what your other system writes. Turn Block sync off if you want Logistified to be the source of truth for Shopify on-hand. ## Auto sync costs on completion Default Off What it controls Whether completing a PO writes its line costs back to Shopify and/or the supplier catalog. When enabled, completing a purchase order updates the cost targets you tick: - Sync Shopify cost and Sync supplier cost: independent checkboxes; either, both, or neither. - Cost source per target: Direct cost or Landed cost. - Method per target: Set new, Simple average, or Weighted average. Weighted average blends the stock you already held with what this PO just brought in, weighted by quantity. It’s computed against the stock level recorded right before this PO’s first receipt (not whatever’s on hand at sync time), so a PO received across several partial deliveries doesn’t get double-counted. Older receipts made before this snapshot existed use on-hand stock at the first weighted calculation as an approximate basis; that quantity is saved and reused on later updates; the manual [Update Unit Cost] (#update-unit-cost) dialog flags this on the PO so you know to double-check it, particularly if the PO was replenishing stock that was previously at zero. Completion stops if costs or a required exchange rate cannot be resolved, so the PO stays in its current status until you fix the missing data. One case never stops it: with Simple average or Weighted average, a cost is auto-synced at most once per order per target. If a line’s Shopify or supplier cost was already synced from this same order (for example you’re completing it again after reopening it), that line is skipped instead of blocking completion, and the completion (and Quick Complete) dialog tells you how many lines will be skipped before you confirm. Set New Price has no such limit and always re-writes the cost. To push a skipped line’s cost by hand, use [Update Unit Cost] (#update-unit-cost). What completion tells you about costs. The green Purchase order completed message adds “Shopify costs for N items are being updated in the background.” when the Shopify writes are still on their way; that is normal, not a warning. If some costs could not be updated, you see Order completed, but some costs need attention with one line per cause, for example “Cost update skipped for SKU-1 and SKU-2: Another cost update for this item is still running. Use Re-sync costs on the order once it has finished.” or “… You can do this in Update Unit Cost.” ## Update Unit Cost The preference above runs at completion. To push a purchase order’s costs out by hand (at any point from In Progress onwards, and still on a Completed order), open the order’s Actions menu and choose Update Unit Cost. It uses the same three methods, but shows you every number before anything is written. The dialog walks through three labelled steps: Review, Confirm and Result. [anchor: step-1--review-costs] ### Step 1: Review costs Choose where the costs go under Update: Shopify cost per item, Supplier catalogue cost, or both. The table and the new costs follow your choice right away; an exchange rate is only needed while Shopify is one of them. If your Xero items are set to Set new cost (see [Xero items and purchase cost] (/features/accounting/xero-items/#sending-purchase-order-costs-to-xero)), a third choice appears: Xero item cost. It sends this order’s direct or landed cost per item to the linked Xero items of the rows you select, whether or not anything was received; the method and the costs you type here don’t change it. The confirm step lists it, and the result says how many Xero item costs are being updated. A table lists each item on the order (title, with its SKU underneath) with its Current costs (the Shopify cost and the supplier cost), the PO cost (editable, so you can correct a price before it propagates), and the New cost the chosen method produces. Nothing changes until you confirm. Tick only the rows you want to update; Select all / Deselect all is in the footer. Pick the Method: - Set New Price: the new cost is this order’s cost per unit. - Simple Average: halfway between the cost before this order arrived and the PO cost. - Weighted Average: blends the cost of the stock you had before this order with this order’s received units, by quantity. A Use landed cost switch appears when the order has landed cost available. It adds this order’s shipping and other extra costs to each unit, so the update can carry freight and duties rather than the bare purchase price. Under each row’s current costs you may see a Last Shopify update / Last supplier update line describing the newest cost update this order made to that target, for example updated to €15.00 (20 units, weighted average), already up to date, being sent, not confirmed yet or resolved: the current cost was kept by …. Not confirmed yet does not prove the update failed (the cost may already have changed), so compare it with the current cost before running an averaging update again. If something needs your attention, one short message above the table says what happened and offers the one button that fixes it, and each affected row carries a small label: - Out of date: the order changed after you opened the window (for example a receipt or a cost edit). Logistified normally refreshes the numbers by itself, keeping your method, your selection and any PO cost you typed; if it still can’t catch up you get a Refresh costs button. - Waiting: an earlier cost update for the item is still running. The dialog checks again automatically for about a minute and unblocks the row on its own; after that, Check again. - Needs your decision: Logistified couldn’t confirm an earlier update. Check the cost in Shopify, then choose Keep current cost (or, while an earlier update is still waiting to be sent, Stop pending update) on the row; the row unblocks in place. On the confirm step, Skip these items lets you go on without them. - Averaging not possible: averaging isn’t possible for the item (for example its earlier cost history is incomplete). Switch to Set New Price switches the method for all selected items; you see the new numbers before confirming. - Couldn’t check: the cost couldn’t be checked just now. Nothing was changed; Try again. - Can’t be updated: for example the item no longer exists. Skip these items (or Skip this item) deselects them so you can continue with the rest. On orders created before cost tracking, Weighted Average can also show Weighted not possible on a row (for example “This item was received at different stock levels, so a weighted average can’t be calculated. Use Set New Price or deselect it.”) with Switch to Set New Price above the table. Next stays disabled while nothing you selected can be updated. If only one cost is affected (for example Shopify can’t be checked just now), untick it under Update and continue with the other. On older orders created before cost tracking was introduced, two more lines can appear: the Original Shopify basis / Original supplier basis (the price recorded the first time this order updated that cost, which every later run averages from) and, for Weighted Average, a note when the stock basis is an approximation: “Some items use current on-hand stock because no receipt baseline was recorded… If this PO replenished empty stock, use Set New Price with landed cost.” ### Currency conversion When the order’s currency differs from your shop currency, a Convert currencies switch appears, on by default, because Shopify stores costs in your shop currency and an unconverted push would be wrong. Supplier costs always stay in the order’s currency. The Exchange rate field (read as “1 unit of your shop currency = X of the order’s currency”) pre-fills from the rate saved on the order when it has one, and otherwise from a live reference rate, which only ever fills an empty field. While it loads you see Loading live exchange rate… rather than a validation error; if the lookup takes too long the field says Live FX rate timed out. Enter it manually. Shortcut buttons let you snap back to the rate Fixed on PO or to the Live rate, and you can always type your own. A rate you change is saved on the order when you click Next, and the costs are recalculated with it before you confirm. [anchor: step-2--confirm--update] ### Step 2: Confirm & update A Changes list shows exactly what will be written, for example Widget · Blue · Shopify cost per item €10.00 → €5.50 (the first six, then “and N more”), and the button says what it does: Update 1 cost, Update 3 costs. [anchor: step-3--result] ### Step 3: Result The result says plainly what happened: Costs updated, Costs already up to date, Some costs were not updated, Nothing was updated, or Not confirmed yet when Shopify hasn’t confirmed an update: the cost may already be applied, so open its Cost history to check before updating it again. Each item is listed once: Updated: €10.00 → €30.00, Already up to date, or the reason it wasn’t updated. When you can fix the cause in the review, Back to review takes you there. If the order changed while the update was being sent, nothing is written: you land back on the review with refreshed numbers and a short note, check them and confirm again. Each item in the result also has a Cost history link. It closes this dialog and opens the item’s cost history: Cost in Shopify now, Last cost set by Logistified, the Cost after a re-sync, any earlier update that is still blocking the item (with Keep current cost / Stop pending update), and a note when the cost in Shopify was changed outside Logistified. Update Unit Cost, Re-sync costs and Complete wait while the page is still saving your other changes, so a cost update never runs against half-saved numbers. ### Re-sync costs On a Completed order whose costs fell behind (for example a receipt was corrected after completion, or the last cost update was not written), a notice at the top of the order says what changed, such as “Received quantities on this order changed after its last cost update; re-sync costs to update the Shopify cost.”, with a Re-sync costs button beside it. Re-sync costs repeats the update your [automatic cost sync settings] (#auto-sync-costs-on-completion) would make. The result is counted plainly: “Costs re-synced: 2 updated, 1 already up to date.”, “2 of 3 costs re-synced” with the reason for the rest, or “Costs could not be re-synced”. Re-sync costs needs automatic cost sync turned on with at least one cost selected. When it is off, the notice offers Update Unit Cost instead. The exception is [Xero items] (/features/accounting/xero-items/) in Set new cost mode: re-sync then still sends the order’s cost to Xero, even with Shopify and supplier cost sync off. ## Incoming inventory tracking Default Off What it controls Whether Logistified writes to Shopify’s incoming inventory at all. When enabled, Shopify’s incoming inventory is updated by PO status changes, line-item quantity changes, and receive syncs (the table in [Side effects → Inventory effects] (/features/supply-orders/purchase-orders/side-effects/#inventory-effects) applies). When disabled, Logistified still tracks pending and received quantities, but doesn’t touch Shopify’s incoming field. Useful when another system owns Shopify’s incoming write or when you’re debugging a drift problem. Note Turning this off won’t reverse already-pushed incoming quantities. To clear stale incoming after disabling, use [Incoming reconciliation] (/features/inventory/incoming-reconciliation/). ## PDF totals Two toggles that control which lines appear in the totals section of exported PDFs: - Show shipping cost: display the PO shipping amount in the PDF totals. - Show additional costs / discounts: display additional costs or discounts in the PDF totals. Both default off, so a fresh shop’s PDF totals show neither line. Turn them on when you want shipping and additional costs itemised for the supplier; leave them off, e.g., when shipping is invoiced separately and shouldn’t appear on the order doc. ## Default line-item sort Default Product title, ascending Options None · order added / Product title / Variant title / Shopify SKU / Supplier SKU / Shopify barcode / Supplier barcode / Quantity ordered / Unit cost / Status / Expected delivery date Direction Ascending or Descending Where it shows The line-item table when you open a purchase order; also applies to exported PDFs and spreadsheets. Sets the column used to order line items when you open a purchase order. Choose None · order added to keep items in the order they were added (the ascending/descending toggle is disabled in this mode). This is a shop-wide preference; all POs open with the same default sort. You can re-sort interactively on the detail page at any time; the preference only sets the starting order. ## Dialog group and sort defaults Default Ungrouped; unsorted: each dialog opens in the order’s own line-item order Group options None / Vendor Sort options None · order added / Product / Variant / SKU / Quantity Direction Ascending or Descending Where it shows The Receive Quantities and Confirm Items dialogs, applied the moment either one opens. Two controls (Dialog group by and Dialog line-item sort) set how line items are grouped and sorted when you open the Receive Quantities or Confirm Items dialog on a purchase order. Quantity sorts by whichever quantity that dialog displays: confirmed quantity in Receive Quantities, ordered quantity in Confirm Items. This is separate from [Default line-item sort] (#default-line-item-sort) above, which only affects the line-item table on the PO detail page, not the dialogs. You can still change the grouping and sorting inside either dialog after it opens; search, group, and sort choices reset to your saved default the next time you open it. ## See also - [Receiving stock] (/features/supply-orders/purchase-orders/receiving/): how the receive flow uses these preferences, including the Receive Quantities dialog’s own group and sort controls. - [Sending the PO] (/features/supply-orders/purchase-orders/sending/): the Confirm Items dialog’s group and sort controls. - [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): what the preferences change. - [Settings] (/features/supply-orders/purchase-orders/settings/): the configuration surfaces (templates, rules, tags). - [Exports] (/features/supply-orders/purchase-orders/exports/): the templates that drive PDF layout. - [Payments] (/features/supply-orders/purchase-orders/payments/): how the paid status is derived and what the paid-status toggles change. - [Line items & costs] (/features/supply-orders/purchase-orders/line-items/#cost-calculation): how a line’s unit cost is calculated and displayed, including sub-cent precision. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries (a different feature from the Split delivery date preference above). Last updated: 23 September 2026 --- Source: https://docs.logistified.app/features/supply-orders/purchase-orders/settings/ # Purchase order settings Every setting that changes how POs behave: where it lives, what it does, what's not yet supported. Every setting that affects purchase order behaviour in Logistified lives in one of these settings pages. This is the cross-reference; open the matching page in Settings to actually change something. For the runtime toggles that change behaviour day-to-day (auto-sync, label default format, incoming tracking), see [Preferences] (/features/supply-orders/purchase-orders/preferences/). ## On this page - Where PO settings live - Address profiles - Tax rates - Landed cost - Snapshot metafields - Write-back metafields - Product tags on transition - Constraint rules - Email templates - Export templates (CSV / XLSX / PDF) - Import templates - Label printing - Document tags - Adjacent settings that affect POs - What settings don’t exist yet - See also ## Where PO settings live Most settings live at Settings → Purchase Orders. The page has ten tabs: - General: company info shown on PDFs (name, VAT ID, address including a State / Province field, branding). - Address profiles: reusable billing and delivery addresses (see below). - Preferences: runtime toggles (see [Preferences] (/features/supply-orders/purchase-orders/preferences/)). - Landed Cost: which components contribute to per-line landed cost, and how they’re allocated across lines (see below). - Export: export templates for line-item CSV / XLSX / PDF and purchase-order-level CSV / XLSX. - Shopify Fields: snapshot and write-back metafields. - Constraints: constraint rule editor (Elevate plan). - Document Tags: categories for uploaded documents (Quote, Invoice, Receipt, etc.). - Product Tags: product-tag-on-transition rules. - Email Templates: supplier email subject/body, per-supplier overrides. Adjacent settings outside the PO settings page (Tax Rates, Carriers, Locations, Email Sending, Label Printing, Data Import / Export) are listed below. ## Address profiles - Where: Settings → Purchase Orders → Address profiles tab. - What it does: saves a named company / billing or delivery address once so you can drop it onto a purchase order instead of retyping it. Typical use is a business that buys under more than one company address, or ships imports to a customs agent rather than a warehouse. Each profile has a Profile name and an Address type (Company / billing or Delivery) plus the usual address fields (company name, VAT ID, address lines, city, state / province, ZIP, country, contact, phone, email). Add address profile creates one; Edit changes it; Archive retires a profile you no longer use, and Restore brings it back. Archived profiles stay visible with an Archived badge and can’t be picked for new orders. Per-supplier defaults. A supplier’s detail page has a Purchase order address defaults card where you pick that supplier’s default Company / billing profile and Delivery profile, or leave them on Use existing defaults. A new purchase order for that supplier then starts with those two addresses already filled in, unless the order carries an address of its own. The delivery default only applies to orders going to one of your own locations; a [dropship] (/features/supply-orders/purchase-orders/dropship/) or [deliver-to-supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) order takes its ship-to address from the customer or receiving supplier instead. If a supplier’s assigned profile is archived, that default is simply inactive until you restore it. Each order keeps a copy. Applying a profile copies the address onto that purchase order. Editing or archiving the profile afterwards never rewrites orders that already exist, and you’re free to adjust the copied address on an individual order; the dialog notes “Copied from profile: name. Editing these fields changes this purchase order only.” ## Tax rates - Where: Settings → Tax Rates. - Types: Sales, Purchase, Shipping. POs use Purchase-type rates. - Assignment: A [tax rate] (/reference/glossary/#tax-rate) is set on the supplier; the PO inherits it; you can override on the PO header. - Per-line override: not supported for product line items. To handle mixed-tax lines, split the PO. - Additional costs & discounts: each entry can carry its own independent purchase tax rate (or none), separate from the header rate above; see [Additional costs → Tax] (/features/supply-orders/purchase-orders/additional-costs/#tax-on-a-cost-or-discount). - Behavior on change: tax rate changes apply to future POs only. Existing POs keep the rate set at creation. ## Landed cost - Where: Settings → Purchase Orders → Landed Cost tab. - Included components: toggles for which PO-level costs contribute to each line’s per-unit landed cost: shipping cost, purchase tax, additional cost or discount, payment tax, and payment tariff. - Allocation method: how the included charges spread across the PO’s lines: - By quantity (default): evenly per received unit. - By value: proportionally to each line’s goods value (unit cost × received quantity). Lines with no value, such as free samples, then carry none of the charges; if no received line has a positive value, the charges fall back to the per-unit spread. - Purchase tax is the exception: it is not affected by the allocation method; each taxable line carries tax on its own value at the PO tax rate, and tax on shipping is spread evenly across taxable received units. ## Snapshot metafields - Where: Settings → Purchase Orders → Shopify Fields tab. - What it does: picks which Shopify variant / product metafields are snapshotted onto the PO line at creation. Those snapshots are then visible as columns on the line-item table and can appear on the PO PDF (subject to the export template). - Adding new metafields: the definitions offered here come from Settings → Variant Settings → Attribute Definitions; link the Shopify metafield there first and it appears in this list. - Why snapshot? The PO carries the value that was true at the time of ordering, even if Shopify-side data later changes. ## Write-back metafields - Where: Settings → Purchase Orders → Shopify Fields tab, Shopify Writeback Rules card. - What it does: writes a PO-derived value back into Shopify when the PO hits a trigger status you choose. - Per rule, configure: trigger status, source field (ordered / confirmed / received / pending quantity, or other calculation), owner type (Shopify product or variant), target metafield key. - Boolean metafields: if the target Shopify-linked attribute is a Boolean, configure separate TRUE and FALSE status lists instead of quantity/date aggregation. The shipped default is TRUE for Confirmed / In Progress / Partially Received and FALSE for Draft / Received / Completed / Cancelled. - Multiple active POs: Boolean rules stay TRUE while any other active PO for the same product or variant still matches a TRUE status. This prevents one received PO from turning off a storefront preorder flag while another open PO should keep it on. - Retrospective apply: new rules can be applied to existing matching POs in one batch operation. - Use case: Storefront badges keyed off “is something on order,” 3PL integrations, internal dashboards. ### Writing dates to kits (Assemblified) If you build kits or assemblies in Assemblified, you usually order their components (raw materials, virtual materials, sub-assemblies), not the finished kit. Turn on Also write to parent bills of materials (Assemblified), just below the main writeback switch, and your date rules (expected or requested delivery date) also write a date onto every kit those components go into. - Off by default, purchase orders only. Transfer-order rules don’t offer it. Quantity and true/false rules are not written to kits. - What the kit date means. Each kit’s date is worked out from all of its components that are on open purchase orders, plus any order for the kit itself, using the rule’s date setting (for example the earliest date). It is not a “complete kit” date: Logistified doesn’t check that every component is on order or in stock. If no component is on an open purchase order any more, the kit’s date is removed. - Only upwards. A component’s date goes to the kits that use it, including kits that use it through a sub-assembly. Ordering a kit never writes dates onto its components. - Kit date. With the switch on, date rules get a Kit date choice: Same as rule, Earliest, Latest, Newest or Oldest. Use it when the kit should show a different date than the components themselves, for example Latest so a kit only shows a date once its last component is due. - Existing values are overwritten. A date already on a kit’s metafield is replaced by the kit date. - When Assemblified can’t be reached. Logistified writes no kit dates for that change, and everything else is written as if the switch were off. A kit you order directly then gets its own order’s date for now. The next purchase-order change, Apply in “Apply to existing orders”, or Recompute kit values puts the kit dates right again. The Assemblified connection state is shown next to the switch: Connected, Connected — last check pending (Assemblified is in use here, but its latest check has not confirmed the connection yet), Connection not confirmed or Not connected. You can turn the switch on before Assemblified is connected. - Recipe changes. When you change a kit’s recipe in Assemblified, kit dates don’t update on their own. Click Recompute kit values (next to “Apply to existing orders”) or wait for the next purchase-order change. Recompute goes through every kit date Logistified wrote, shows its progress, and tells you if some kits couldn’t be checked or changed while it ran, so you can run it again. - Cleaning up. When you turn off the kit switch or the main writeback switch, or delete a rule (or change its metafield or whether it writes to products or variants), Logistified asks “Also clear the kit values Logistified wrote?” if it wrote any. Keep kit values saves and leaves the dates as they are. Clear kit values saves and then removes the kit dates Logistified wrote. After turning off only the kit switch, a kit that is itself on an open purchase order keeps the date from its own order. After turning off the main switch, every kit date Logistified wrote is removed. After deleting or changing a rule, its kit dates are removed, also on kits that are themselves on open purchase orders, unless another rule writes to the same metafield. Cancel saves nothing. A date that was already on its way to Shopify can take a minute to settle; run the clean-up again if a kit still shows an old date. - Getting dates onto kits right away. Kits get their dates with the next purchase-order change that touches one of their components. To fill them in at once for orders that are already open, use Apply in “Apply to existing orders”. ## Product tags on transition - Where: Settings → Purchase Orders → Product Tags tab. - What it does: applies (or removes) a Shopify tag on the linked product / variant when a PO transitions between statuses. - Per tag, configure: - Apply statuses: operator picks which transitions trigger the apply. - Remove statuses: operator picks which transitions trigger the remove. - Removal policy: always (always remove) or protected (only remove if no other active PO holds this product). - Not hard-coded. You can wire Sent → apply / Completed → remove if that’s typical, or any other combination that matches your storefront’s needs. ## Constraint rules - Where: Settings → Purchase Orders → Constraints tab. - What it does: opens [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/), where you build purchase-order rules from presets such as MOQ, pack size, Product MOQ, supplier minimums, CBM/weight caps, group rules, and bundle ratios. - Editor behavior: rules can be previewed against sample data or a real PO before saving. The Advanced graph remains available for debugging/power users. - Inputs: rules can bind built-in PO fields, Product & variant attributes, and Data Modeling semantic mappings. - Runtime: saved rules show as PO line-item badges and purchase-order hints. Optimizer-target rules also guide the [Constraint optimizer] (/features/supply-orders/purchase-orders/optimizer/). - Limits: active rule statuses are Draft and Sent. Rebalance/reduce/remove optimizer plans are not available yet; the active optimizer mode is Fill gaps. - Elevate plan only. ## Email templates - Where: Settings → Purchase Orders → Email Templates tab. - What it does: subject + body for the supplier email per PO event. - Placeholders: supports things like supplier name, PO number, your shop name. If you haven’t set a phone number in your sender details, the default “If you have any queries, please call us at …” line is left out of the email instead of printing an empty number. Text you wrote yourself around {PHONE_NUMBER} is kept as you wrote it. - Per-supplier overrides: you can assign a specific template as the default for a given supplier. When you send to that supplier, the override is used in place of the shop-wide template. - PDF attachment: each email template links to an export template, which drives the PDF layout / column set. Changing the export template changes the PDF the supplier receives. - Email text: the fixed words around your message can be changed per template under Email text: the document name in the header (“Purchase order”), the “Attachment” label, the inbox preview, the reply note, and the footer’s “Sent by … via”. Leave a field empty to keep the English text. Use {PO_NUMBER} and {SENDER} where the PO number and your sender name should appear. The footer always ends with “Logistified”. The template’s saved text is used every time you send or resend with it. ## Export templates (CSV / XLSX / PDF) - Where: Settings → Purchase Orders → Export tab. - Line-item templates: two separate sections, two separate template types. XLSX/CSV templates drive the column set and order of CSV / XLSX outputs; PDF templates drive the layout and styling of the PO PDF (and the supplier-email attachment). A template is one type or the other, never both. Between them they cover bulk line-item export, individual PO export, supplier emails, and PDF attachments. - Purchase-order-level templates: drive the global PO-list CSV / XLSX export that creates one row per PO with supplier, location, status, totals, payment, and paid-status fields. These templates are not used inside an individual PO and are not attached to supplier emails. - Per template: XLSX/CSV templates carry column selection and order. PDF templates carry date-field mapping, optional PDF date labels, and layout config (totals visibility, address formatting, compact layout, which standard line-item columns show, and whether a line you’ve [split into several dated deliveries] (/features/supply-orders/purchase-orders/delivery-schedules/) prints its breakdown under the quantity). The logo and company details are shop-wide and come from the General tab, not from the template. Blank date-label fields keep the default labels. - PDF text and date format: a PDF template can replace the fixed words on the purchase order PDF (“Purchase Order”, “Supplier Information”, “Ship To:”, “Order Details”, “Timeline”, “Payment Terms”, “Total”, “VAT ID”, the barcode labels and every other fixed word) in the Document text section, for example to send a German PDF to German suppliers. Each field shows the current English text; leave it empty to keep it. The Date format choice under Dates prints every date as October 16, 2026, 16.10.2026 or 2026-10-16. Logistified does not translate for you; you type the words. Use one PDF template per language and set it as the default for those suppliers. - Column picker: on CSV / XLSX templates, the available-columns list is searchable and grouped by source, with collapsible groups and a per-group Select all / Clear toggle. The line-item catalog includes live inventory, planning-constant, and ABC / revenue columns read from your Logistified data at export time, none selected by default. PDF templates use their own fixed set of standard line-item columns instead. Details at [Exports → Finding a column] (/features/supply-orders/purchase-orders/exports/#finding-a-column-in-a-large-catalog). - Per-supplier defaults: available for line-item / PDF templates. PO-level templates are global list templates and do not have supplier assignment controls. - Selectable at export time: override the default by picking a template in the export dialog. - Multiple presets: save many; use the right one for each downstream system. ## Import templates - Where: Settings → Import Templates (under the Data Import group in the settings sidebar). - What it does: column-mapping presets for bulk uploads: PO line item data, supplier links, variant overrides. - Linked to: the unified import flow that appears wherever you click “Import” (PO list, add-line-items dropdown, etc.). ## Label printing - Where: Settings → Label Printing. Four tabs: - Simple Mode: defaults for the rule-based label PDF (label size, barcode style, fields shown). - Advanced Designer (Beta): template-driven layout for custom designs. Build per-template field placements, font sizes, alignment. - Test Print: generate a sample label PDF from real PO data without committing settings, so you can verify physically before saving. - Preferences: shop-wide defaults shared by both print modes: PDF page layout, bottom layout (size & price), label print order, and price format (with a preview to sanity-check formatting). - No full live layout preview yet: Test Print is the closest approximation. ## Document tags - Where: Settings → Purchase Orders → Document Tags tab. - What it does: defines categories for documents you upload to a PO: Quote, Invoice, Receipt, custom labels. - Why: each tag has its own colour, so the Type badge on the Documents card tells you at a glance what a file is. You can also type a brand-new type straight into the upload dialog; defining it here just gives it a colour and keeps the naming consistent. There is no document-type filter or report yet. ## Adjacent settings that affect POs Setting Effect on POs Settings → Email Sending Email prefix (sender address), reply-to addresses, sender name. Required before any PO email can be sent. Settings → Carriers The carrier dropdown in the Shipping card on the PO. Settings → Locations & overrides The “from” address on the PO PDF (location overrides apply at PDF render time). Supplier row (Suppliers detail) Default payment terms, default currency, default tax rate, default email-template assignment, inherited by new POs from this supplier. ## What settings don’t exist yet Knowing what’s missing helps you triage “is this a setting I haven’t found, or is it genuinely unavailable?” - Per-line tax override on product line items: workaround: split the PO. (Additional cost / discount entries carry their own rate.) - Per-shop default constraint rule set applied at PO creation: rules are evaluated but not auto-applied to ordered quantities at creation. - “Send test email” button: templates can only be tested by triggering a real status change (or by using Test Print for label printing). - Automatic credit application on PO creation: credits are applied manually. - Auto-cancel of applied credits when a PO is cancelled: credit applications must be reversed manually. - Bulk re-send of failed emails: re-send is per-PO from the actions menu. - Full live layout preview in label printing settings: Test Print is the workaround. Note Each settings change applies to future POs by default. Existing POs hold the values they had at creation time, except where the setting is read at action time (tag triggers, export template selection at PDF generation). Tip When in doubt about which settings page to open, search the Settings sidebar; every page is one click away. ## See also - [Preferences] (/features/supply-orders/purchase-orders/preferences/): runtime toggles (auto-sync, label default format, incoming tracking). - [Constraint Studio] (/features/supply-orders/purchase-orders/constraints/): configure PO constraints. - [Settings → Overview] (/features/settings/overview/): the full settings index. - [Side effects & integrations] (/features/supply-orders/purchase-orders/side-effects/): what the settings change. - [Creating a PO] (/features/supply-orders/purchase-orders/creating/): when the defaults get applied, including the address profiles. - [Exports → Addresses on the PDF] (/features/supply-orders/purchase-orders/exports/#addresses-on-the-pdf): how the billing, supplier, and delivery blocks are resolved on the printed order. - [Delivery schedules] (/features/supply-orders/purchase-orders/delivery-schedules/): splitting a line into several dated deliveries, and the PDF template toggle for its breakdown. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/overview/ # Transfer orders Move stock between two of your own locations. In Logistified, a [transfer order] (/reference/glossary/#transfer-order) records moving stock between two of your own locations. Common uses: rebalancing between a warehouse and a retail store, or shifting stock to a fulfilment hub. On the Elevate plan, the destination can be a supplier instead of a location: see [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/). It can also be a location of another store connected through Multi-Store: see [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/overview/). Transfer orders are not POs. POs go to a supplier and bring inventory in. Transfer orders move existing inventory you already own, normally between your own locations, or (on Elevate) out to a supplier who holds it for you. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Lifecycle] (/features/supply-orders/transfer-orders/lifecycle/) The 7 statuses (including Completed) and the Resumed action. [Search, filters & saved views] (/features/supply-orders/transfer-orders/search-and-filters/) Search the list, filter by status/date, and save shop-wide presets. [Creating a TO] (/features/supply-orders/transfer-orders/creating/) Blank, CSV/XLSX, min/max, forecast, sales, or from orders. [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) Elevate: ship to a supplier who holds the goods as your stock instead of a location. [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/overview/) Elevate: send stock to a connected store, accept its transfers, or ask it for stock. [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/) What moves where on each transition. [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/) One shipment per TO; partial receipts; discrepancies. [Materials from Assemblified] (/features/supply-orders/transfer-orders/assemblified-materials/) See the raw materials and sub-assemblies a transfer will use before you send. [Exports] (/features/supply-orders/transfer-orders/exports/) Bulk CSV / XLSX export: line-item or transfer-order-level. [Settings] (/features/supply-orders/transfer-orders/settings/) TO-specific preferences. ## Key concepts - [Transfer order] (/reference/glossary/#transfer-order): the artifact itself. - [Origin location] (/reference/glossary/#origin-location): where stock leaves. - [Destination location] (/reference/glossary/#destination-location): where stock arrives. - [Planned quantity] (/reference/glossary/#planned-quantity): what you intend to move. ## Where to next - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): for drift between Logistified and Shopify. - [Line-item column views] (/features/supply-orders/line-item-views/): choosing and saving the columns on the line-item table. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/lifecycle/ # TO lifecycle The 7 statuses, the status flow, and what you can edit at each. In Logistified, a transfer order moves through up to 7 statuses, plus a “Resumed” action that returns it from On Hold to an active state. This page is the reference. ## On this page - The 7 statuses - Status flow - Mutability: what you can edit at each status - Removing several lines at once - Resume from On Hold - See also ## The 7 statuses Status What it means Typical entry Draft You’re composing the TO. No effect on inventory yet. New TO created. Sent The TO has been dispatched. Source on-hand is decremented; destination incoming is incremented. You click Send. Partially Received Some lines received; others outstanding. First receipt at the destination. Received All lines received. Last receipt. Completed Closed for reconciliation. Unlocks the post-completion tools: Fix On Hand Quantity, Fix Negative Incoming, and Adjust Incoming Quantity. You click Complete from Received (or directly from Partially Received). On Hold Paused mid-flow. You click Put On Hold. Cancelled Order cancelled. You click Cancel. Resumed is a transition action, not a status. From On Hold, the Resume (Sent) menu item returns the TO to Sent. ## Status flow ``` Draft → Sent → Partially Received → Received → Completed ↓ ↓ ↓ On Hold (Resume → Sent) ↓ Cancelled (available from Sent, Partially Received, Received, On Hold) ``` The detail page also exposes step-back actions (Revert to Draft (from Sent) and Revert to Sent (from Partially Received or Received)) for the rare case you need to undo a status change. These don’t change inventory in unexpected ways: each transition runs the same sync logic as a fresh forward move. [anchor: mutability--what-you-can-edit-at-each-status] ## Mutability: what you can edit at each status Status Add lines Delete lines Edit planned quantity Edit received quantity Edit shipping Draft yes yes (single or bulk) yes n/a yes Sent / Partially Received no individual lines only (no bulk) no yes yes Received no individual lines only (no bulk) no no yes On Hold mirrors the status it was paused from mirrors mirrors mirrors mirrors Completed no no no no no: use the post-completion tools for reconciliation Cancelled no no no no no Past Draft, you can’t add new lines. To add a forgotten SKU, use the Split Transfer Order action (see [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/#splitting-a-to)) or cancel and recreate. Single lines can still be deleted while the TO is Sent, Partially Received, or Received. ## Removing several lines at once While a transfer order is in Draft, the line-item table gains a checkbox on every row and one in the header, handy when a transfer generated from your forecast or from sales brings in more than you want to send. - Tick individual rows, or use the header checkbox to take everything the table is currently showing. It only ever covers the filtered rows, so searching first and then ticking the header is the quick way to clear out one vendor or one search term; the box shows a half-tick while only some of the visible rows are selected. - A Remove selected (N) button appears next to the search box once at least one row is ticked. - Clicking it asks you to confirm (“Remove N line items?”) before anything happens. Removing lines can’t be undone, so the confirmation is deliberate. The checkboxes and the button disappear the moment the TO leaves Draft; from Sent onwards, lines can only be deleted one at a time. ## Resume from On Hold From On Hold, the only Resume option in the menu is Resume (Sent); it puts the TO back into Sent. If you need to step further back than that (e.g., back to Draft), resume into Sent first, then use Revert to Draft. Caution Cancelling a TO that’s already Sent does not reverse received quantities; they stay where they are for the audit trail. The cancellation only zeros out remaining incoming at the destination and adds back the still-unshipped quantity to source on-hand. You may need a stock take to clean up. ## See also - [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/): what moves where on each transition. - [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/): partial receipts, splitting, discrepancies. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/search-and-filters/ # Search and filter transfer orders Search the transfer order list, filter by status or date, and save shop-wide filter presets. Logistified’s transfer order list has a search box, a set of filters, and named presets that save a filter set (including the search term) for everyone in the shop to reuse. ## On this page - Searching the list - AI search - Adding and editing filters - Available filters - Saving a filter set as a preset - Setting a shop default - Renaming and deleting presets - Edge cases & current behavior ## Searching the list Type into the search box to match against the TO number or a line’s variant title. The list updates shortly after you stop typing; clearing the box (the × inside it) updates immediately. The search term is shareable; it’s reflected in the page’s URL, so a bookmarked or copied link reproduces the same search. ## AI search You can also describe the transfers you want. Click into the search box and press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English and press Enter. A preview shows the filters it understood (status, destination, created by, tags and a date period), and nothing changes until you click Apply. For example: - “sent transfers to Hamburg that Ben Carter created last month” - “transfers received in the last 7 days” Only the destination is used as a location: in “transfers from Berlin to Hamburg”, Hamburg becomes the filter and “from Berlin” isn’t used, because the list has no source-location filter. If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/) for the full walkthrough. ## Adding and editing filters Click + Filter to open the filter picker: choose a field, then set its value. Each active filter appears as a chip below the toolbar; click a chip to edit it, or the × on the chip to remove it. Clear all removes every filter and the search term in one step. ## Available filters - Status: one or more of the 7 statuses (Draft, Sent, Partially Received, Received, Completed, On Hold, Cancelled). See [The 7 statuses] (/features/supply-orders/transfer-orders/lifecycle/) for what each means. - Destination: one or more destination locations, plus a pinned At supplier entry for TOs [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) rather than a location. The At supplier entry is available on every plan, so you can still find those TOs even if your shop is no longer on Elevate. A pinned Connected store entry finds the TOs you [sent to a connected store] (/features/supply-orders/transfer-orders/inter-store/sending/); it shows once your store exchanges stock with other stores. - Created by: one or more of the people who have raised a transfer order, so you can narrow the list to a colleague’s orders. Orders created by a connected AI assistant or an API key are listed under that connection’s name. - Date: a date range on when the TO was created, with quick choices for Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month, alongside custom from/to dates. Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. The list also carries a Created by column next to the dates, and each transfer order shows the same information as a line under its title on the detail page; hover it for the creator’s email address. Transfer orders raised before this was introduced, and ones created automatically, show only a date. ## Saving a filter set as a preset Once your filters or search term differ from whatever preset is currently active (or from All, the unfiltered default), a Save button appears next to the filter bar: - Save overwrites the currently active preset with your current filters and search term. - Save as… prompts for a name and creates a new preset, which becomes the active one. A preset saves the whole query: every active filter and the search box’s contents. Selecting a preset later applies both; selecting All clears both. Note Presets are shared by the whole shop, not private to your account. Anyone who saves, renames, stars, or deletes a preset changes it for every staff account viewing the transfer order list. ## Setting a shop default Open the preset switcher and use the star action on a preset to make it the shop’s default. The starred preset’s filters and search term are applied automatically the next time anyone opens the transfer order list with a plain, unfiltered link; a link that already carries filters or a search term (a bookmark, a shared link) always takes priority over the default. Only one preset per shop can be starred at a time; starring a different one clears the previous default. ## Renaming and deleting presets Both actions are available from the preset switcher. Deleting the preset you currently have selected drops the switcher back to All, but leaves your current filters and search term exactly as they were; only the saved preset itself is gone. ## Edge cases & current behavior - A shared link can name a preset that’s since been deleted. The link still applies whatever filters and search term it carried; the switcher just falls back to showing All since the preset it pointed at no longer exists. - The transfer order list no longer supports the older, browser-only “Save Filters” default. Filter presets are now saved to the shop, not to your browser, so they’re the same for you on any device and for every other operator. - The remembered page size is separate and still per-device. How many rows you see per page keeps following your own browser; it isn’t part of a saved preset. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/creating/ # Creating a TO Six creation paths: blank, CSV/XLSX, min/max, forecast, sales, or from orders. Logistified offers six ways to create a transfer order: blank, from a CSV/XLSX file, from min/max levels, from the forecast, from sales, or from orders. ## On this page - Creation paths - The min/max creation flow - The forecast creation flow - The sales creation flow - The from-orders creation flow - Creating a sales order from a TO - The same-location guard - Settings that affect creation - See also ## Creation paths Open Supply Orders → Transfer Orders. The Create Transfer Order dropdown offers: Path Menu item Notes Blank Create Empty TO Pick origin + destination, then add lines manually on the detail page. On Elevate, the destination can be a supplier instead of a location: see [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/), or a connected store: see [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/sending/). From CSV/XLSX Import from CSV/XLSX Bulk-create one or more TOs from a spreadsheet. Rows are grouped by from + to location pair. Rows where origin = destination are flagged and skipped. From min/max Create from Min/Max Picks variants whose destination stock is below your trigger threshold and the source has enough surplus to refill them. From forecast Create from Forecast Uses your demand forecast to move surplus from the origin to cover a predicted shortfall at the destination. You pick the two locations and a strategy, then review the recommended quantities before creating. From sales Create from Sales Moves the number of units sold over a period you choose, from the origin to the destination, capped at what’s available at the source by default. From orders Create from Orders Build one TO by picking line items off one or more sales orders. Also available from the Orders tab, per order or in bulk. When your store exchanges stock with other stores through Multi-Store, the menu ends with Request stock from a connected store. It doesn’t create a TO in your store: it asks the other store to send you stock. See [Stock requests] (/features/supply-orders/transfer-orders/inter-store/stock-requests/). ## The min/max creation flow You pick one origin and one destination, then choose three rules: - Trigger: when does a destination need stock? Choose minimum inventory, reorder point, or target inventory. The TO will only include variants whose destination on-hand is below the chosen level. - Refill: how high do you want to top up to? Choose reorder point, target inventory, or max inventory. The refill level must be higher than the trigger level (the dialog hides invalid combinations). - Source policy: how much of the source’s stock are you willing to move? - Cap at available stock (default): never propose more than the source actually has on hand. - Ignore levels at source: take whatever’s needed, even if it would leave the source negative. - Keep source at target / reorder point / min: leave at least that much at the source after the move. You can also set a minimum transfer quantity to skip variants where the calculated move is too small to be worth it, and add variant filters to narrow the flow to a subset of your catalog (a single vendor or product type, for example). A Location-Specific Destination Stock switch (on by default) decides how the trigger and refill levels are evaluated: with it on, they compare the destination location’s own stock; with it off, they compare stock across all locations combined. Source-side stock and the source policy floors always stay specific to the source location. When you preview with this switch off, the preview table is badged global destination stock and its Stock column is relabeled to make the wider comparison clear. Choosing Preview calculates the recommended quantities and opens an editable table: From/To stock plus the trigger and refill thresholds you chose, one row per variant. Adjust or remove any line, then Create Transfer Order; the Draft only ever contains variants that were in the preview. Quantities are re-checked against current stock at creation (they may differ from the preview in either direction), and increased quantities are capped at what the source location can supply under the chosen source policy (only Ignore levels at source is unbounded). Caveats: - Variants without the relevant override at the destination (e.g. no minInventory if you chose the minimum-inventory trigger) are skipped. - If you pick Keep source at target / reorder point / min and a variant has no such override at the source, it falls back to transferring the full needed quantity for that variant. - If you pick Ignore levels at source, source on-hand isn’t protected; review the preview before creating. ## The forecast creation flow This flow uses your demand forecast to rebalance stock: it moves surplus from the origin to cover a forecasted shortfall at the destination. You pick one origin and one destination, choose a strategy, then review the recommended moves before creating. Strategy: - Deficit / surplus (default): move just enough surplus from the origin to cover the destination’s forecasted shortfall. Two sub-options shape it: - Refill the destination to cover its coverage horizon (default) or its lead-time period. - Trigger a refill when the destination falls below its reorder point (default) or below its target. - Equalize days of supply: level out the days-of-stock between the two locations instead of refilling to a fixed target. The refill and trigger options above don’t apply here, so they’re hidden. There’s also a one-click Warehouse → selling preset for the common case of a non-selling warehouse feeding a store; it sets the deficit/surplus strategy to release stock to the selling location even when the warehouse itself has no forecast demand. Other controls: - Allow the origin to drop to: how much to protect at the source after the move: its reorder point (default), target, minimum, or ignore (move whatever’s needed). - Forecast basis: use global demand for both locations (default), or each location’s own sales history. - Minimum transfer quantity: skip moves smaller than this (default 0). - Count incoming stock toward availability (default on). - Round transfers down to pack size (default off). You can run the forecast from a saved view (locked: it uses that view’s filters and settings as-is) or from custom settings you configure in the dialog. Either way you get an editable preview of the recommended quantities, and your edits are kept when you create the Draft TO. Note With global demand, both locations share the same predicted demand, which can legitimately produce no recommended transfers; you’ll see a friendly empty state rather than an error. ## The sales creation flow You pick one origin and one destination, a period, and a sales scope. Logistified totals the units sold over that period and moves them from the origin to the destination. Sales dates use the timezone configured for your Shopify store, shown beside the period controls. Last N days includes today in that timezone; you can also choose a single calendar day. Create keeps the dates from the preview, including if you confirm after midnight. Changing the sales settings requires a fresh preview, as does a changed store timezone detected by Logistified. If the timezone cannot be loaded, choose Retry; your order details are kept. - Sales scope: whose sales to count: - Destination location (default): units sold at the destination. - Origin location: units sold at the origin. - Global: units sold everywhere. - Cap at source (default on): never move more than the origin actually has. Turn it off (Allow source to go negative) to move the full units-sold figure regardless of source stock. - Count incoming stock at the source toward the cap (default on). - Include zero-quantity rows (default off): when on, variants that compute to 0 (e.g. no source stock) still appear in the preview so you can bump them. The preview is editable. An override can exceed source availability, forcing a line even when the source shows 0. Creating produces a Draft TO. ## The from-orders creation flow Build a single TO by picking line items off one or more sales orders, useful when you want to move exactly what specific orders need. Entry points: - Orders tab (Supply Orders → Orders): select orders and use Actions → Create TO from selected orders, or use a single order’s … → Create TO from Order. - Transfer Orders list: Create Transfer Order → Create from Orders, then click Add More Orders to pick orders. How it works: - Review the line items in your cart, adding more orders as needed. - Pick the From and To locations. With exactly two active locations they’re pre-filled; with more, you choose. You need at least two active locations, and origin must differ from destination. - Quantities default to the ordered quantity and are fully editable. They are not capped against the origin’s stock. - The same variant appearing on several orders merges into one line with the quantities summed; the line shows which orders it came from. Once created, each contributing order shows a TO badge on the Orders tab linking to the new transfer order, and you can filter the Orders tab by Has Transfer Order. ## Creating a sales order from a TO This is the reverse direction: from a transfer order’s detail page, Actions → Create sales order turns the TO’s line items into a Shopify draft order. - Choose whether to tag the draft to the origin or destination location, then pick which lines to include and adjust quantities. - The draft is created in Shopify with the TO number and location recorded as tags, custom attributes, and a note. Note Shopify draft orders can’t be bound to an inventory location when they’re created, so the location is recorded as metadata only: Shopify still routes fulfillment and inventory itself. Use the tags and note to route it manually on Shopify’s side if you need to. After creation, the TO shows a Linked sales order → Open in Shopify row; creating again overwrites the link. The action is disabled when the TO has no line items, and system-generated lines (placeholder or custom variants that aren’t real Shopify products) are left out automatically. ## The same-location guard You can’t pick the same location as origin and destination; every creation dialog (blank, min/max, forecast, sales, and from-orders) and the edit dialog all block it. The CSV importer warns and skips any rows where the two locations match, rather than blocking the whole upload. This guard doesn’t apply when the destination is a supplier (see [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/)); a supplier is never treated as one of your locations. ## Settings that affect creation - Default carrier: Settings → Carriers. Populates the carrier dropdown on the shipment card. - Email template: Settings → Transfer Orders → Email Templates. Default subject + body used when you send a TO notification. - Product tags: Settings → Transfer Orders → Product Tags. Each tag is per-tag configurable: you choose which TO statuses auto-set it and which ones auto-remove it. Tags with no auto rules are manual-only. Note Transfer orders don’t carry a tax rate; they’re internal moves between your own locations, no tax. ## See also - [Lifecycle] (/features/supply-orders/transfer-orders/lifecycle/): what happens after Draft. - [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/): what each transition does to inventory. - [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): the Elevate destination option, and where it’s offered. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/supplier-destination/ # Ship to a supplier Send a transfer order from one of your own locations to a supplier, who receives and holds the goods as your stock instead of a warehouse. [Elevate plan] (/reference/subscription-plans/) A Logistified transfer order normally moves stock between two of your own locations. It can instead ship to a supplier, who receives the goods and holds them on your behalf: the stock leaves one of your locations, but instead of arriving at another one, it’s recorded as your stock sitting at that supplier. Use it when you’re staging stock with a manufacturer, finisher, or 3PL before it goes back into a location, the mirror image of [buying from one supplier and delivering to another] (/features/supply-orders/purchase-orders/deliver-to-supplier/), but starting from your own shelf instead of an order you place. ## On this page - What makes a TO a supplier-destination TO - Creating one - The holding supplier and its address - Where these TOs show up - Sending - Receiving at the supplier - Unreceiving - What this does to your inventory numbers - Documents and exports - Limits - See also ## What makes a TO a supplier-destination TO Every transfer order has an origin location. Its destination is normally another one of your locations, but it can be a supplier instead: Flow Feature buy from supplier A → deliver to B [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) (PO) supplier → my location [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/) my location → supplier This page The goods really do leave your origin location; a supplier-destination TO decreases on-hand there exactly like any other transfer. What’s different is the other end: there’s no destination location to receive into, so the arrival is recorded as your stock held at the supplier instead. Note Shipping a transfer order to a supplier needs the Elevate plan; the goods are recorded as supplier-held stock, an Elevate capability. On a lower plan the option isn’t offered when creating or editing a TO. Orders you already have stay fully visible and workable: you can find them, receive them, export them; the plan only gates picking or changing the destination itself. A downgrade never silently rewrites an existing order’s destination back to a location. ## Creating one Open Supply Orders → Transfer Orders → Create Transfer Order → Create Empty TO, pick your origin location, then open the destination picker and choose Ship to a supplier (held as your stock); it sits below your locations, described as “The supplier receives and holds the goods for you.” A Holding supplier field appears once you pick it. You can also switch an existing TO onto this destination while it’s still Draft: open it, edit the header, and pick the same entry from the destination picker. Those two places are the only ones. Create from Min/Max, Create from Forecast, Create from Sales, and Create from Orders all keep the ordinary two-location picker, and the CSV/XLSX importer refuses a supplier destination outright: “Imported transfer orders cannot ship to a supplier; create the transfer order from the transfer orders list and pick the destination supplier there.” Copying a TO and Split Transfer Order both carry the destination, the holding supplier, and its address to the new order, so a copy or a split-off remainder stays sendable without re-picking anything. ## The holding supplier and its address The Holding supplier field lists your suppliers. Picking one snapshots its address onto the transfer order as the destination address; from then on it belongs to the TO, so you can edit it there if this shipment goes somewhere other than that supplier’s address on file, and your edit sticks. If the holding supplier has no address on file, the TO’s Locations card shows No address on file for this supplier. Add one before sending. in place of an address, and sending is blocked until one exists. Caution The destination and the holding supplier can only be set or changed while the TO is Draft; changing them later is treated the same as changing the destination location itself, which the ordinary [Draft-only editing rules] (/features/supply-orders/transfer-orders/lifecycle/#mutability--what-you-can-edit-at-each-status) already lock down. Switching a TO back to an ordinary location destination clears the holding supplier but keeps the address you had, as your own override. ## Where these TOs show up - Transfer orders list: an At supplier badge sits next to the TO number, and the list’s Destination filter gains a pinned At supplier entry above your real locations, the only way to filter these TOs in, since they have no destination location of their own. It stays available on every plan, so a shop that moves off Elevate can still find the orders it has. - Detail page: the information card’s destination tile reads At supplier: instead of a location name, and the same badge sits beside the TO number. The Locations card’s To side shows the holder above the snapshotted address. - Supply orders dashboard: wherever the dashboard shows a TO’s destination, these read At supplier: and are searchable by either “at supplier” or the holder’s name. - Adjust incoming: this post-completion tool refuses on a supplier-destination TO with its own message: “This transfer order ships to a supplier, so no Shopify location carries incoming for it and there is nothing to adjust.” There’s simply no Shopify location to adjust. ## Sending Send needs all three of these before it will run, and names whichever is missing: - An origin location: the goods still have to leave a warehouse. - A holding supplier. - An actionable address for that supplier (street, city, postal code, or country). ## Receiving at the supplier Receiving works through the same Receive Items dialog as any other TO, full or partial, one or several passes. The difference is where the quantity lands: it’s recorded as your stock at the holding supplier rather than moved into a Shopify location, so nothing changes in Shopify’s inventory at any point in the receive. Note Received quantities on a supplier-destination TO can’t be lowered from the receive dialog; the recorded stock at the supplier has to be reversed along with the received quantity, and that only happens safely through a status change. To correct an over-entered receive, use Revert to Sent to unreceive the line, then receive it again with the right quantity. ## Unreceiving Reverting a supplier-destination TO’s receipt removes the matching quantity from your recorded stock at the supplier, but only what’s still free to take back. If some of that stock has already moved on (reserved or released by a supplier stock release), the revert is refused rather than reaching into stock that’s no longer just sitting there. ## What this does to your inventory numbers - Origin on-hand decreases at Send, exactly like an ordinary transfer. - Nothing happens at a Shopify location on the destination side, ever; there’s no destination location on this TO, so there’s nothing for Shopify to update there. - No Shopify incoming is raised at any point. A supplier-destination TO doesn’t track incoming the way a warehouse TO does, because incoming exists to warn a location about stock headed its way, and there is no such location here. - Forecasting: a location-scoped view of incoming never counts these TOs, since they have no destination location to count against. A shop-wide view of incoming keeps counting them while they’re open; the goods are still yours, just in transit to a supplier instead of a location. - Once received, the stock appears under Suppliers → the holding supplier → Variants → My stock at supplier, the same place [deliver-to-supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) purchase orders leave their held stock. A [supplier stock release] (/features/supply-orders/supplier-stock-releases/overview/) against that supplier is what eventually brings it into a location. ## Documents and exports - PDF: the To Location block gains a line: Deliver to: , holding these goods on our behalf. - CSV / XLSX exports: seven Destination columns (company name, two address lines, city, ZIP, country, phone) carry the holding supplier’s snapshotted address on these TOs, and the ordinary destination location’s address on every other TO. Add them from a [line-item or transfer-order-level export template] (/features/supply-orders/transfer-orders/exports/#export-templates) like any other column. The existing To Location columns stay blank on a supplier-destination TO; there’s no location to read. ## Limits - Elevate plan required to create one or to switch a TO onto this destination. - Only Create Empty TO and editing a Draft TO offer it; the min/max, forecast, sales, and from-orders creation flows, and the CSV/XLSX importer, don’t. - The destination and holding supplier are Draft-only, locked once the TO is sent. - One holding supplier per TO: there’s no splitting a shipment between a supplier and a location on the same order. - Received quantities can only be lowered by reverting to Sent and receiving again, not directly in the receive dialog. - Not available from a [Shopify POS] (/features/pos/overview/) device: receive these TOs from the transfer order’s own detail page. ## See also - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): the purchase-order sibling this mirrors, and where the destination-address export columns pattern comes from. - [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/): bringing supplier-held stock into a location. - [Creating a TO] (/features/supply-orders/transfer-orders/creating/): the rest of the creation paths. - [Search, filters & saved views] (/features/supply-orders/transfer-orders/search-and-filters/): the Destination filter’s At supplier entry. - [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/): the receive flow this destination reuses. - [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/): what an ordinary TO does to inventory, for comparison. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/overview/ # Inter-store transfers Move stock between your Shopify stores that run Logistified and are connected through Multi-Store. [Elevate plan] (/reference/subscription-plans/) An inter-store transfer moves stock from one of your Shopify stores to another. Both stores run Logistified and are connected through [Multi-Store] (/features/settings/multi-store/). The sending store books the stock out of one of its locations. The receiving store accepts the transfer and picks a location, and the moment it accepts, the stock is in that location’s available stock. There are two ways to start one: - Send a transfer (push): you create a transfer order to a connected store and send it. - Ask for stock (pull): you send a stock request to a connected store. That store turns it into a transfer order and sends it to you. ## On this page - Pages in this section - Which stores can exchange stock - What happens to your stock - Where you find it - Plan - Limits - See also ## Pages in this section [Setting up] (/features/supply-orders/transfer-orders/inter-store/setup/) Switch inter-store transfers on for a connection and get your products ready. [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/) Create a transfer order to a connected store, send it, or withdraw it. [Receiving a transfer] (/features/supply-orders/transfer-orders/inter-store/receiving/) Accept an incoming transfer into one of your locations, or decline it. [Stock requests] (/features/supply-orders/transfer-orders/inter-store/stock-requests/) Ask a connected store for stock, and answer requests from other stores. [Troubleshooting] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/) Needs attention, retries, force cancel, and closing a thread. ## Which stores can exchange stock Multi-Store has one main store and one or more additional stores. - The main store and each of its additional stores can send each other transfers. - Two additional stores of the same main store can send each other transfers too. Their messages travel through the main store, so the main store’s connection to each of them needs inter-store transfers switched on. - Two main stores can’t send each other transfers. Each store must be on the Elevate plan, and the connection must have Inter-store transfers switched on. See [Setting up] (/features/supply-orders/transfer-orders/inter-store/setup/). ## What happens to your stock There’s one transfer order in each store. The sending store’s transfer order ships to a connected store. The receiving store’s transfer order is created when it accepts. Moment Sending store Receiving store You send Available stock at the origin location goes down. The transfer order is Sent. Nothing yet. The offer arrives Nothing changes. The offer waits under Incoming. No transfer order, nothing in Shopify. The other store accepts The transfer order is received and completed. Nothing changes in Shopify. A transfer order is created, and the accepted units go straight into available stock. Completed. The other store declines The transfer order stays Sent. Cancel it to get your stock back. Nothing is created. You withdraw (Cancel) The transfer order is cancelled and the stock comes back. The offer is gone. Accepting is the receipt: the receiving store doesn’t receive the goods in a second step. No Shopify incoming is raised in either store, so stock on its way doesn’t show as incoming at the receiving location. ## Where you find it These places show once Multi-Store is on and at least one connection has inter-store transfers switched on, or once your store already has an inter-store transfer. - Procurement → Inter-store: the Inter-store tile on the Supply Orders page, with the number of things waiting for you. It shows while Multi-Store is on. The page has four tabs: Incoming (offers and stock requests waiting for your answer), Outgoing (your open transfers and stock requests), History (exchanges that ended), and Needs attention. - Transfer orders list: a banner when something waits for you, for example 2 incoming transfers waiting · Review. Transfers to or from a connected store show a Partner store badge in place of the connected store’s location, and the Destination filter has a pinned Connected store entry. - Create Transfer Order menu: Create Empty TO lets you pick a connected store as the destination, and Request stock from a connected store opens a stock request. - Transfer order detail page: a Connected store transfer panel shows where the exchange stands in both stores. - Settings → Multi-Store → Messages: every message sent between the stores, and any that are stuck. Wherever the other end is a connected store, a Partner store badge marks it; in lists where every row is a connected store, the badge shows the store’s short name, for example other-store for other-store.myshopify.com. Hover over the badge, or tab to it, to see the full store name, its location and its transfer order number. The confirmation messages shown after an action name the store by its full Shopify domain. ## Plan Each store must be on the Elevate plan to start something new: send a transfer, accept one, send a stock request, or accept a stock request. The other store’s plan is checked too. Finishing or cleaning up an exchange that already exists never needs Elevate. A store that has left Elevate can still decline an offer or a stock request, withdraw its own request, cancel its transfer, retry a book-out or book-in, force cancel, close a thread, and use the Messages tab. On a lower plan the Inter-store page still opens, with a plan notice, and Accept is disabled. ## Limits - Read-only through the API and MCP. The REST API and a connected AI assistant can read transfers to and from a connected store, but can’t create, change or answer them. - Only two ways to create one. Create Empty TO and editing a Draft offer a connected store as the destination; accepting a stock request also creates one. Create from Min/Max, Create from Forecast, Create from Sales, Create from Orders and the CSV/XLSX importer don’t. - Products match by SKU only, not by barcode or title. - No cost or currency travels with the transfer. - Acceptance is final. A line accepted short stays short on both transfer orders. The units the other store didn’t accept are not booked back into the sending store automatically. - A declined transfer isn’t returned automatically. The sender cancels its transfer order to get the stock back. - Floormode locations. A location whose transfers Floormode runs can’t send to a connected store, and a location where Floormode receives the stock can’t receive one; the accept dialog says why. - No email alerts. Problems show under Needs attention on the Inter-store page. - Shopify POS can’t receive the sending store’s transfer order; the connected store receives it in its own store. Note Inter-store transfers move stock between two different Shopify stores. To move stock between two locations of the same store, use an ordinary [transfer order] (/features/supply-orders/transfer-orders/overview/). ## See also - [Settings → Multi-store] (/features/settings/multi-store/): connecting your stores. - [Guides → Multi-store setup] (/guides/multi-store-setup/): pairing a second store, step by step. - [Transfer orders] (/features/supply-orders/transfer-orders/overview/): moving stock between your own locations. Last updated: 7 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/setup/ # Setting up inter-store transfers Switch inter-store transfers on for a Multi-Store connection and get your products ready on both stores. [Elevate plan] (/reference/subscription-plans/) In Logistified, inter-store transfers are switched on per connection, on the main store. Once a connection has them on, the two stores can send each other transfers and stock requests. ## On this page - Before you start - Switch inter-store transfers on - Transfers between two additional stores - Get your products ready - See also ## Before you start - Both stores run Logistified and are connected through Multi-Store. If they aren’t yet, follow [Multi-store setup] (/guides/multi-store-setup/) first. - Each store is on the Elevate plan. ## Switch inter-store transfers on 1. On the main store: open Settings → Multi-Store. In the Connected Stores table, click the settings button of the store you want to exchange stock with (its tooltip reads Configure store settings). 2. Under Transfers between stores, turn on Inter-store transfers. 3. Click Save Settings. 4. On the additional store: open Settings → Multi-Store. Under Whitelist Management, the main store’s entry now shows the badge Inter-store transfers on, with Set by the main store beside it. The additional store can’t change this switch; only the main store can. New connections start with the switch off. Repeat the steps for every additional store that should send or receive stock. Both stores show the Inter-store tile on the Supply Orders page while Multi-Store is on. With the switch on, stores on Elevate also offer the Connected store destination when you create a transfer order, and Request stock from a connected store in the Create Transfer Order menu. Settings → Multi-Store has a Messages tab whenever Multi-Store is on. Caution If saving shows a warning that the settings may be out of sync with the connected store, the change was saved on the main store but didn’t reach the other store. Reconnect the store, then check the Inter-store transfers badge on the additional store again. ## Transfers between two additional stores Two additional stores of the same main store reach each other through the main store. For that, the main store’s connection to each of the two stores needs Inter-store transfers switched on. The main store passes the messages along; it never holds the stock. Two main stores can’t send each other transfers. ## Get your products ready Logistified matches products between the two stores by SKU only. For each product you want to move: - The SKU exists in both stores, on exactly one active variant in each. Two variants with the same SKU in one store can’t be matched. - It’s stocked at the location in Shopify: the location the stock leaves in the sending store, and the location it goes to in the receiving store. - It’s a real Shopify product that tracks inventory. Placeholder or custom lines that aren’t real Shopify products can’t go to a connected store. You don’t have to check this by hand. On a Draft transfer order to a connected store, the Partner match column shows each line’s status, and the receiving store sees the same check when it accepts. See [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/#check-the-lines). ## See also - [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/overview/): how it works. - [Settings → Multi-store] (/features/settings/multi-store/): the connection and its settings dialog. - [Troubleshooting] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/): the Messages tab, and what to do when a store is gone. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/sending/ # Sending a transfer Create a transfer order to a connected store, send it, follow it, or withdraw it while the offer is open. [Elevate plan] (/reference/subscription-plans/) You send stock to a connected store with an ordinary transfer order whose destination is that store. When you send it, Logistified books the stock out of your origin location and offers the transfer to the other store, which then accepts or declines it. ## On this page - Create the transfer order - Check the lines - Send it - Follow it on the detail page - Withdraw an offer - When the other store answers - What’s locked once it’s sent - Lists, documents and exports - See also ## Create the transfer order Open Supply Orders → Transfer Orders → Create Transfer Order → Create Empty TO. 1. Pick the From Location: where the stock leaves. 2. Under Destination, switch from This store to Connected store. 3. Pick the Connected store, then the Location at connected store: where the stock should arrive. Stores are listed by their short name, with the full Shopify domain underneath. The locations are that store’s active locations, read from it while the dialog is open. 4. Create the Draft and add lines as usual. You can also turn an existing Draft into a transfer to a connected store: edit its header and make the same choice. Switching a Draft back to This store removes the connected store from it. The Connected store option shows only on Elevate, and only when at least one connected store takes inter-store transfers. If none does, the dialog says “No connected store takes inter-store transfers yet.” See [Setting up] (/features/supply-orders/transfer-orders/inter-store/setup/). A few things can’t go to a connected store: - A From Location whose transfers [Floormode runs] (/features/supply-orders/transfer-orders/floormode-execution/). - Lines that aren’t real Shopify products, such as placeholder or custom lines. The other creation paths (Create from Min/Max, Create from Forecast, Create from Sales, Create from Orders, and the CSV/XLSX importer) always ship to one of your own locations. ## Check the lines On a Draft to a connected store, the line-item table gets an extra column, Partner match. It checks each line against the other store’s products at the location you picked. Hover over a status to see what it means and how to fix it: Status What it means Matched The other store has exactly one active product with this SKU, stocked at that location. Not found The other store has no product with this SKU. Duplicate SKU The other store has more than one product with this SKU. No SKU This line has no SKU, so there’s nothing to match on. Not stocked The product exists there but isn’t stocked at that location in Shopify. When a line, or a store’s plan, would stop the send, a notice above the table reads Send will be refused. It names the SKUs and how to fix them, for example “1 SKU is missing at the partner store: ABC-1. Remove it, or give a product there the same SKU, before sending.” Click a SKU to show its line in the table. The column is a preview: Send checks again. ## Send it Click Send. The Send Transfer Order dialog has one option, Send offer to partner store, already selected, and lists what happens next. Click Send offer. Before anything moves, Logistified checks that: - your store is on Elevate; - every line is a real Shopify product; - Floormode doesn’t run the From Location; - the other store is on Elevate and can be reached; - every line is Matched at the other store. If a check fails, nothing is booked out and the transfer order stays a Draft. The message names the problem, including the SKUs that don’t match. If every check passes: 1. The transfer order moves to Sent. 2. The units are booked out of available stock at the From Location in Shopify. 3. Once every line is booked out, the offer goes to the other store. It shows up there under Procurement → Inter-store → Incoming. No incoming is raised at the other store. The stock shows up there only when it accepts. Send via Email isn’t offered on a Draft to a connected store. Send it first; once it’s sent, you can email it. ## Follow it on the detail page The Connected store transfer panel on the transfer order shows: - Where it goes: To with a Partner store badge. Hover over the badge, or tab to it, to see the store, the location and, once it has accepted, the other store’s transfer order number. - This store: Booking out, Awaiting partner acceptance, Accepted by partner, Declined by partner, Withdrawn, or Abandoned (after a force cancel). - Offer: whether the offer reached the other store, for example Sent to partner or Not sent yet. - Partner response: the other store’s view, read each time you open the page, for example No answer yet. If it can’t be read, the panel says Partner not reachable. - What happens next, while the stock is being booked out or the offer waits for an answer. If the other store accepted fewer units than you sent, the panel says how many units are short. - A table of the lines, headed Book-out at : Planned, Qty out, and Book-out (Booked out, Not booked out, or Outcome unknown). Once the other store has answered, the table also shows Received, Partner accepted and Partner booked in. - For the partner store’s stock request, when you’re sending this transfer in answer to a [stock request] (/features/supply-orders/transfer-orders/inter-store/stock-requests/). When something is stuck, the panel also shows Retry book-out, Retry delivery or Force cancel. See [Troubleshooting] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/). ## Withdraw an offer While the offer is open (Awaiting partner acceptance), click Withdraw offer on the panel, or Cancel on the transfer order. Logistified first withdraws the offer from the other store. Only when the other store confirms is the transfer order cancelled and the stock returned to the From Location. - The other store already accepted: the cancel is refused. “The connected store has already accepted this transfer, so it can no longer be withdrawn or cancelled. The stock is theirs now.” - The other store can’t be reached: the cancel is refused and nothing changes. Try again later. If the other store is gone for good, use [Force cancel] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/#force-cancel). - Still Booking out: the offer hasn’t left yet, so Cancel works like any cancel and returns the stock. ## When the other store answers Accepted. Your transfer order is received with the quantities the other store accepted, then moves to Completed on its own. Nothing changes in your Shopify stock at this point: it was booked out when you sent. If the other store accepted fewer units than you sent, the shortfall stays visible on both transfer orders. Those units aren’t booked back into your stock automatically. Declined. The panel shows “Declined by the partner store: — cancel to return the stock to .” Your transfer order stays Sent. Click Cancel to return the stock to the From Location. Note A declined transfer is never cancelled for you. Until you cancel it, the units stay booked out of your origin location. ## What’s locked once it’s sent From Sent on, you can’t change the lines, the planned quantities or the two ends, receive by hand, adjust on-hand, Put On Hold, split or delete the transfer order. Once the offer has left, Revert to Draft is locked too. Cancel stays available, and withdraws the offer first while it’s open. Copying the transfer order creates a new Draft that isn’t part of this exchange. ## Lists, documents and exports - Transfer orders list: the To Location cell shows a Partner store badge. Hover over it, or tab to it, to see the store and its location. The Destination filter has a pinned Connected store entry for these transfer orders. - PDF: the To Location block shows the connected store’s location and Connected store: . - CSV / XLSX exports: the To Location cells read · . ## See also - [Receiving a transfer] (/features/supply-orders/transfer-orders/inter-store/receiving/): what the other store does with your offer. - [Troubleshooting] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/): Retry book-out, Retry delivery and Force cancel. - [Creating a TO] (/features/supply-orders/transfer-orders/creating/): the other ways to create a transfer order. - [Lifecycle] (/features/supply-orders/transfer-orders/lifecycle/): the statuses a transfer order moves through. Last updated: 7 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/receiving/ # Receiving a transfer Accept a transfer from a connected store into one of your locations, or decline it with a reason. [Elevate plan] (/reference/subscription-plans/) When a connected store sends you a transfer in Logistified, it arrives as an offer. Nothing exists in your store yet: no transfer order, no change in Shopify, no incoming. You either accept it, which receives the stock straight into one of your locations, or decline it. ## On this page - Where offers arrive - Accept a transfer - Decline a transfer - Your transfer order - See also ## Where offers arrive Open Procurement → Inter-store → Incoming. The transfer orders list also shows a banner while offers wait, for example 2 incoming transfers waiting · Review. Each incoming row shows: - the store that sent it, under Partner store, as a badge with the store’s short name. Hover over the badge, or tab to it, to see the full store name, the location the stock comes from and the sender’s transfer order number; - the sender’s transfer order number, as Partner: ; - the number of lines and units; - when it arrived (Arrived), and its state. An offer you haven’t answered after 7 days shows as No answer under Needs attention, in both stores. ## Accept a transfer Click Accept on the row. The dialog Accept transfer from opens, with the sending store as a badge in its title. 1. Receive into: pick the location the stock goes to. The list shows your own active locations; the location the sender picked is preselected when it’s in the list. Changing it checks the lines again. 2. Review the lines. Each line shows the item and SKU, Shipped, Match (whether it matched one of your products), Stock here (your stock at the location you picked), and Accept. 3. In Accept, enter how many units you take, from 0 up to the shipped quantity. It starts at the shipped quantity. 4. Click Accept and receive. Match uses the same words as the sender’s check: Status What it means Matched You have exactly one active product with this SKU, stocked at the location. Not found You have no product with this SKU. Duplicate SKU You have more than one product with this SKU. No SKU The sender’s line has no SKU. Not stocked The product exists but isn’t stocked at this location in Shopify. If the check can’t be read, each line shows Not checked; click Try again. Accept and receive stays disabled until: - a location is chosen, and it can receive the transfer (if it can’t, the dialog says why); - every line is Matched, including lines you accept 0 of, because each one becomes a line of your transfer order; - every quantity is a whole number from 0 to the shipped quantity, and at least one is above 0. “An all-zero accept is a decline.” If a line doesn’t match, fix the product in your store (for example, add the SKU, or stock the product at the location in Shopify) and the dialog checks again. Otherwise, decline the transfer with a reason so the sender can send a corrected one. ### What accepting does Accepting is the receipt. In one step, Logistified: 1. creates a transfer order in your store, from the sender’s location to the location you chose; 2. adds the accepted units straight to available stock at that location in Shopify; 3. completes the transfer order. The dialog closes with “Accepted — is received into ”. Your answer goes to the sending store, and its transfer order completes when the answer arrives. A line you accept short stays short, on your transfer order and on the sender’s. Nothing is sent back. If the stock can’t be added in Shopify, the dialog stays open with a warning that starts “Your answer is on its way to the partner store, and was created”, explains what’s left, and offers Open transfer order. Your acceptance stands; finish the book-in on the transfer order. See [Retry a book-out or book-in] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/#retry-a-book-out-or-book-in). ## Decline a transfer Click Decline on the row. In the Decline transfer from dialog, enter a Reason (required, up to 500 characters) and click Decline. Decline stays disabled until you’ve entered a reason. You’ll see “Transfer declined — your reason is on its way to ”. Nothing is created in your store, and nothing changes in Shopify. The sender sees your reason and cancels its transfer order to get its stock back. Declining doesn’t need the Elevate plan. ## Your transfer order The transfer order the accept created has a Connected store transfer panel: - From with a Partner store badge, and their transfer order . Hover over the badge, or tab to it, to see the sending store; - This store (the state in your store), Your response (whether your answer reached the sender, for example Sent to partner), and Partner store (the sender’s view, read each time you open the page, or Partner not reachable); - when you accepted fewer units than were shipped, how many units are short; - a table of the lines, headed Book-in at : Shipped, Accepted (with (N short) when you accepted less), Received, and Book-in (Booked in, Not booked in, or Outcome unknown); - For your stock request, when the transfer answers a [stock request] (/features/supply-orders/transfer-orders/inter-store/stock-requests/) you sent. Because the exchange is already settled, most actions are hidden: you can’t add lines, cancel, revert, put it on hold, split, copy or delete it, or fix its on-hand or incoming. Receive Items stays only while a line is received below its accepted quantity, and it receives up to the accepted quantity, never more. Complete shows once every line is booked in. Note You can also receive the rest of an accepted transfer on a [Shopify POS] (/features/pos/overview/) device, up to the accepted quantity. POS doesn’t complete it: use Complete or Retry book-in on the transfer order once every line is booked in. ## See also - [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/): the sender’s side. - [Troubleshooting] (/features/supply-orders/transfer-orders/inter-store/troubleshooting/): Retry book-in and Needs attention. - [Stock requests] (/features/supply-orders/transfer-orders/inter-store/stock-requests/): ask a connected store for stock instead of waiting for it. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/stock-requests/ # Stock requests Ask a connected store for stock, and turn a request from another store into a transfer you send. [Elevate plan] (/reference/subscription-plans/) In Logistified, a stock request asks a connected store to send you stock. It’s a message, not an order: nothing is created in either store, and nothing moves in Shopify, until the other store accepts it into a Draft transfer order and sends that Draft. ## On this page - How a request flows - Ask for stock - Withdraw a request - Answer a request - Decline a request - See also ## How a request flows 1. You send a request: which products, how many, where to deliver them, and by when. 2. The other store accepts it, which creates a Draft transfer order in that store, or declines it with a reason. 3. The other store reviews the Draft and sends it, like any [transfer to a connected store] (/features/supply-orders/transfer-orders/inter-store/sending/). 4. The transfer arrives under Incoming in your store, and you [accept it] (/features/supply-orders/transfer-orders/inter-store/receiving/). On both stores, the transfer’s row on the Inter-store page reads For stock request, and its transfer order panel links it back to the request. ## Ask for stock Open Supply Orders → Transfer Orders → Create Transfer Order → Request stock from a connected store. The menu item shows on Elevate, once a connection has [inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/setup/) switched on. In the Request stock dialog: - Connected store: the store to ask. The list shows the connected stores that take inter-store transfers, by their short name with the full Shopify domain underneath. - Deliver to: one of your own active locations. - Add products: pick the products you need. Each gets a row with a quantity (1 to start) and Remove. The other store matches them by SKU, so a product without a SKU is flagged and can’t be requested. At most 250 products per request. - Needed by (optional): becomes the requested delivery date on the other store’s Draft. - Note (optional, up to 1,000 characters): shared with the other store as the notes on its Draft. Click Send request. It’s enabled once you’ve chosen a store, a location and at least one product, and every quantity is a whole number of 1 or more. The dialog closes with “Stock request sent to ”. The request is refused if the other store isn’t on Elevate or can’t be reached right now. Your request now shows under Procurement → Inter-store → Outgoing, with the store you asked as a Partner store badge, Needed by , its lines and units, and the state Requested. Click View request on the row to read it in full: its status, when you sent it, where it’s delivered to, the date, your note and its lines. ## Withdraw a request While the request is Requested, click Withdraw on its Outgoing row, then Withdraw in the Withdraw stock request to dialog. The other store decides: - It hasn’t answered yet: the request ends in both stores. “Stock request withdrawn — no longer sees it”. - It already accepted: the request can’t be withdrawn. Its transfer shows under Incoming once the other store sends it. - It already declined: nothing to withdraw. - It can’t be reached: the request stays open. Try again later. Withdrawing doesn’t need the Elevate plan. ## Answer a request Requests from other stores show under Procurement → Inter-store → Incoming, as rows of the kind Stock request with Accept and Decline. View request on the row shows the request read only, including the requester’s note and the location the stock goes to. The transfer orders list shows a banner while they wait, for example 1 incoming stock request waiting · Review. A request you haven’t answered after 7 days shows as No answer under Needs attention, with a Review request link. Click Accept. The dialog Accept stock request from opens with the request in one sentence and the requester’s note. Hover over the store’s badge in the title, or tab to it, to see where the requester wants the stock delivered. 1. Send from: pick the location the stock leaves from. The list shows your own active locations; it’s preselected when you have only one. Changing it checks the lines again. 2. Review the lines: the item and SKU, Requested, Match, Stock here (your stock at the location you picked), and Send. 3. In Send, enter how many units you’ll send. It starts at the requested quantity. You can send more than the location has in stock: the dialog shows a hint, not an error, because you can still change the Draft. 4. Click Create transfer. A line you can’t send reads Not available here with its reason, and is left off the Draft: Status What it means Matched You have exactly one active product with this SKU, stocked at the location. You can send it. Not found You have no active product with this SKU. Duplicate SKU You have more than one active product with this SKU. No SKU The requested line has no SKU. Not stocked The product isn’t stocked at this location in Shopify. Not tracked The product can’t be booked out of Shopify, for example a placeholder or custom line. Create transfer stays disabled until a location is chosen and can send, at least one line matches, and at least one quantity is above 0. “Sending nothing is a decline.” If nothing matches at a location, the dialog says “None of the requested products can be sent from ”; pick another location, or decline. ### After you accept The dialog stays open on the result: - Draft created, and your answer is on its way to the other store. - The lines left out, with their reasons. - Open transfer order, to go to the Draft. Nothing has moved in Shopify yet. The Draft ships from the location you chose to the requester’s location, with the requested date as its requested delivery date and the note as its notes. Review it like any Draft: you can still change lines, quantities, the date and the note. If you change its destination to another store, it no longer answers this request. Then click Send. Sending checks the lines, books the stock out and offers the transfer to the requester, as described in [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/#send-it). Caution Accepting a request doesn’t send anything. The requester only sees the transfer, under Incoming, after you Send the Draft. ## Decline a request Click Decline on the request’s row. In the Decline stock request from dialog, enter a Reason (required, up to 500 characters) and click Decline. Nothing is created in either store. The requester sees your reason in its History tab, under the state Declined. Declining doesn’t need the Elevate plan. ## See also - [Inter-store transfers] (/features/supply-orders/transfer-orders/inter-store/overview/): how transfers between connected stores work. - [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/): what happens when the Draft is sent. - [Receiving a transfer] (/features/supply-orders/transfer-orders/inter-store/receiving/): accepting the transfer that answers your request. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inter-store/troubleshooting/ # Troubleshooting inter-store transfers Find stuck transfers and stock requests, retry a book-out or book-in, force cancel, and close a thread to a store that's gone. In Logistified, nothing between two connected stores gives up on its own or fails silently. A transfer or request that’s stuck waits where you can see it until someone acts. This page covers where to look and what each fix does. Everything on this page works without the Elevate plan, so a store that has left Elevate can still finish or end what it has. ## On this page - Where to look - Needs attention - Retry a book-out or book-in - When Logistified can’t tell what Shopify did - Retry delivery - Force cancel - Close thread - The Messages tab - See also ## Where to look - Procurement → Inter-store → Needs attention: every exchange that’s stuck, with a link to where you fix it. - Transfer orders list: a banner such as 1 inter-store transfer needs attention · Review. - The transfer order’s Connected store transfer panel: the state in both stores, each line’s book-out or book-in, and the retry buttons. - Settings → Multi-Store → Messages: every message sent between the stores, and any that are blocked. ## Needs attention Each row names the problem, the exchange, the other store (Partner store, as a badge with its short name), and how long it’s been stuck (Since). The tab shows the first 100 rows and counts the rest. Shown as What it means What to do Booking out stuck You sent a transfer, but its stock wasn’t booked out after an hour, so the offer hasn’t left. Open the transfer order and use Retry book-out. Or Cancel it: the offer hasn’t left, so the stock comes back. Booking in stuck You accepted a transfer, but its stock wasn’t booked into Shopify an hour later. Open the transfer order. Its panel says what’s left: send it, receive the rest, or Retry book-in. Delivery blocked The other store refused a message, or your store stopped sending it. Fix the cause, then Retry or Resolve it under Messages. If the other store is gone for good, use [Close thread] (#close-thread). Message refused Your store refused a message from the other store. Review it under Messages. Stores disagree The two stores don’t agree on where the exchange stands. Don’t adjust stock to make the numbers match. Email [support@p-h.solutions] (mailto:support@p-h.solutions) with the transfer order numbers from both stores. Not delivered A message hasn’t reached the other store for more than 7 days. Check that the stores are still connected, then Retry it under Messages. No answer An offer or stock request has waited more than 7 days. If it’s waiting for you, accept or decline it. If you sent it, wait, or withdraw it. Follow-ups pending Product tags or line-item fields after a status change haven’t run. Open the transfer order; that runs them again. Each row has one link: Open transfer order when your store has one, Review offer or Review request for an open incoming offer or request, or Open messages for the Messages tab. A blocked row also offers Close thread. ## Retry a book-out or book-in When stock wasn’t booked out of, or into, Shopify for every line, the transfer order’s panel shows a retry button: - Retry book-out on the sending store’s transfer order, while it’s still Booking out. - Retry book-in on the receiving store’s transfer order, when a line is received but not booked in. Fix the cause in Shopify first, for example a location that no longer stocks the product. A retry first checks each line’s result in Shopify. A line that’s already done is only counted, never booked twice. The other lines are booked now. The table then shows each line’s result, or Failed: . After a successful book-out, the offer goes to the other store. After a successful book-in, the transfer order completes. ### When the receiving transfer order is still a Draft If accepting created your transfer order but couldn’t send it, it stays a Draft. The panel says so. Click Send (nothing moves in Shopify), then receive the accepted quantities with Receive Items, then Complete it, or use Retry book-in. If a line was received below its accepted quantity, receive the rest with Receive Items first; Retry book-in only books in what’s been received. ## When Logistified can’t tell what Shopify did Sometimes a book-out or book-in reached Shopify, but its answer never came back. Logistified can’t tell whether Shopify applied it, so the line reads Outcome unknown, and the retry doesn’t change anything on its own. The dialog turns into Check Shopify before booking in (or Check Shopify before booking out). 1. Read the lines the dialog lists, for example Blue mug: +4 at Main warehouse. That’s the change to look for. 2. In Shopify, open the inventory history of each item at that location, and look for this transfer’s stock being added (or taken out). 3. Pick the answer that matches Shopify: - Mark as booked in: “Shopify already shows these units at ; record them here without changing Shopify.” - Book in anyway: “Shopify does not show them; add them now.” On the sending side, the same choice reads Mark as booked out or Book out anyway. Caution Pick carefully: each wrong answer costs stock. Booking in units Shopify already has counts them twice. Marking units Shopify doesn’t have leaves them missing from available stock. The transfer order’s log records who decided. ## Retry delivery Retry delivery shows on the panel when a message of the transfer wasn’t delivered or was refused: on the sending store, the offer; on the receiving store, its answer. It sends the message again. If the cause is still there, the message is blocked again; see the [Messages tab] (#the-messages-tab). ## Force cancel Use Force cancel on the sending store’s transfer order when the offer is open (Awaiting partner acceptance on the panel) and the other store is no longer connected, so the offer can’t be withdrawn. While the other store is still connected, withdraw with Withdraw offer or Cancel instead; Force cancel refuses. It works in two steps, so the stock comes back whenever it can: 1. Click Force cancel. If the offer certainly never reached the other store, the transfer order is cancelled and the stock returns: “Transfer cancelled — the stock is back at ”. 2. If the other store has the offer, or may have it, the dialog warns No stock is returned. Tick “I understand the stock will not be returned to .” and click Force cancel again. The transfer order is cancelled and the units stay booked out: “Transfer cancelled — no stock was returned”. The panel’s state then reads Abandoned. ## Close thread Close thread ends a blocked exchange with a store that no longer accepts your store’s messages: it disconnected, or switched inter-store transfers off. Retry and Resolve only block such an exchange again. You’ll find Close thread on a blocked row under Needs attention, and under Settings → Multi-Store → Messages → Blocked threads. It asks you to confirm: “The other store no longer accepts this store’s messages. The undelivered messages are discarded and never sent, and the thread leaves Needs attention.” - The messages that weren’t delivered are discarded. Nothing reaches the other store. - The exchange keeps its state. For example, a transfer you accepted stays accepted. - The transfer order’s panel shows Closed by on : . - If the other store still answers, the close is refused: use Retry or Resolve instead. Close thread isn’t offered for your own transfer that’s still Booking out or Offered: end that one from its transfer order with Cancel or [Force cancel] (#force-cancel), which also deals with the booked-out stock. ## The Messages tab Settings → Multi-Store → Messages shows while Multi-Store is on: - Needs attention: messages and exchanges that are stuck, with Dismiss for a refused message. - Blocked threads: exchanges whose messages stopped, with the store, the kind of exchange, the reason and since when. Retry sends the stopped message now; Resolve releases the block so the next delivery attempt sends it. Fix the cause first, or the message is stopped again. Close thread is the way out when the other store is gone. - Message log: every message, with time, type, direction, the other store, state and any refusal code. ## See also - [Sending a transfer] (/features/supply-orders/transfer-orders/inter-store/sending/): withdraw and the decline banner. - [Receiving a transfer] (/features/supply-orders/transfer-orders/inter-store/receiving/): the receiving transfer order and its panel. - [Setting up] (/features/supply-orders/transfer-orders/inter-store/setup/): the Inter-store transfers switch on each connection. - [Settings → Multi-store] (/features/settings/multi-store/): connecting and reconnecting stores. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/inventory-effects/ # Inventory effects What moves where on each TO transition, and how it interacts with Shopify and the forecast. Most status changes on a Logistified transfer order move stock at its origin, its destination, or both. This page lists what moves where, what reaches Shopify, and how transfers interact with the forecast. ## On this page - What moves where, per transition - Why “incoming” matters at the destination - Multi-location forecasting - Checking historical transfer sync - See also ## What moves where, per transition Transition Origin Destination Shopify push Draft → Sent available decreases by planned quantity incoming increases by planned quantity yes Sent → Partially Received unchanged incoming → available (per received line) yes Partially Received → Received unchanged remaining incoming → available yes Sent or Partially Received → Cancelled sent quantity added back to available remaining incoming zeroed; already-received quantity removed from available yes Received or Partially Received → Sent or Draft (revert) sent quantity added back to available already-received quantity removed from available, received counts reset to 0 yes Draft → Cancelled no effect no effect no → On Hold / Resumed no effect no effect no Received / Partially Received → Completed no inventory change: unlocks reconciliation tools no inventory change no Notes: - At Send time, the planned quantity is what moves; there’s no separate “shipped quantity” you enter at dispatch. - Cancelling or reverting only undoes what the system itself pushed to Shopify. Leaving Received or Partially Received pulls the already-received quantities back out of the destination’s available stock and resets each line’s received count to 0, so the lines can be received again. - Logistified writes Shopify’s available quantity. Shopify’s on-hand figure follows automatically, because on-hand is derived from available plus committed and the other tracked states. - Editing the shipping date or carrier doesn’t push to Shopify; those are app-only details. - This table is for TOs with a destination location. A TO [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) (Elevate) still decrements origin available at Send, but nothing happens on the destination side in Shopify at any transition; there’s no Shopify incoming push and no destination available change, because the destination isn’t a Shopify location at all. Note 3PL-managed available stock. If your fulfillment partner owns Shopify available inventory at the origin and/or destination, turn off the matching Update source / destination location available in Shopify switch in [TO settings → Preferences] (/features/supply-orders/transfer-orders/settings/#inventory-sync-preferences-tab). The available changes in the table above on a turned-off side (origin decrement on Send with the source switch off; destination move-in on Receive with the destination switch off) are left to your 3PL; Logistified still pushes the incoming changes and keeps its own tracking in sync on both sides. Typical setup: source switch on, destination switch off; you send from your own warehouse, the 3PL’s system books the arrival. Turning off incoming updates. The same card has a third switch, Sync incoming to Shopify (on by default). Turned off, transfer orders skip every incoming change in the table above: sending no longer raises incoming at the destination, and receiving adds the received units directly to destination available (when that side’s switch is on) instead of moving them out of incoming. With both destination-facing switches off, transfer orders leave Shopify untouched at the destination entirely. Logistified’s own in-transit tracking and forecasts keep working either way. ## Why “incoming” matters at the destination Even before the goods arrive, Logistified marks them as [incoming] (/reference/glossary/#incoming-quantity) at the destination. This lets the forecast at the destination see the upcoming stock, so reorder suggestions there don’t ask for more than you need. ## Multi-location forecasting When you have a TO in Sent state: - The destination’s “Days of stock with all incoming” reflects the in-transit units. - The origin’s stock dropped at Send time, so it shows accurate available stock. Note TOs and POs both contribute to a location’s “incoming” total. The forecast adds them up so reorder suggestions take both into account. ## Checking historical transfer sync An assistant with read access can inspect Logistified’s recorded transfer sync state, including historical lines whose product variant is now missing or deleted. This inspection makes no inventory changes and does not recreate products. A Completed transfer can still have unresolved sync work. An in-flight amount means Logistified recorded a claim awaiting confirmation; it does not confirm what happened in Shopify or Assemblified. A hold marker applies to the line; it does not identify which movement or acknowledgement is held, and other outstanding changes can coexist with it. Even zero outstanding totals do not prove that both systems or physical stock agree. Before deciding on a correction, compare the transfer’s history with Assemblified’s delivery and application records, Shopify’s inventory history at both locations, and any physical movement or count evidence. Keep the historical product identifiers when asking support to investigate. The inspection does not authorize a retry, acknowledgement release, reversal, or reopening of a Completed transfer; historical repair needs a separate decision after that evidence is reviewed. ## See also - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): fixing drift between Logistified and Shopify. - [Forecast → Locations & multi-location math] (/features/forecast/locations/): how the destination’s forecast sees TOs. - [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): what changes on the destination side when a TO ships to a supplier instead of a location. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/shipping-receiving/ # Shipping & receiving One shipment per TO, partial receipts, splitting a TO, and discrepancy handling. In Logistified, a transfer order ships as one shipment and can be received in full or in parts. This page covers shipping, receiving, splitting a transfer order and handling discrepancies. ## On this page - One shipment per TO - Carrier dropdown - Receiving: full or partial - Splitting a TO - Discrepancies on receipt - See also ## One shipment per TO A TO has exactly one shipment. The shipment record holds the carrier, tracking number, and shipping date. If you need to dispatch the same items in two physical shipments (different carriers, different days), use Split Transfer Order to break the TO into two; see below. ## Carrier dropdown Pulled from Settings → Carriers. If your carrier isn’t listed, add it there first. [anchor: receiving--full-or-partial] ## Receiving: full or partial Open the TO and click Receive Items. The receive dialog shows every line with its planned quantity and a “Receive” input. Enter the received quantity per line and save. - Full receipt: all remaining lines fully received → status becomes Received. - Partial receipt: some lines partially or fully received, others not → status becomes Partially Received. Receive the rest later from the same dialog. Unsaved entries are never lost. Whatever you’ve typed is saved automatically while the dialog is open, so closing it by accident (or reloading the page) doesn’t discard your progress: reopen the dialog and it restores what you had, with a notice offering to discard it if you’d rather start fresh. Saving the receipt clears the saved progress. If someone received while the dialog was open (on the till or in another tab), nothing is saved, whether you were adding to a line or correcting it down. The dialog says “Someone received items on this transfer order while this dialog was open, so nothing was saved. The quantities now include their receipt; check them and receive again.”; the page refreshes behind it and your counts stay on top of the new quantities. If Shopify couldn’t be updated, your received quantities are still saved. You see “Received quantities saved, but Shopify inventory was not updated.” with the reason (or “1 of 2 items updated…” when only some went through), and a Retry Shopify update button that sends just the Shopify update again; nothing is received twice. The message stays at the top of the transfer order until the update goes through or you dismiss it. If an earlier update is still being applied, it says “Shopify inventory is still being updated for this transfer order. Check again in a minute.” and offers Check again. The retry isn’t offered when Shopify incoming sync is turned off for transfer orders; the message still stays at the top of the transfer order and says what to do instead (update the available quantity of those items at the destination in Shopify) until you dismiss it. A transfer heading to one of your retail locations can also be received on the till: see [Shopify POS] (/features/pos/overview/), where staff without admin access count it in with a stepper, a POS barcode scanner or the camera. When you’re done with receipts and want to lock the TO for reconciliation, use Complete from the actions menu: see [Lifecycle] (/features/supply-orders/transfer-orders/lifecycle/) for what that unlocks. Note TOs [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) use the same Receive Items dialog, but the received quantity is recorded as your stock at that supplier instead of moving into a Shopify location. You also can’t lower an already-received quantity from this dialog on one of these TOs; use Revert to Sent to unreceive the line, then receive it again with the right quantity. ## Splitting a TO Use Split Transfer Order in the TO detail’s actions dropdown when you need to break one TO into two. Common reasons: - A forgotten SKU on a Sent TO (you can’t add new lines past Draft, but you can split out a new draft and add to that). - Splitting a partial receipt so the un-received remainder lives on its own TO and the already-received items stay closed on the original. - Dispatching the same plan in two physical shipments with different carriers or dates. Available on any TO except Completed and Cancelled. In the split dialog, each line gets a mode: Mode What happens Keep The line stays on the source TO unchanged. Move The whole line moves to the new TO. Split A portion of the planned quantity moves to the new TO; the rest stays on the source. Smart defaults if the source TO is Partially Received: - Fully-unreceived lines default to Move. - Partially-received lines default to Split; only the unreceived remainder moves. - Fully-received lines default to Keep (their work is done). You can choose to create the new TO as a fresh Draft or to inherit the source TO’s status. ## Discrepancies on receipt - Under-receive. The remainder stays as incoming at the destination. Receive later, or split off the remainder, or cancel the remaining quantity. - Over-receive. Blocked with a validation error: the dialog won’t let you save a receive larger than the planned quantity for that line. If the extra units really arrived, investigate with the origin location, then use a stock take or (once the TO is Completed) the Fix On Hand Quantity tool to reconcile. Caution Past Draft, you can’t add new lines to a TO. If your team forgot a SKU, use Split Transfer Order to spin out a new TO for the missing items, or cancel and recreate. ## See also - [Lifecycle] (/features/supply-orders/transfer-orders/lifecycle/): what receipts and completion do to status. - [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/): what receipts do to inventory. - [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): receiving into supplier-held stock instead of a location. - [Shopify POS] (/features/pos/overview/): receiving a transfer at the counter. - [Floormode warehouse execution] (/features/supply-orders/transfer-orders/floormode-execution/): when Floormode handles picking, dispatch, and receiving instead of this flow. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/floormode-execution/ # Floormode warehouse execution When Floormode runs a transfer order's source warehouse, Send hands its picking and dispatch to Floormode; receive each shipment at its destination. If your shop uses Floormode, our companion warehouse app, a Logistified transfer order whose source warehouse Floormode runs is picked and dispatched there instead of following the ordinary [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/) flow. You don’t choose this per order: Send hands it to Floormode by itself. Each dispatch updates this transfer order automatically; physical receipt at the destination is recorded separately. The first dispatch also appears as Departure reported by Floormode on the order’s Activity tab. Note This applies only to warehouses you handed to Floormode under Settings → Integrations (see [Integrations] (/features/settings/integrations/#floormode)). A transfer order whose source warehouse stays with Logistified is sent and received as described in [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/). ## On this page - Sending a transfer order from a Floormode warehouse - When Floormode can’t take a transfer - Plan status and what each one means - Retrying and cancelling - Receiving shipment positions - What still happens here - See also ## Sending a transfer order from a Floormode warehouse Create and plan the transfer in Logistified as usual. On its Order & Items tab, a Warehouse picking in Floormode panel says what Send will do: “Floormode runs the source warehouse. When you mark this transfer as sent, it goes to Floormode for picking; it is marked as sent when Floormode ships it.” When you mark the Draft transfer as Sent, Logistified hands it to Floormode instead: - the confirmation reads “Sent to Floormode for picking. Floormode runs the source warehouse; this transfer is marked as sent when Floormode ships it.”; - the transfer stays a Draft for now, and no stock moves in Logistified or Shopify at that moment; - once Floormode ships it, the transfer becomes Sent and the shipped quantities appear here. Open transfers in Floormode opens Floormode’s transfers list, where you can find the order. Send via Email isn’t available for such a transfer before Floormode ships it: “Floormode runs this transfer’s source warehouse, so it is picked there. Use Send to hand it to Floormode; email the transfer once Floormode ships it.” Only the first Send of a Draft hands a transfer to Floormode. Resuming a transfer from On Hold, or moving one back to Sent, keeps the path it already took. ## When Floormode can’t take a transfer If Floormode runs the source warehouse but can’t take this particular transfer, Send is refused with the reason, and nothing is sent or moved. Where Logistified can tell in advance, the panel already shows the reason. The common ones: You see What to do “Floormode runs this warehouse, but its connection doesn’t confirm transfer picking yet. Open Settings → Integrations and confirm the connection again.” Open Settings → Integrations, check readiness on the Floormode card and activate the agreement again, then send the transfer. “Floormode cannot execute transfers of Assemblified sub-assemblies yet.” Remove the Assemblified sub-assembly lines (SKU starting with ASM-), or move them from a warehouse Logistified runs. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#transfers). “Floormode keeps its own materials and moves them between its warehouses itself. Remove the Floormode material from this transfer order.” Remove the Floormode material line; move it in Floormode instead. “This transfer has prior inventory progress and cannot be enrolled as a fresh physical transfer.” Something was already sent or received on this transfer here. Create a new transfer for what’s left. A destination Floormode can’t send to Floormode sends a transfer only to a warehouse it runs, or to one the receiving agreement names as Logistified’s (and only once Floormode confirms receipts there). The message says which applies; change the destination, or confirm the agreement again under Settings → Integrations. ## Plan status and what each one means The panel’s message tells you where the plan stands: Status What it means Waiting for confirmation Floormode hasn’t acknowledged the plan yet. Sending the request doesn’t mark goods as dispatched; source inventory remains protected. Accepted Floormode confirmed the plan. Its warehouse team can now pick and dispatch; each shipment updates this transfer order automatically. Not accepted Floormode rejected the plan and reports the reason. Fix the issue, then send it again. ## Retrying and cancelling - Retry delivery: if Floormode hasn’t confirmed the plan yet, send the same plan again. - Retry source publication: once Floormode has accepted the plan, Logistified may still be catching up on confirming shipments or updating the origin side. The panel shows how many of those updates are pending, refused, or expired, and lets you retry the ones still eligible. Refused or expired stock updates are held for verification; this retry does not apply them again. Saved shipment confirmations can still be resent when eligible. - Cancel unshipped plan: cancels whatever Floormode hasn’t shipped yet. Anything already dispatched stays in transit; cancelling doesn’t return those goods to source stock or erase their shipment history. ## Receiving shipment positions Once Floormode has dispatched at least one shipment, Review shipment receipts opens a dialog listing shipped positions: the item, which shipment and position it belongs to, lot and expiry when tracked, how much was dispatched, and how much is still remaining. To record a physical receipt: 1. Check off the positions you’re receiving. You can only select positions from one shipment at a time, and only ones Logistified is responsible for receiving; a position that Floormode itself receives shows a note instead of a checkbox. 2. Enter the quantity actually received for each checked position, up to what’s remaining. 3. Confirm the receipt. Your entry is saved before it’s sent, so if confirmation is interrupted (a dropped connection, an accidental reload), reopening the dialog in the same browser, with its saved data intact, picks up the same receipt so you can retry it without recording it twice. Retry it unchanged to resolve the outcome, or use Review quantities to discard it and start over once it’s safe to. The dialog shows up to 100 positions across the transfer’s shipments and warns when more exist. Positions with quantity still to receive appear first. After a position is fully received and the list refreshes, another outstanding position can become visible. Receive only positions you can identify in the dialog; hidden positions are never selected automatically. Note A confirmed receipt updates this transfer order’s received quantities right away, but your Shopify inventory and incoming numbers can take a little longer to catch up; the confirmation itself doesn’t mean Floormode has finished settling the shipment on its side. ## What still happens here Create and plan the transfer in Logistified; Send hands it over. Once handed over, source picking and dispatch happen in Floormode, and ordinary shipping, splitting, and manual status changes cannot override that execution. Track shipment and receipt progress here, and use the Floormode panel for retries or cancellation. Record destination receipts in Logistified only when it is responsible for receiving; destinations handled by Floormode are received there. ## See also - [Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/): the ordinary receive flow used when Floormode isn’t handling a transfer order. - [Integrations] (/features/settings/integrations/#floormode-retained-stock-reports): retained stock reports Floormode last sent, kept visible even after its connection is turned off. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/assemblified-materials/ # Materials from Assemblified See which raw materials and sub-assemblies Assemblified will use when a transfer takes more of a product than is pre-assembled at the origin location. If your store uses Assemblified, some of the products you transfer in Logistified have a recipe (a Bill of Materials). When a transfer takes more of such a product than Assemblified has pre-assembled at the origin location, Assemblified builds the missing units when you send the transfer, and uses up their raw materials and sub-assemblies at the origin location. The transfer order shows this before you send: per line, how many units come from the pre-assembled stock and how many will be built, and for the whole transfer, the list of materials that will be used. You can print the same list on the transfer order PDF. ## On this page - What you need - The Manufacturing (Assemblified) columns - The Materials (Estimated) card - On the PDF - It’s an estimate, for quantity not yet sent - When Assemblified can’t be reached - See also ## What you need The Assemblified app connected to your shop. Install it from the Shopify App Store; Logistified detects the connection on its own, and there’s nothing to configure. It works on every plan. Without Assemblified, you see nothing new on your transfer orders unless you add the columns below yourself. They then say that Assemblified isn’t connected, with a link to open it. ## The Manufacturing (Assemblified) columns Open Columns above a transfer order’s line items and add any of the three columns in the Manufacturing (Assemblified) group. Like every other column, you can save them in a [view] (/features/supply-orders/line-item-views/). Column What it shows Pre-assembled at source Units of the product already assembled at the origin location, as this line finds them after the transfer’s earlier lines. Sending takes from this stock first. Built from components Units Assemblified will build from components when you send: the part of the line the pre-assembled stock doesn’t cover. Instead of a number it can read Disabled here, No recipe, Conflict in recipe or Can’t build here; hover for what to check in Assemblified. Components How many components that build uses. Hover for each component with its quantity and, when it isn’t the origin location, where it’s taken from, plus the sub-assemblies taken from their pre-assembled stock. A line for a product Assemblified doesn’t assemble shows a dash; hover it for the reason. Once a line has been sent, Built from components reads Sent, and while it’s on its way to Assemblified it reads Being sent to Assemblified. The page checks again by itself until Assemblified confirms. ## The Materials (Estimated) card Under the line items, the Materials (Estimated) card adds up every line into one pick list. Click its header to open it. Each row shows the item, its SKU, the quantity, the unit, the location when it isn’t the origin location, and the finished products it’s used for. Sub-assemblies taken from their pre-assembled stock are labelled Sub-assembly (pre-assembled), and Assemblified’s virtual materials are labelled Virtual. The card only appears when there’s something to list. A transfer whose lines are all covered by pre-assembled stock, or that has nothing left to send, shows no card. ## On the PDF The transfer order PDF lists the same materials in a Materials (estimated) section after the totals, so you can print it as a pick list or attach it before you send. The PDF attached to the destination-location email includes it too. To leave it off, switch off Materials from Assemblified in your PDF template at Settings → Transfer Orders → Export. It’s on by default. If Assemblified doesn’t answer within a few seconds, the PDF is still created: it says Materials list unavailable — Assemblified did not answer instead of the list. A shop without Assemblified never gets the section. ## It’s an estimate, for quantity not yet sent Note The numbers are an estimate based on Assemblified’s current stock and recipes. If stock changes before you send, or the lines reach Assemblified in a different order, what Assemblified actually uses can differ. - Only quantity not yet sent is estimated. For a draft, that’s the whole planned quantity. Once a transfer is sent, quantity already sent reads Sent and isn’t listed again; the estimate covers only what’s still to send. Received, completed and cancelled transfers show no materials. - Quantities are what Assemblified will take from stock, in whole units for regular items. Hover a quantity for the exact requirement. Virtual materials show their exact quantity. - A quantity marked ≈ is a component Assemblified itself recomputes and that is used in fractions. Its whole-unit figure can turn out different, so the exact requirement is shown instead. - Up to 500 lines per transfer. A larger transfer says it has too many lines to estimate. ## When Assemblified can’t be reached If Assemblified doesn’t answer, the columns show a dash with Retry. If you’ve already seen materials on this page, the card keeps showing the last estimate, says it couldn’t refresh, and offers Retry too. Nothing else on the page is affected. ## See also - [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/): moving Assemblified’s sub-assemblies on a transfer. - [Line-item column views] (/features/supply-orders/line-item-views/): choosing and saving columns. - [Exports] (/features/supply-orders/transfer-orders/exports/): the transfer order PDF. - [TO settings & preferences] (/features/supply-orders/transfer-orders/settings/): where PDF templates live. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/exports/ # Transfer order exports Bulk CSV / XLSX exports of transfer orders, driven by templates you control. Logistified’s transfer orders export to CSV / XLSX. You can export a single TO from its detail page, or bulk export many TOs at once from the list. The column set comes from an export template you control. This page covers the bulk export flow, the two data levels, and where templates live. ## On this page - Bulk export from the list - Line-item vs transfer-order-level - Single-TO exports - Export templates - See also ## Bulk export from the list On the Transfer Orders list, tick the checkbox on any rows you want (or use the header checkbox to select the whole page), then click Export. The selection persists as you page through the list and apply filters, so you can build up a set across several pages. Clear selection resets it. The dialog asks three things (the footer shows a fourth step, Export, for the run itself): 1. Scope: what to include: - Selected: only the TOs you ticked. - All on this page: every TO visible on the current page. - All filtered: every TO matching your current filters, across all pages. 2. Data level: line-item or transfer-order-level (see below). 3. Format + template: CSV or XLSX, and which export template drives the columns. Leave it on Use default settings to use the shop default. Bulk export produces one combined file for the whole selection. Caution Line-item exports fetch one TO at a time so the server is never hammered, with a progress bar as it runs. A few hundred TOs can take a minute or more; narrow the scope if you can. You can cancel mid-run; no file is downloaded if you do. ## Line-item vs transfer-order-level Data level One row per Use when Line item TO line item Another system needs SKU, planned quantity, unit cost, product / variant, or line-level metafield data. Header fields repeat on every line. Transfer order level transfer order You want a summary (TO number, status, from / to location, item count, total value, and shipping) with one row per TO. No supplier or payment fields, because a transfer order moves stock between two of your own locations. Each data level uses its own template type, so the template picker on the format step only shows templates built for that level. ## Single-TO exports From an individual transfer order you can also generate: - A PDF: the transfer document with header, line items, and shipment metadata. The same PDF can be attached to the destination-location notification email. On a TO [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/), the To Location block adds a line: Deliver to: , holding these goods on our behalf. If your store uses Assemblified, the PDF also lists the [materials Assemblified will use] (/features/supply-orders/transfer-orders/assemblified-materials/#on-the-pdf) for quantity not yet sent; switch Materials from Assemblified off in the PDF template to leave it out. - A CSV / XLSX of that one TO’s line items. ## Export templates Templates are configured at Settings → Transfer Orders → Export. There are three sections: - PDF templates drive the single-TO transfer document (and the file attached to the destination-location notification email). They carry layout options, not a column list. - Line-item templates drive the line-item CSV / XLSX export (and the per-TO export). - Transfer-order-level templates drive the one-row-per-TO bulk export. They are global list templates with no per-supplier assignment; TOs have no supplier. You can save many templates per shop and pick one at export time; sensible defaults ship for both levels. The Available columns list on CSV / XLSX templates is searchable and grouped by source, with collapsible groups and a per-group Select all / Clear toggle. The line-item catalog also includes live variant data read from your Logistified data at export time (inventory at the source location, at the destination location, and summed across all your locations; planning constants for the destination; and ABC / revenue metrics), so a single row can answer “how much is available to send, and how much is already at the destination?” None of these are selected by default, and the transfer-order-level catalog doesn’t include them. Planning constants export blank when not configured, not 0. Both catalogs also offer seven Destination columns (company name, two address lines, city, ZIP, country, phone). On an ordinary TO these carry the destination location’s address; on a TO [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) (Elevate) they carry that supplier’s address instead, so the destination is never blank in an export just because the TO has no location. ## See also - [TO settings & preferences] (/features/supply-orders/transfer-orders/settings/#the-five-tabs): the Export tab where templates are built. - [Settings → Data export templates] (/features/settings/data-export-templates/): column presets across the app. - [Purchase Orders → Exports] (/features/supply-orders/purchase-orders/exports/): the sibling PO export flow. - [Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): the Destination columns and PDF line documented above. - [Materials from Assemblified] (/features/supply-orders/transfer-orders/assemblified-materials/): the PDF’s Materials section. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/transfer-orders/settings/ # TO settings & preferences TO-specific preferences: metafields, writeback rules, product tags, exports, and email templates. The settings for Logistified’s transfer orders hold their own preferences: metafields, writeback rules, product tags, exports and email templates. ## On this page - Where TO settings live - The five tabs - Update Metafields action - Adjacent settings - What’s shared with Purchase Orders - See also ## Where TO settings live Settings → Transfer Orders. ## The five tabs Tab What it configures Metafields Two cards: Line Item Metafields (which variant metafields show up as line columns and appear in exports) and Shopify Writeback Rules (which line-item field changes get written back to the product or variant in Shopify while the TO is active). Product Tags Define tags and per-tag rules for when they’re automatically added or removed based on TO status transitions. Each tag has its own list of auto-set statuses and auto-unset statuses. Tags with no rules configured are manual-only. Preferences Two cards: Inventory Sync, which controls how transfer orders update Shopify inventory (per-location Update source / destination location available in Shopify toggles plus Sync incoming to Shopify; see [Inventory Sync] (#inventory-sync-preferences-tab) below), and Line items, which sets the default sort order for line items when you open a transfer order. Pick a column (Product title, Variant title, Shopify SKU, Supplier SKU, Shopify barcode, Supplier barcode, Quantity, or None (order added)) and a direction (ascending / descending). Export Column presets for CSV / XLSX exports and PDF layout. Two sections: line-item templates (one row per TO line) and transfer-order-level templates (one row per TO), picked at export time from the [bulk export] (/features/supply-orders/transfer-orders/exports/) on the list. PDF templates include a Compact layout option, a Show barcode column toggle (displays the variant barcode in a dedicated column next to the SKU) and a Materials from Assemblified toggle (on by default; lists the [materials Assemblified will use] (/features/supply-orders/transfer-orders/assemblified-materials/) for quantity not yet sent). Email Templates Subject + body for the destination-location notification email sent when you dispatch a TO. ### Update Metafields action Turning on a line-item metafield in the Metafields tab only stamps lines added from then on; lines already on a TO won’t pick it up automatically. Each transfer order’s Actions menu has an always-available Update Metafields entry that fills in a value for every line missing one and refreshes lines that already have one, using current data from Shopify. It never clears an existing value, so it’s safe to run at any time; a line that can’t be matched to a Shopify product is simply left untouched. The same action exists on purchase orders and return orders. ### Inventory Sync (Preferences tab) By default, transfer orders move Shopify available stock: sending a TO decrements available at the origin, and receiving moves stock into available at the destination (see [Inventory effects] (/features/supply-orders/transfer-orders/inventory-effects/)). If a 3PL or WMS owns your Shopify available inventory at one of those locations (your fulfillment partner writes those numbers and you don’t want Logistified competing with it), you can turn off Logistified’s available movements per location side. The card has two switches, both on by default: - Update source location available in Shopify: sending a TO decrements available at the origin; cancelling or reverting a sent TO restores it, and planned-quantity changes adjust it. Turn it off when a partner writes source-location inventory to Shopify itself. - Update destination location available in Shopify: receiving a TO moves incoming stock into available at the destination. Turn it off when a partner writes destination-location inventory to Shopify itself: receiving then only clears Shopify incoming, and reverting a received TO won’t reduce destination available. The most common setup: you manage the origin warehouse yourself but ship to a 3PL whose own system updates Shopify at the destination; leave the source switch on and turn the destination switch off. Sending still decrements your origin stock, while the 3PL’s receipt is the only thing that raises destination available (no double-counting). Whatever you choose here, Logistified still keeps Shopify incoming quantities up to date (as long as Sync incoming to Shopify below is on) and keeps tracking every movement in the Assemblified ledger; only the available numbers on a turned-off side are left for your partner to manage. The card has a third switch, Sync incoming to Shopify (on by default), controlling the incoming side: - On (default): sending or adjusting a transfer order raises Shopify incoming at the destination, and receiving clears it: the classic behavior. - Off: transfer orders make no Shopify incoming updates at all. Receiving instead adds the received units directly to destination available (when the destination switch above is on). With both destination-facing switches off, transfer orders don’t touch Shopify at the destination in any way. Turn it off when Shopify’s incoming numbers at the destination are owned by another system, or when you simply don’t want in-transit transfers reflected in Shopify. Note that flipping the switch while transfers are in transit can leave a stray incoming quantity in Shopify (raised before the change, never cleared after it); the [Incoming reconciliation] (/features/inventory/incoming-reconciliation/) tool finds and fixes those. The preference is shop-wide and all three switches are on by default, so every existing store keeps its current behavior (stores that previously used the single “Disable Shopify available inventory movements” toggle land with the two available switches off, same effect as before). A Save button appears in the card header once you flip a switch. ### Default line-item sort (Preferences tab) The Line items card in the Preferences tab lets you set the column and direction used to order line items when you open a transfer order. Choose None: order added to keep items in insertion order (the direction toggle is disabled in that mode). The default is product title, ascending. You can still re-sort interactively on the detail page; this preference only sets the starting order. ## Adjacent settings Setting Effect on TOs Settings → Carriers Carrier dropdown on the shipment card. Settings → Email Sending Sender domain, signature, branding for the notification email. Settings → Locations & overrides Origin / destination addresses on the TO PDF. For the post-completion reconciliation tools (Fix On Hand Quantity, Fix Negative Incoming, Adjust Incoming Quantity), see [Lifecycle → The 7 statuses] (/features/supply-orders/transfer-orders/lifecycle/#the-7-statuses) for what unlocks them. ## What’s shared with Purchase Orders The template engines for email and for export columns are shared with Purchase Orders (same editor UI, same available variables), but each order type stores its own templates. Editing a TO email template doesn’t affect POs. Product tags and Shopify Writeback Rules are configured separately per order type. Changing TO product-tag rules has no effect on PO tagging. Note TOs reuse a lot of PO infrastructure under the hood. If you’ve configured POs already, the look and feel of these tabs will be familiar, but the stored settings are independent. ## See also - [Transfer Orders → Exports] (/features/supply-orders/transfer-orders/exports/): where the Export-tab templates are used. - [Purchase Orders → Settings & preferences] (/features/supply-orders/purchase-orders/settings/): the parallel reference for POs. - [Settings → Overview] (/features/settings/overview/): the cross-cutting settings index. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/supplier-stock-releases/overview/ # Supplier stock releases Release supplier-held stock to your warehouse and track delivery receipts. [Elevate plan] (/reference/subscription-plans/) In Logistified, a supplier stock release (SSR) is the order type you use to pull stock that’s physically still at the supplier but already owned by you into one of your warehouse locations. It’s the counterpart to a PO line set to Supplier-held fulfillment: that PO registers the inventory as buyer-owned supplier-held stock; an SSR later releases it. If your supplier never holds your stock (i.e., every PO is delivered straight to your warehouse), you don’t need SSRs. ## On this page - When to use an SSR - Where supplier-held stock comes from - What you can do here - Finding releases - Key concepts - See also ## When to use an SSR You hold stock at your supplier (through buy-ahead, batch production, or pre-positioning) and want to call some of it down to your own warehouse. The SSR captures the request, the shipment, and the receipt, and (optionally) syncs the received warehouse quantity back to Shopify on-hand. ## Where supplier-held stock comes from There are two ways to end up holding stock at a supplier: - A line set to Supplier-held on an ordinary purchase order. Instead of adding to warehouse on-hand, receiving that line creates (or grows) a buyer-owned stock position at the PO’s own supplier. - A whole purchase order [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/). You buy from one supplier and a second one takes delivery; every line is held, and receiving credits the position to the supplier that holds the goods, not the one you bought from. Raise the release against the holder. Either way, that buyer-owned balance is what releases draw from. Consignment stock (goods in your warehouse that the supplier still owns) is tracked separately and cannot be released with an SSR. ## What you can do here [Lifecycle] (/features/supply-orders/supplier-stock-releases/lifecycle/) The 7 statuses, transitions, and what you can edit at each. [Receiving & Shopify sync] (/features/supply-orders/supplier-stock-releases/receiving-and-sync/) How received quantities consume supplier-held stock and reach Shopify. ## Finding releases Search the release list by release number, supplier, location, SKU, or product, or filter it by status, supplier, and date. The date picker offers Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month, alongside a custom range. Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. ## Key concepts - Supplier-held stock position: your inventory physically located at the supplier. Created from PO receipts when the PO line’s fulfillment mode is Supplier-held, or when the whole PO is delivered to another supplier. - Release: the order that moves supplier-held stock from the supplier to one of your warehouses. - Release line item: one variant + requested quantity on the release. - Allocation: the link from a release line item to one or more supplier-held stock positions; consumed as the SSR is received. - Destination location: the warehouse where the release will land. Required before you can send the release. Note SSRs do not create new stock; they only relocate stock you already own from the supplier to your warehouse. The PO receipt is what increased your owned quantity in the first place. ## See also - [PO line items & fulfillment modes] (/features/supply-orders/purchase-orders/line-items/): where supplier-held stock originates. - [Deliver to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/): the other way stock ends up held at a supplier. - [Suppliers → directory] (/features/suppliers/directory/): the Supply tab shows each supplier’s open held stock. - [Line-item column views] (/features/supply-orders/line-item-views/): choosing and saving the columns on the line-item table. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/supplier-stock-releases/lifecycle/ # SSR lifecycle The 7 statuses, transitions, and what you can edit at each. In Logistified, a supplier stock release moves through up to 7 statuses. This page is the reference. ## On this page - The 7 statuses - Status flow - Actions by status - Mutability: what you can edit at each status - Reverts and reopens - See also ## The 7 statuses Status UI label What it means Typical entry draft Draft You’re composing the release. No supplier-held stock is consumed yet. New release created. requested Sent to Supplier The release request has been sent. Lines are allocated against open supplier-held positions. You click Send to Supplier. shipped Shipped The supplier has shipped against the request. Shipped quantities are equal to requested by default. You click Mark as Shipped. partially_received Partially Received Some quantity has been received into the destination warehouse; some is still in transit. First Receive Quantities call that doesn’t cover everything. received Received All requested quantity has been received into the warehouse. Last receipt that closes every line. completed Completed The release is closed. You click Complete Release from Received. cancelled Cancelled The release was cancelled. Any open allocated supplier-held stock is returned to the available pool. You click Cancel Release. Note that the status enum value requested displays in the UI as “Sent to Supplier”; the underlying state name is requested. ## Status flow ``` Draft → Sent to Supplier → Shipped → Partially Received → Received → Completed ↕ (Revert to Draft) ↕ (Revert to Sent) ↑ ↑ └ (Unreceive ─┘ → reverses) └─────────────── Cancelled ←──────────────────┘ ↓ Reopen → previous status ``` - Revert to Draft is available from Sent to Supplier or Shipped; preserves the line items and zeros shipped quantity. - Revert to Sent is available from Shipped; clears shipped quantities back to zero. - Unreceive Quantities is available from Partially Received, Received, or Completed; reverses the warehouse receipt and re-reserves the supplier-held stock. - Reopen Release is available from Cancelled (re-reserves still-open supplier-held stock) or from Completed (moves it back to Received for review). ## Actions by status Status Available primary actions Also in “More actions” Draft Send to Supplier Cancel Release Sent to Supplier Receive Quantities, Mark as Shipped Revert to Draft, Cancel Release Shipped Receive Quantities Revert to Sent, Revert to Draft, Cancel Release Partially Received Receive Quantities, Sync to Shopify (if unsynced) Unreceive Quantities Received Complete Release, Sync to Shopify (if unsynced) Unreceive Quantities Completed Sync to Shopify (if unsynced) Unreceive Quantities, Reopen Release Cancelled Reopen Release Not applicable Send to Supplier is gated: the release must have a destination location, at least one open line item with quantity > 0, and every line’s destination must be available at the chosen location. [anchor: mutability--what-you-can-edit-at-each-status] ## Mutability: what you can edit at each status Status Add lines Delete lines Edit requested qty Edit shipped qty Edit received qty Draft yes yes yes n/a n/a Sent to Supplier / Shipped / Partially Received / Received no (only existing lines) individual lines only no yes yes Completed / Cancelled no no no no no The bulk-edit panel only opens for non-terminal releases. ## Reverts and reopens The detail page exposes step-back actions for cases where you need to undo a forward move: - Revert to Draft clears shipped quantities and resets statuses on lines and schedules, but keeps the line items themselves. Useful if the release was sent prematurely. - Revert to Sent moves a Shipped release back to Sent to Supplier and clears shipped quantities. - Unreceive Quantities rolls back warehouse receipts and re-reserves the supplier-held stock. The allocated supplier-held stock position is increased again accordingly. - Reopen Release from Cancelled re-reserves any supplier-held stock that’s still available; from Completed it moves back to Received. Caution Cancelling a release that has received quantities is not allowed; Received, Completed, and Cancelled releases cannot be cancelled. To reverse a partially received release, use Unreceive Quantities first to zero out receipts, then cancel. ## See also - [Receiving & Shopify sync] (/features/supply-orders/supplier-stock-releases/receiving-and-sync/): what happens to supplier-held stock and Shopify on-hand on receive. - [Overview] (/features/supply-orders/supplier-stock-releases/overview/): what an SSR is and where supplier-held stock comes from. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/supplier-stock-releases/receiving-and-sync/ # Receiving & Shopify sync How received quantities consume supplier-held stock and reach Shopify on-hand. Receiving on a Logistified supplier stock release (SSR) does two things: it consumes allocated supplier-held stock, and it creates a warehouse inventory receipt. The Shopify on-hand update is a separate step, either auto-triggered, or driven manually from the Sync to Shopify action. ## On this page - The receive flow - Partial receipts - Auto-sync vs. manual sync - What Sync to Shopify does - Unreceive - See also ## The receive flow When you click Receive Quantities and submit one or more line receipts: 1. Each requested receipt quantity is matched against open allocations on the line (oldest first). An allocation is the link from a release line item to a specific supplier-held stock position. 2. For each allocation the SSR consumes: - The allocation’s quantityReceived increases; the allocation closes when fully received. - The underlying supplier_stock_position is decremented (quantityTotal and quantityReserved). When the position hits zero, its status becomes consumed. - An inventory receipt line is created against the destination warehouse location (receiptType = supplier_stock_release). 3. The release line item’s quantityReceived is updated; its status becomes partially_received or received accordingly. 4. The release header status rolls up: received if every line is closed, partially_received otherwise. The receipt itself is a normal inventory_receipts row, the same kind used by PO receipts. Each receipt line is marked shopifySyncStatus = pending until you sync it. ## Partial receipts You can receive less than the requested quantity in a single call; the release transitions to Partially Received and you can issue further receipts later. Each call creates a separate inventory_receipts row, visible on the Receipts sub-tab of the line items table. If you try to receive more than the remaining open quantity on a line, the call fails with Received quantity exceeds open release quantity. ## Auto-sync vs. manual sync Whether Shopify gets touched on receive depends on the global setting Auto-sync on receiving (Settings → Purchase orders). The same setting governs PO receipts. - On: every successful receive call immediately attempts to sync the newly received quantities to Shopify on-hand at the destination location. If the Shopify update partially fails, the locally-synced records are rolled back so the receipt and the Shopify state stay in step. - Off: receipts stay flagged shopifySyncStatus = pending. You can sync them later from the Sync to Shopify action on the release header. ## What Sync to Shopify does The Sync to Shopify action opens a dialog listing every line with unsynced received quantity. You pick which lines and how many units to push, then submit. For each line: - The local inventory_receipt_line_items records flip from pending to synced. - An InventoryAdjustment call updates Shopify on-hand at the release’s destination location. - If Shopify rejects any update, the local sync record for that line is rolled back. The action is only offered when the release has at least one unsynced receipt; once everything is synced, the button shows as disabled with “No unsynced warehouse receipts.” An Assemblified sub-assembly line (SKU starting with ASM-) is not updated in Shopify: its received quantity is sent to Assemblified, and the quantity here updates when Assemblified confirms it. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#returns-and-supplier-stock-releases). Note Shopify sync uses the destination location stored on the release header. If the destination is missing the variant in Shopify, that line will fail to sync; fix the Shopify location/variant mapping and retry. ## Unreceive Unreceive Quantities reverses receipts. For each unreceive call: - The most recent receipt allocations for the line are walked back; quantityReceived on allocations decreases, and the underlying supplier stock position is restored (its status flips back to active if it had been marked consumed). - The release line item’s quantityReceived decreases; if it drops to zero on every line the release reverts to Sent to Supplier, otherwise it stays at Partially Received. - The associated receipt line is removed from the inventory receipt. Unreceive does not automatically reverse a prior Shopify sync; if you unreceive quantity that was already synced, you’ll need to sync the corrected (lower) value back to Shopify separately. The unsynced delta becomes negative until you do. ## See also - [Lifecycle] (/features/supply-orders/supplier-stock-releases/lifecycle/): the full status machine, including Reopen and Revert. - [Inventory → Incoming reconciliation] (/features/inventory/incoming-reconciliation/): for catching drift between Logistified and Shopify. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/overview/ # Return orders (RMA) Send stock back to a supplier and reconcile the resulting credit. Elevate-plan feature. [Elevate plan] (/reference/subscription-plans/) In Logistified, a [return order] (/reference/glossary/#return-order) (also known as an RMA, “Return Material Authorization”) records goods you’re sending back to a supplier and the credit you expect to receive. Use it for defective batches, wrong shipments, or any case where you need an audit trail for the return + the credit. RMAs are not customer returns. RMAs are supplier-facing; they go to your supplier. Customer returns happen in Shopify directly. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Lifecycle] (/features/supply-orders/return-orders/lifecycle/) 11 statuses, what you can edit when, and how cancellation works. [Search, filters & saved views] (/features/supply-orders/return-orders/search-and-filters/) Search the list, filter by status/date, and save shop-wide presets. [RMA codes] (/features/supply-orders/return-orders/rma-codes/) Header reason, line reason, condition, disposition. [Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/) Three ways to mint a supplier credit: grouped, per-item, or single line. [Quick actions (fast-forward)] (/features/supply-orders/return-orders/fast-forward/) Three Quick actions that skip intermediate statuses. [Move inventory] (/features/supply-orders/return-orders/move-inventory/) Manual flow to restock taken-back units. [Settings] (/features/supply-orders/return-orders/settings/) RMA codes, email templates, line-item metafields. ## Key concepts - [Return order] (/reference/glossary/#return-order): the artifact itself. - [RMA reason] (/reference/glossary/#rma-reason): header-level reason. - [Line reason] (/reference/glossary/#line-reason): per-line reason. - [Condition] (/reference/glossary/#condition): physical condition per line, typically recorded after inspection. - [Disposition] (/reference/glossary/#disposition): what happens to the returned units. - [Credit memo] (/reference/glossary/#credit-memo): the document confirming a credit. - [Grouped credit] (/reference/glossary/#grouped-credit): one credit covering the whole RMA. - [Quick actions] (/reference/glossary/#fast-forward): Quick Approve & Ship / Quick Close shortcuts (internally “fast-forward”). ## Where to next - [Suppliers → Supplier credits] (/features/suppliers/credits/): the credit ledger. - [Purchase Orders → Applying supplier credits] (/features/supply-orders/purchase-orders/credits/): using credits on POs. - [Guides → Manage returns (RMA)] (/guides/manage-returns-rma/): end-to-end walkthrough. - [Line-item column views] (/features/supply-orders/line-item-views/): choosing and saving the columns on the line-item table. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/lifecycle/ # RMA lifecycle 11 statuses, what you can edit when, and how to undo mistakes. [Elevate plan] (/reference/subscription-plans/) In Logistified, a return order moves through 11 statuses. Eight form a forward chain you’ll walk most of the time; three (On Hold, Rejected, Cancelled) are side states for pauses, supplier refusals, and your own do-overs. Every status (including the “terminal” ones) has at least one back-edge you can use to fix a mistake. ## On this page - The 11 statuses - Forward flow - Backward moves - Dated columns - What you can edit by status - How the status stepper renders the 11 statuses - What cancellation does - See also ## The 11 statuses Status What it means Goes back to Draft You’re composing the RMA. No supplier-side effect. Not applicable Pending Approval Submitted but not yet approved. Draft Approved Approved (by you or by your supplier, depending on flow). Pending Approval In Transit The goods are en route to the supplier. Approved Received by Supplier The supplier confirmed receipt. In Transit Inspection Complete The supplier inspected the goods. Received by Supplier Resolved The credit (or replacement) is finalised. Inspection Complete Closed The RMA is closed for the books. Resolved On Hold Paused. The status you were in before (via Resume) Rejected The supplier (or your team) rejected the return. Pending Approval Cancelled Cancelled. Draft Notably: - No “Disputed” status (unlike POs). - No status is a one-way street. Closed, Rejected, and Cancelled all have a single corrective back-edge so you can fix mistakes without recreating the RMA. - Cancelled wipes forward-progress dates. See the dated-columns section below. ## Forward flow ``` Draft → Pending Approval → Approved → In Transit → Received by Supplier → Inspection Complete → Resolved → Closed ``` From most in-flight statuses you can also branch sideways to On Hold (and resume back) or Cancelled. ## Backward moves Every status except Draft has at least one back-edge. Use these to correct mistakes: - Pending Approval → Draft - Approved → Pending Approval - In Transit → Approved - Received by Supplier → In Transit - Inspection Complete → Received by Supplier - Resolved → Inspection Complete - Closed → Resolved - Rejected → Pending Approval - Cancelled → Draft - On Hold → previous status (via Resume) Note A back-edge fixes the status. It does not unsend an email, unvoid a credit, or reverse an inventory move you made via the Move-inventory dialog; those are independent actions. ## Dated columns Each forward transition stamps a corresponding date: approved date, shipped date, supplier-received date, inspection-completed date, resolved date, closed date. Going on hold stamps an on-hold date; resuming stamps a resumed date; rejecting stamps a rejected date. Cancelling clears only the forward-progress dates (approved, shipped, supplier-received, inspection-completed, resolved). It does not clear the cancelled date, the on-hold date, the resumed date, or the rejected date, and it does not touch the activity log. Caution Clearing the forward dates is destructive for audit. If you cancel an RMA, you lose the original timeline as visible columns. The activity log preserves the full history, but reports that read the columns directly will look as if those steps never happened. ## What you can edit by status Mutability falls into three groups. Fully editable: Draft, Pending Approval. Add or remove line items, change any quantity field, edit the header (supplier, location, reason, notes, costs). Issuing supplier credits isn’t typically meaningful yet because the goods haven’t been received. In-flight: Approved, In Transit, Received by Supplier, Inspection Complete, Resolved, On Hold. You can: - Edit any quantity field (requested, approved, shipped, received, cancelled, taken) at any time. The backend doesn’t gate quantity edits by status. - Edit the header (supplier, location, notes, cost fields, etc.). - Add new line items only in Pending Approval (so for the in-flight statuses: no). - Remove line items in Approved and On Hold (not in In Transit, Received by Supplier, Inspection Complete, or Resolved). - Issue a single-line credit starting at Received by Supplier (gated to Received by Supplier, Inspection Complete, and Resolved). - Issue Individual or Grouped credits in the app at any time, though they only make practical sense once goods are in motion or received. Connected assistants require an assigned supplier and a current status of Received by Supplier, Inspection Complete, or Resolved; see [assistant credit eligibility] (/features/supply-orders/return-orders/issuing-credits/#issuing-credits-through-an-assistant). Locked: Closed, Rejected, Cancelled. No edits. To make changes, use the corrective back-edge (Closed → Resolved, Rejected → Pending Approval, Cancelled → Draft) and edit from there. ## How the status stepper renders the 11 statuses The detail page’s status stepper shows the 8 forward statuses as a horizontal flow: Draft → Pending → Approved → In Transit → Received → Inspected → Resolved → Closed. The three side states (On Hold, Rejected, Cancelled) don’t appear as steps; when one is active, it shows as a coloured badge next to the stepper (amber for On Hold, red for Rejected and Cancelled). This is intentional, not a missing step. ## What cancellation does - The status moves to Cancelled. - Forward-progress dates are cleared (see above). - Issued credits are not automatically voided. Void them separately if you want them gone. - Inventory moves performed via the Move-inventory dialog are not reversed. - The activity log still records the cancellation and preserves the prior history. To pick the RMA back up, transition Cancelled → Draft and edit from there. ## See also - [Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/): the three credit-mint paths. - [Quick actions (fast-forward)] (/features/supply-orders/return-orders/fast-forward/): skipping intermediate statuses. - [Move inventory] (/features/supply-orders/return-orders/move-inventory/): manually moving taken-back stock to a location. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/search-and-filters/ # Search and filter return orders Search the return order list, filter by status or date, and save shop-wide filter presets. Logistified’s return order list has a search box, a set of filters, and named presets that save a filter set (including the search term) for everyone in the shop to reuse. ## On this page - Searching the list - AI search - Adding and editing filters - Available filters - Saving a filter set as a preset - Setting a shop default - Renaming and deleting presets - Edge cases & current behavior ## Searching the list Type into the search box to match against the RMA number, supplier name, or a line’s variant title. The list updates shortly after you stop typing; clearing the box (the × inside it) updates immediately. The search term is shareable; it’s reflected in the page’s URL, so a bookmarked or copied link reproduces the same search. ## AI search You can also describe the returns you want. Click into the search box and press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English and press Enter. A preview shows the filters it understood (status, created by, and a date period on the date you name (submitted, approved, shipped, closed and so on)), and nothing changes until you click Apply. For example: - “approved RMAs Anna Schmidt created last month” - “returns shipped in the last 7 days” There’s no supplier filter on this list, so search for a supplier by name in the normal search box. If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/) for the full walkthrough. ## Adding and editing filters Click + Filter to open the filter picker: choose a field, then set its value. Each active filter appears as a chip below the toolbar; click a chip to edit it, or the × on the chip to remove it. Clear all removes every filter and the search term in one step. ## Available filters - Status: one or more of the 11 RMA statuses (Draft, Pending Approval, Approved, In Transit, Received by Supplier, Inspection Complete, Resolved, Closed, On Hold, Rejected, Cancelled). See [Lifecycle] (/features/supply-orders/return-orders/lifecycle/) for what each means. - Created by: one or more of the people who have raised a return order, so you can narrow the list to a colleague’s returns. RMAs created by a connected AI assistant or an API key are listed under that connection’s name. - Date: a date range on when the RMA was created, with quick choices for Today, Last 7 days, Last 30 days, Last 365 days, This month, and Last month, alongside custom from/to dates. Last 365 days includes today and the preceding 364 calendar days. On narrower windows, the calendar shows one month at a time; use the arrows to move between months. The list also carries a Created by column next to the dates, and each return order shows the same information as a line under its title on the detail page; hover it for the creator’s email address. RMAs raised before this was introduced, and ones created automatically, show only a date. There’s no supplier or location filter on this list; those pickers only appear inside the create dialogs. ## Saving a filter set as a preset Once your filters or search term differ from whatever preset is currently active (or from All, the unfiltered default), a Save button appears next to the filter bar: - Save overwrites the currently active preset with your current filters and search term. - Save as… prompts for a name and creates a new preset, which becomes the active one. A preset saves the whole query: every active filter and the search box’s contents. Selecting a preset later applies both; selecting All clears both. Note Presets are shared by the whole shop, not private to your account. Anyone who saves, renames, stars, or deletes a preset changes it for every staff account viewing the return order list. This isn’t gated by the Elevate plan requirement on the return orders feature itself ; any account that can see the list can save presets on it. ## Setting a shop default Open the preset switcher and use the star action on a preset to make it the shop’s default. The starred preset’s filters and search term are applied automatically the next time anyone opens the return order list with a plain, unfiltered link; a link that already carries filters or a search term (a bookmark, a shared link) always takes priority over the default. Only one preset per shop can be starred at a time; starring a different one clears the previous default. ## Renaming and deleting presets Both actions are available from the preset switcher. Deleting the preset you currently have selected drops the switcher back to All, but leaves your current filters and search term exactly as they were; only the saved preset itself is gone. ## Edge cases & current behavior - A shared link can name a preset that’s since been deleted. The link still applies whatever filters and search term it carried; the switcher just falls back to showing All since the preset it pointed at no longer exists. - The return order list no longer supports the older, browser-only “Save Filters” default. Filter presets are now saved to the shop, not to your browser, so they’re the same for you on any device and for every other operator. - The remembered page size is separate and still per-device. How many rows you see per page keeps following your own browser; it isn’t part of a saved preset. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/rma-codes/ # RMA codes The four code taxonomies: header reason, line reason, condition, disposition. [Elevate plan] (/reference/subscription-plans/) RMA codes are categorisation tags you use on returns in Logistified to keep your reporting consistent. There are four code taxonomies: one for the header, three for line items. ## On this page - The four code types - Operator-managed - Default codes - How they’re used - See also ## The four code types Code type What it categorises Where it lives on the RMA [RMA reason] (/reference/glossary/#rma-reason) Overall reason for the return Header [Line reason] (/reference/glossary/#line-reason) Per-line reason Line item [Condition] (/reference/glossary/#condition) Condition of the units after inspection Line item, post-inspection [Disposition] (/reference/glossary/#disposition) What happens to the returned units (restock / scrap / repair) Line item ## Operator-managed Add / rename / remove codes at Settings → Return Orders → RMA codes. Renames don’t migrate historical RMAs; older RMAs keep the old code string. ## Default codes The app ships with sensible defaults so you can start using RMAs straight away: 11 RMA reasons, 10 line reasons, 6 conditions, and 8 dispositions. Customise to fit your business, for example, “Wrong colour” or “Damaged in transit” as common line reasons. ## How they’re used - When you create an RMA, pick the header RMA reason. - When you add a line, pick a line reason. - Convention is to record Condition and Disposition once the goods have been inspected, but the fields are editable any time the line item is editable; they’re not locked to a specific status. The four codes flow into your downstream reporting: group RMAs by reason, count failures by disposition, etc. Note Renaming a code only affects future selections. Existing RMAs keep the old text. If you need to migrate, edit the RMAs individually or export and re-import. ## See also - [Settings] (/features/supply-orders/return-orders/settings/): where to manage the codes. - [Lifecycle] (/features/supply-orders/return-orders/lifecycle/): when each code is set. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/issuing-credits/ # Issuing supplier credits Three credit-mint paths: single line, per-item (individual), or grouped. [Elevate plan] (/reference/subscription-plans/) Logistified offers three ways to issue a supplier credit from a return order (RMA). Pick the one that fits the supplier’s response. This page is the canonical reference for credit minting; the credit ledger lives at [Suppliers → Credits] (/features/suppliers/credits/); applying credits to POs is at [Purchase Orders → Applying supplier credits] (/features/supply-orders/purchase-orders/credits/). In the UI, the Create credit dialog shows three mode buttons: Grouped, Individual, and Edit (for editing an existing credit on this RMA). ## On this page - The three mint paths - Issuing credits through an assistant - What happens when a credit is issued - Currency - The total credit amount - Voiding and editing a credit - Auto-allocation - Cancellation does not void credits - See also ## The three mint paths The status requirements in this table describe actions in the Logistified app. Connected assistants have the additional requirements below. Path UI label Use when Status requirement Sets credit status to Issue credit for one line (single-line action from the line row) Crediting line-by-line as inspection completes. Received by Supplier, Inspection Complete, or Resolved. “Issued” for that line. Issue per-item (individual) credits Individual in the Create credit dialog Crediting many lines at once. Any status. “Issued” per line. Issue a [grouped credit] (/reference/glossary/#grouped-credit) Grouped in the Create credit dialog Supplier sends one lump-sum credit covering the whole RMA. Any status. “Issued” for every line. ## Issuing credits through an assistant A connected assistant with write access can issue Individual (per-line) or Grouped credits on the Elevate plan. Both require a supplier assigned to the return order and one of these current statuses: - Received by Supplier - Inspection Complete - Resolved The app’s Any status entries above do not apply to assistant-issued credits. For example, an assistant cannot issue a grouped credit on a Draft RMA. Closed, On Hold, Rejected, and Cancelled are also outside the eligible statuses, even if the goods reached the supplier earlier. If credit creation is refused, check the return order’s assigned supplier, current status, and actual return progress. If the saved status is out of date, ask the assistant to make only supported lifecycle changes that reflect what has actually happened and that you authorize. Do not advance or reopen a return solely to unlock credit. If the goods have not reached the supplier, wait for confirmed receipt before asking the assistant to issue the credit. If no supplier is assigned, choose the correct supplier before issuing it. Reaching an eligible status does not create a credit automatically; issuing the agreed credit remains a separate action. See [Operating transfers, stock takes & returns] (/features/agent-access/operating-inventory-and-returns/#supplier-returns-rmas) for the assistant’s other return-order actions. ## What happens when a credit is issued - A credit row appears in the supplier’s credit pool. - The [credit memo] (/reference/glossary/#credit-memo) number is auto-generated. - The total credit amount on the RMA header is recomputed (for individual and grouped paths; see caveat below). - The credit becomes available for application to future POs. ## Currency Each credit keeps its own currency. When you edit a credit, the amounts are shown and labelled in that credit’s currency. The RMA’s total credit amount counts the credits in the supplier’s currency; credits issued in another currency are listed separately on the RMA (for example “Also issued in USD: $100.00”), so amounts in different currencies are never added together on the RMA. The balance roll-up on the supplier’s Credits tab still sums every currency (see [Suppliers → Credits] (/features/suppliers/credits/#currency-awareness)), so we still recommend keeping a supplier on a single currency where you can. ## The total credit amount Every way of issuing, editing or voiding a credit (single line, Individual, Grouped, Edit and Void) recomputes the RMA’s total credit amount from its credits, so it always matches the credits it shows. Editing one credit of an RMA that has several keeps the others in the total. If some lines were removed from the RMA while the Individual credits dialog was open, the credits for the remaining lines are still created and you’re told what was skipped: “Created 1 of 2 credits. 1 item was skipped because it is no longer on this return order.” If none of the lines are left, nothing is created and the dialog stays open. ## Voiding and editing a credit [Voiding] (/reference/glossary/#void) removes the credit from the supplier’s available pool. Voiding is irreversible; there is no “unvoid” action. If you’re not sure, edit instead. Editing a credit can change the total amount, the per-line breakdown, and the credit memo. Edits cascade back to the RMA header’s total credit amount. ## Auto-allocation There is none. Credits sit in the supplier’s pool until you choose to apply them to a specific PO. ## Cancellation does not void credits If you cancel an RMA after issuing credits, the credits stay valid. To remove them, void each one explicitly. Note Credit minting is always operator-driven. Lifecycle transitions like “Received by Supplier” or “Resolved” don’t mint credits automatically. ## See also - [Suppliers → Credits] (/features/suppliers/credits/): the credit ledger. - [Purchase Orders → Applying supplier credits] (/features/supply-orders/purchase-orders/credits/): using a credit on a PO. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/fast-forward/ # Quick actions (fast-forward) Three one-click shortcuts that skip intermediate RMA statuses when speed matters. [Elevate plan] (/reference/subscription-plans/) Quick actions (internally called [fast-forward] (/reference/glossary/#fast-forward)) are one-click shortcuts that skip intermediate statuses on a Logistified return order (RMA). They live as a second item in each transition button’s split-dropdown, alongside the manual version. Useful when the intermediate states aren’t operationally meaningful. ## On this page - The three Quick actions - “Mark All In Transit” is not a Quick action - What Quick actions do NOT do - See also ## The three Quick actions - Quick Approve & Ship: Pending Approval → In Transit. Stamps approved and shipped dates; fills approved and shipped quantities from the requested quantity. - Quick Close (from In Transit): In Transit → Closed. Stamps supplier-received, inspection-complete, resolved, and closed dates; fills received quantities from shipped. - Quick Close (from Received by Supplier): Received by Supplier → Closed. Stamps inspection-complete, resolved, and closed dates; fills received quantities from shipped. In the UI, each appears in the actions split-dropdown for the current status: Pending Approval has Manual Approval + Quick Approve & Ship; In Transit has Mark Received + Quick Close; Received by Supplier has Complete Inspection + Quick Close. ## “Mark All In Transit” is not a Quick action The Approved → In Transit dropdown has a similar-looking option called Mark All In Transit that ships every approved quantity in one step. It’s a regular transition with auto-fill, not a status-skip; the RMA still ends up in In Transit, not further along. Don’t confuse it with Quick Approve & Ship (which jumps two statuses) or Quick Close (which jumps to the end). ## What Quick actions do NOT do - They don’t mint credits. Crediting stays a separate, explicit operator action; see [Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/). - They don’t run any per-status side effect that wasn’t already running. - They don’t move inventory back into a location; use the [Move-inventory dialog] (/features/supply-orders/return-orders/move-inventory/) for that. Note Dated columns get stamped honestly; if you use a Quick action today, every intermediate date reads today. The audit log still records the single Quick-action click; it doesn’t fabricate distinct earlier steps. ## See also - [Lifecycle] (/features/supply-orders/return-orders/lifecycle/): the full status flow. - [Issuing supplier credits] (/features/supply-orders/return-orders/issuing-credits/): what Quick actions don’t do for you. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/move-inventory/ # Move inventory dialog Manually restock taken-back units to a specific location. [Elevate plan] (/reference/subscription-plans/) A separate operator-driven flow on a Logistified return order moves taken-back units back to inventory at a specific location. Useful when: - You’ve been shipped extra units in error and want to restock them. - You’re salvaging usable units from a defective shipment. ## On this page - What it does - How to launch - What it does NOT do automatically - See also ## What it does Moves units recorded as “taken back” on RMA lines into inventory at a location of your choice. Updates the location’s on-hand; pushes the change to Shopify. An Assemblified sub-assembly line (SKU starting with ASM-) is never sent to Shopify: the move is sent to Assemblified, and the quantity here updates when Assemblified confirms it. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/#returns-and-supplier-stock-releases). ## How to launch From the RMA detail page → Move Inventory button. The dialog shows every line on the RMA. Rows with nothing left to move are shown but disabled, so you can always see the full line list. The button is hidden in Closed, Rejected, and Cancelled RMAs; use the corrective back-edge (see [Lifecycle] (/features/supply-orders/return-orders/lifecycle/)) to reopen the RMA first. ## What it does NOT do automatically Inventory moves are never triggered by RMA status transitions. You always launch the dialog explicitly. Tip If your supplier returns goods to you after rejecting your RMA (rare but possible), use this dialog to add them back to inventory at the right location. ## See also - [Lifecycle] (/features/supply-orders/return-orders/lifecycle/): the RMA’s overall flow. - [Inventory → Inventory levels] (/features/inventory/inventory-levels/): what the move updates. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/return-orders/settings/ # RMA settings & preferences RMA codes, email templates, export templates, and line-item metafields. [Elevate plan] (/reference/subscription-plans/) The settings for Logistified’s return orders (RMAs) hold the RMA codes, email templates, export templates and line-item metafields. ## On this page - Where RMA settings live - Sub-sections - Update Metafields action - Adjacent settings - What’s not yet supported - See also ## Where RMA settings live Settings → Return Orders. ## Sub-sections The Settings → Return Orders page has six tabs: Tab What it configures RMA Codes Header RMA reason codes (the dropdown shown at the top of every RMA). Item Codes The three line-level taxonomies (line reason / condition / disposition). Metafields Variant metafields visible on RMA lines. Preferences Line items: sets the default sort order for line items when you open a return order. Pick a column (None · order added, Product, SKU, Requested, Unit cost, or Credit) and a direction (ascending / descending). Default is Product, ascending. Export Columns in CSV / XLSX exports and PDF layout. No per-supplier assignment: unlike PO export templates, the shop default always applies. The CSV / XLSX column picker is searchable and grouped by source, and its catalog includes live inventory (at the return’s location and across all locations), planning-constant, and ABC / revenue variant columns alongside the RMA fields, none selected by default. Email Templates Subject + body for the supplier email. Per-supplier overrides supported. ### Update Metafields action Turning on a line-item metafield in the Metafields tab only stamps lines added from then on; lines already on a return order won’t pick it up automatically. Each return order’s actions dropdown has an always-available Update Metafields entry that fills in a value for every line missing one and refreshes lines that already have one, using current data from Shopify. It never clears an existing value, so it’s safe to run at any time; a line that can’t be matched to a Shopify product is simply left untouched. The same action exists on purchase orders and transfer orders. ## Adjacent settings Setting Effect on RMAs Settings → Tax Rates RMAs don’t carry tax; credits are pre-tax. Settings → Email Sending Sender domain, signature. Settings → Locations & overrides Return address on the PDF. Settings → Carriers Carrier dropdown for the return shipment. ## What’s not yet supported - Approval workflow toggles (multi-step approver chains). - Auto-credit on Resolved (operator-driven by design). - Per-supplier disposition policies. Note Most RMA infrastructure (email, export, PDF) is shared with Purchase Orders. If you’re new to Logistified, configure POs first; RMA behavior will feel familiar. ## See also - [Purchase Orders → Settings & preferences] (/features/supply-orders/purchase-orders/settings/): the parallel PO reference. - [RMA codes] (/features/supply-orders/return-orders/rma-codes/): what the code editor controls. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/overview/ # Manufacturing orders Plan and track a production run, items you build in-house or have a subcontractor build for you. In Logistified, a manufacturing order (MO) plans and tracks a production run: build a target quantity of one or more items, either in-house or through a subcontractor, using materials that come from your own stock or a supplier’s. It ties together the purchase orders, transfers, stock releases and stock adjustments that actually move the materials and the finished goods, and shows you progress across all of them from one page. Note Manufacturing orders are an Elevate plan feature. ## On this page - What a manufacturing order is and isn’t - Statuses - Builds: in-house vs. subcontract - Creating a manufacturing order - The list page - What you can do here - Key concepts - Where to next [anchor: what-a-manufacturing-order-is--and-isnt] ## What a manufacturing order is and isn’t - It’s a plan and a dashboard: target quantities, the materials each unit needs, and how much has actually been built or received, all computed live from the documents linked to it. - It’s not a separate inventory movement. A manufacturing order never adjusts stock on its own; every quantity change happens through a linked purchase order, transfer order, supplier stock release, or stock adjustment. Cancelling or deleting a manufacturing order never touches those documents; it only removes the connections between them. - It’s not a costed document. Manufacturing orders don’t carry prices, and the production PDF you send to a manufacturer never shows one, regardless of your other document settings. ## Statuses Status Meaning Draft The plan is being set up (items, quantities, materials) before any production has started. In Progress Production is underway: materials have been staged, work has been recorded, or the order was sent to a manufacturer. Completed The run finished. Cancelled The run was called off. A cancelled order is archived; it drops out of your active lists but its history stays intact. ## Builds: in-house vs. subcontract Each item on a manufacturing order belongs to a build: the actual production run for that item. A build is either: - Internal: you make it yourself, at one of your own locations, using your own team. - Subcontract: a manufacturer makes it for you. You choose which supplier is doing the work, and can send them a production order by email. Materials for a build can come from stock already on hand, or be staged first through a purchase order, a transfer, or a supplier stock release; Logistified shows what’s needed, what’s available, and what’s still missing as you work. ## Creating a manufacturing order Go to Supply Orders → Manufacturing Orders and select Create Manufacturing Order. The dialog asks up to three questions, and everything else follows from the answers: Choice Options What it decides Where Internal or Subcontracted Internal asks for a Production location; subcontracted asks for a Manufacturer. Execution Manual or Assemblified engine Manual means you type the materials in yourself and record production by hand. The engine reads each product’s bill of materials from Assemblified. Materials Already at the manufacturer or From my stock Subcontracted builds only, where the materials the manufacturer will use come from. All four combinations of Where and Execution are allowed: a subcontracted build can use the engine’s bills of materials too. Assemblified engine is offered only when the shop has a connected Assemblified account; without one the option is greyed out with a note, and Manual works the same way except that you enter the materials yourself. Switching Where back and forth keeps whatever you already chose for Execution and Materials. On a subcontracted build, the Materials answer describes the usual route for that build: Already at the manufacturer means they’re on the manufacturer’s shelf, or arrive there on a purchase order delivered straight to them; From my stock means you ship them out of one of your own locations. See [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/) for what each one creates. You can also give the order an optional Name (leave it blank and it shows by number), an Expected completion date (strongly recommended, since it’s what places these units on the forecast timeline) and Notes. ### Items and materials Add one row per product with Add product, and set the Target quantity you want built. Expand a row to see that product’s materials, shown both Per unit and as a Total against the target; change the target and the total rescales. - On an Assemblified engine build, materials are filled in from the product’s bill of materials and marked from BOM; their per-unit quantities are read-only, and a refresh control re-reads them. - On a Manual build (or for a product the engine has no bill of materials for), you add the materials yourself and type how much of each one unit needs. A build can mix the two: a product with no bill of materials inside an otherwise engine-driven build is labelled Manual and is built and recorded by hand. You can also start an order from the [Forecast page] (/features/forecast/view-table/): select rows, then Actions → Create Manufacturing Order, and the dialog opens with each target already filled in from the row’s suggested reorder quantity. Those rows also show MOQ and Pack columns; a target below the primary supplier’s minimum order quantity or off its pack size is flagged Below MOQ or Not a pack multiple, with a Round all up button that fixes every flagged row at once. ## The list page The manufacturing orders list shows one row per order: Column What it shows Manufacturing Order The order number, its optional name, and how many builds it has. Status Draft, In Progress, Completed or Cancelled, with an Overdue badge beside it when an in-progress order’s expected completion date has passed. Target Total units planned across the order. Built Total units produced so far. Buildable now How many more units the materials on hand could actually make. Progress Three short badges (materials, building and distribution) summarising how far along the run is. Created When the order was created. Created by Who created it. Search by manufacturing order number, and filter by Status, Execution, Production location, Created by, and a Date range on when the order was created or last updated. Any combination of filters and search term can be saved as a named preset that everyone in the shop can reuse, the same way the [transfer order list] (/features/supply-orders/transfer-orders/search-and-filters/#saving-a-filter-set-as-a-preset) works. You can also describe the orders you want with AI search: click into the search box, press Tab (or click the light-blue Tab: try AI search badge; on a phone or tablet, tap AI search), type a request in English such as “in-progress automatic MOs at the Berlin warehouse created last month” or “cancelled manual MOs”, and press Enter. A preview shows the status, execution, production location, created by and date filters it understood, and nothing changes until you click Apply. If you don’t see the badge, AI search isn’t enabled for your shop yet. See [Find orders with AI search] (/guides/search-with-ai/). Each row has a checkbox. Select orders individually (selections carry across pages), the whole page, or everything matching your filters, then use Export above the table for a CSV or XLSX; see [Bulk-exporting from the list page] (/features/supply-orders/manufacturing-orders/documents-and-exports/#bulk-exporting-from-the-list-page). ## What you can do here [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/) Allocate materials, record production, distribute finished goods, and read the badges on every item. [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/) Get materials to a manufacturer, record what they built, and bring the finished goods back. [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/) Generate a production PDF, attach files, email a subcontractor, export CSV/XLSX, and print finished-goods labels. [Settings] (/features/supply-orders/manufacturing-orders/settings/) Export templates and the manufacturer email template, where they live and what they control. Day to day, from the manufacturing order list and detail pages you can also: - Edit details: the name and notes stay editable while a run is in progress; the build’s mode, location/manufacturer, and material source can only be changed while it’s still a Draft. - Record production as it happens, and see a live rollup of what’s built, what materials are still needed, and whether anything is overdue against its expected completion date. Select all in the record-production dialog fills every line with exactly what’s left to reach its target. - Leave comments on the order’s activity log for your team, alongside the automatic history of every status change and action. - Delete or cancel an order; deleting removes its attachments and activity log along with it; the linked purchase orders, transfers and adjustments are left untouched either way. ## Key concepts - Manufacturing order: the plan for a production run. - Build: one item’s production run within the order: internal or subcontract, with its own location or manufacturer. - Target: the quantity a build is meant to produce. - Built: the quantity actually produced so far, computed from the linked documents and recorded production. - Overdue: a badge shown on an in-progress build whose expected completion date has passed. It’s informational only; nothing else changes automatically. ## Where to next - [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/): what the detail page shows and every action on it. - [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/): working with a manufacturer end to end. - [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/): the production PDF, attachments, sending to a subcontractor, and CSV/XLSX exports. - [Settings] (/features/supply-orders/manufacturing-orders/settings/): export and email templates. - [Purchase orders] (/features/supply-orders/purchase-orders/overview/), [Transfer orders] (/features/supply-orders/transfer-orders/overview/) and [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/): the documents a manufacturing order links to for staging materials and receiving finished goods. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/the-build-card/ # The build card Read the item-by-item Build card, allocate materials, record production, and distribute finished goods. Opening a manufacturing order in Logistified shows the Build card: everything about that production run in one place, one row per item you’re making. Manufacturing orders are an Elevate plan feature. ## On this page - The three page tabs - The card header - Warnings - Items to build - The toolbar - The documents table - The Materials tab and claims - Header actions ## The three page tabs Tab What’s on it Plan & Progress An Overview card with the headline numbers, then the Build card itself. Notes & Activity Log Internal Notes you can save, plus an Activity feed of every status change and action. You can leave comments there for your team, and edit or delete your own. Attachments Files, generated documents and the manufacturer email history: see [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/). Everything on the Build card is worked out from the documents linked to it each time you load the page. Nothing is stored, so receiving, reverting or cancelling a linked document shows up here immediately. ## The card header The header names the build (Internal or Subcontracted, Manual or Assemblified engine, and the location or manufacturer it runs at) with the expected completion date underneath. If no date is set, it says so: a build without one doesn’t appear on the forecast timeline. Below that, three badges say where the build stands: Phase Badges Materials No materials required · Unallocated · Partially allocated · Allocated · Materials arrived Building Not started · In progress · Built Distribution Not started · In transit · Partially distributed · Distributed Then a one-line roll-up: how many units are buildable now, how many are built against the target, and (once anything has been made) how many have been received back into a location out of what was built. Note A unit counts as distributed only once it has been received. Units on their way are counted separately as in transit and never folded into the distributed figure. ## Warnings A warnings strip sits above the items table whenever something is worth a second look. It’s always one summary line (how many materials aren’t fully arrived, how many other warnings there are, and which items can’t be built yet) with a Show details toggle. Expanded, material shortfalls become a small table: the material, how much has Arrived, how much is Needed, and how many of each item’s remaining units that pile covers if it’s used on them first. Other warnings read as one line each, for example: - an item built past its target (not an error: the numbers simply stop treating the target as a ceiling), - a material or item claimed on more documents than it needs, - work orders planning more units than the target, - an item with no bill of materials being built by hand inside an engine build, - an expected completion date that has passed. Nothing here blocks anything, and the same warnings put a marker on the item rows they’re about, so the strip and the table never disagree. ## Items to build One row per item, with: Column What it shows Item Product name and SKU, plus a Manual badge when the item has no bill of materials, and a warning marker when the row has one. Target How many units this item is meant to produce. Materials A badge: None needed, Needs allocation, Arriving, Ready, or Built. The number in brackets is how many units the arrived materials can make. Building Built against target with a progress bar, how many are buildable now, and a chip per work order on engine builds. Distribution How many finished units have been received, and how many are still in transit. Documents Chips for the documents feeding this item: select one to jump to its row in the documents table below. Expand a row to see that item’s own materials and how much of each it still needs. Each row also has its own menu, grouped Materials / Building / Distribution, that runs the toolbar actions below scoped to just that item. ## The toolbar The actions sit on the tab row above the table and act on the whole build; the same actions appear on each item’s row menu scoped to that item. They’re available while the run is live; once an order is Completed or Cancelled the card becomes read-only. Link document attaches a document that already exists: either an Allocation document (a purchase order, transfer order or supplier stock release bringing materials in) or a Distribution document (a transfer order or supplier stock release moving finished units out). Search by number and pick it. Allocate materials turns a shortfall straight into a new, already-linked document. The Source is the only real choice; the kind of document follows from it and from how the build is set up: Source What it creates Order from a supplier A purchase order, delivered to your production location, or straight to the manufacturer on a subcontracted build. Release supplier-held stock A supplier stock release out of a supplier’s shelf. Internal builds only. Transfer from a location A transfer order out of a location you pick. Quantities open pre-filled with what’s still missing, rounded up to the supplier’s minimum order quantity and pack size where they apply, the same rounding you’d see creating a purchase order from the forecast. The rounding is advice, not a lock: lower a quantity and you get a Below MOQ or Not a pack multiple flag rather than a refusal. Build opens a menu whose contents depend on how the build runs: - Record production: enter how many units were made. On an internal build this prepares a stock adjustment that draws the materials and adds the finished units; because inventory is tracked in whole units, fractional material draws are rounded to the nearest whole number and the dialog tells you when that happened. On a subcontracted build it draws and credits against the manufacturer’s stock instead; see [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/#recording-production). Select all fills every line with exactly what’s left to reach its target. - Add work order: internal engine builds only. Creates a work order in Assemblified for the items that have a bill of materials, or links one that already exists; its progress then flows back to the build automatically. A build can carry several. - Track a work order: subcontracted builds only. Links the manufacturer’s work order so you can see its status, for reference only. Distribute finished goods sends built units onward. It’s called Send finished goods on an internal build (a transfer order out of the production location) and Release finished goods on a subcontracted one (a supplier stock release out of the manufacturer’s stock). Pick a destination location; quantities pre-fill with what’s been built but not yet sent, so running it again after a partial send suggests exactly the remainder. Refresh requirements appears on engine builds and re-reads the bills of materials in case they changed, only while the order is still a Draft. Note Which build action an item offers depends on how it’s made. An item with a bill of materials on an internal engine build is driven by a work order; everything else (manual builds, items with no bill of materials, and all subcontracted production) is entered by hand with Record production. ## The documents table Under the items table, every document linked to the build is listed with its number, type, Phase (allocation, execution or distribution), status, the items it carries and what it contributes. Selecting a document chip on an item row highlights its row here. Cancelled or deleted documents stop contributing numbers but stay listed, so the paper trail is never lost. ## The Materials tab and claims The Materials tab lists every material the build needs, with Needed, Allocated and Arrived quantities plus a stock column (Available at your production location on an internal build, or At manufacturer on a subcontracted one) alongside SKU and barcode. Under the table, each material has a collapsible Documents panel showing the documents bringing it in: how much is On document, how much is Allocated and Arrived, and a Claimed figure you can edit. A claim is how you say what share of a shared document belongs to this build. Order 500 metres of webbing on one purchase order for three runs, and the claim is where you record that 200 of them are this build’s. Leave it blank (it reads Auto), and Logistified works the split out for you. A claim larger than the document carries is flagged rather than blocked. On a subcontracted build the tab also keeps a history of everything recorded at the manufacturer, with a Reverse action per entry. ## Header actions At most two actions sit directly in the header; the rest are in the Actions menu, grouped Change status, Export & tools, then the destructive ones. Action What it does Edit details Change the name, dates and notes. The build’s mode, location or manufacturer, and material source can only change while the order is a Draft. Start production / Mark as Completed / Cancel / Reopen The status transitions. Completion is never automatic; when everything is built and received, the page suggests it and you confirm. Send to manufacturer / Resend Email the production document to a subcontractor. Quick PDF export and Export… The production PDF and CSV/XLSX exports. Print labels Finished-goods labels, with a preset that sets each item’s label count to its target. Revert to Draft Undo a mistaken send, while nothing has been produced yet. Delete Remove the order and its attachments. Linked purchase orders, transfers and adjustments are left untouched. The email, PDF, export and label actions are covered in detail on [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/). ## See also - [Manufacturing orders overview] (/features/supply-orders/manufacturing-orders/overview/): creating one, and the list page. - [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/): recording production and getting finished goods back from a manufacturer. - [Purchase orders → Receiving] (/features/supply-orders/purchase-orders/receiving/) and [Transfer orders → Shipping and receiving] (/features/supply-orders/transfer-orders/shipping-receiving/): what happens on the documents a build links to. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/subcontracting/ # Subcontracting a build Have a manufacturer build for you, and track your materials and finished stock at their location. A subcontracted build is one you don’t make yourself; a manufacturer makes it for you. Logistified tracks what you own at their location, both the materials you send or buy in there and the finished goods they produce, until you bring those finished goods into one of your own locations. Manufacturing orders are an Elevate plan feature. ## On this page - Getting materials to the manufacturer - Sending the production order - Recording production - Tracking a work order - Getting finished goods back - What this does to your Shopify inventory ## Getting materials to the manufacturer When you create a subcontracted build you answer a Materials question, and the answer names the route you’ll normally use: Answer What it means The document you’d raise Already at the manufacturer They’re on the manufacturer’s shelf, or you buy them in from a supplier who delivers straight to the manufacturer. A purchase order delivered to the manufacturer. From my stock You ship your own inventory out to them. A [transfer order addressed to that supplier] (/features/supply-orders/transfer-orders/supplier-destination/), which they receive and hold as stock that’s still yours. Either way, the materials end up counted as supplier-held stock: goods you own that physically sit at the manufacturer. The [supplier stock releases overview] (/features/supply-orders/supplier-stock-releases/overview/#where-supplier-held-stock-comes-from) explains that balance in general. The answer is a default, not a rule. From the build card’s Allocate materials action a subcontracted build can raise either document whenever it needs to: a purchase order to the manufacturer, or a transfer out of one of your locations. Releasing supplier-held stock isn’t offered on a subcontracted build: the materials need to reach the manufacturer, not come home. ## Sending the production order Once the plan is right, Send to manufacturer emails the build its own production document (a PDF, XLSX or CSV) to the manufacturer’s contact. It’s offered only on a subcontracted build with a manufacturer assigned, and the first send moves the order from Draft to In Progress. A production document never shows a price. Full detail, including resending, the email history and rolling a mistaken send back to Draft, is on [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/#emailing-a-subcontractor). ## Recording production When the manufacturer tells you units are finished, select Record production on the build card and enter how many units they built. Unlike an internal build (where inventory is tracked in whole units and fractional material draws get rounded), a subcontracted build accepts exact quantities. 2.5 kg of foam is submitted as 2.5. The material figures are pre-filled from units times per-unit quantity, and you can correct them to whatever was actually used. Recording production does two things in one step: 1. Draws down the materials the build consumed from what the manufacturer is holding for you. 2. Credits the finished units back onto the manufacturer’s shelf, as stock you now own at their location. If there isn’t enough of a material at the manufacturer to cover the draw, the submission is refused with the shortfall named per item and nothing is written. Recorded entries are listed on the build’s Materials tab, each with a Reverse action. Reversing writes a paired, opposite entry that undoes the draw-down and the credit together, so the history stays a full record rather than an edited one. An entry that has already been reversed can’t be reversed twice. ## Tracking a work order If the manufacturer also uses Assemblified, Track a work order on the build card’s Build menu links their work order so you can see its status here. A build can track more than one. Note Tracking is informational only. A work order on a subcontracted build never draws the build’s materials or moves its built figure; production is always what you enter with Record production. The build card says so under the tracked work orders. ## Getting finished goods back Finished units credited at the manufacturer aren’t in one of your locations yet. Distribute finished goods opens the Release finished goods dialog, which creates a supplier stock release for the units the manufacturer has built and is still holding, addressed to a destination location you pick, and links it to the build. Quantities pre-fill with what’s been built but not yet sent or received, so running it again after a partial release suggests exactly the remainder. The release then behaves like any other; see [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/) for shipping and receiving it. A build only counts units as distributed once the release has been received. Units on their way show separately as in transit. ## What this does to your Shopify inventory Nothing, until the goods land in one of your locations. Materials shipped out on a transfer order to the manufacturer leave your location’s stock and become supplier-held; buying them in on a purchase order delivered to the manufacturer never touches a location at all. Recording production moves quantities between two supplier-held balances at that manufacturer. Only when you receive the supplier stock release does stock arrive in a Shopify location. ## See also - [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/): the rest of the card’s toolbar, badges and tabs. - [Transfer orders → Ship to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/): sending your own stock to a manufacturer. - [Supplier stock releases] (/features/supply-orders/supplier-stock-releases/overview/): calling stock back out of a supplier. - [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/): the production PDF and the email path. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/floormode-execution/ # Manufacturing in a Floormode warehouse When Floormode runs the production warehouse, it picks a manufacturing order's components and books its output; what the order's card shows and what Logistified refuses. If your shop uses Floormode, our companion warehouse app, a manufacturing order produced at a warehouse Floormode runs is executed through Floormode. Floormode’s team picks the components and puts the finished goods away; Logistified keeps the order, its plan and its built counts, but writes no stock adjustment for it. Note This applies to a manufacturing order with one build, Internal and Manual (see [Builds] (/features/supply-orders/manufacturing-orders/overview/#builds-in-house-vs-subcontract)), whose production location is a warehouse you handed to Floormode under Settings → Integrations (see [Integrations] (/features/settings/integrations/#floormode)), and that no Assemblified work order executes. Every other order works as described in [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/). ## On this page - How it runs - The Floormode card - Orders Floormode doesn’t execute - When Floormode can’t take a step - Handing the warehouse back - See also ## How it runs 1. Start production. Floormode receives the order’s component plan (the requirements times the targets) and picks the components to its production bench. 2. Record production. Use the order’s Record production dialog as usual. Instead of a stock adjustment, Logistified tells Floormode which components the production consumed and how much finished goods it made. Floormode books both, and puts the output away. 3. Built counts. What you record counts as built straight away, on the order, in the list, in exports and in the forecast’s incoming, even before Floormode has put it away. Editing the materials or the targets of a started order sends Floormode the changed plan. Cancelling the order cancels Floormode’s pick. Recording the same production twice is safe: pressing Record production again in the same dialog after an interrupted answer never records it twice. ## The Floormode card The order’s page shows where Floormode stands, step by step: The card says What it means Sent to Floormode Logistified handed Floormode the plan; Floormode hasn’t cut a pick yet. Pick these components in Floormode Floormode cut a pick for it; the card links to it. Picking in Floormode Floormode is picking. Staged in Floormode · record a build The components are at the bench. Record what you produce. Picked short in Floormode / Pick cancelled Floormode could not pick everything, or its pick was cancelled. Put away this output in Floormode · receipt Floormode received the output you recorded; the card links to its put-away. Put away N so far in Floormode / Put away N Part of the recorded output, or all of it, is on the shelf in Floormode. If Floormode refuses something, the card shows Floormode’s reason and what to do: - A production’s components were not booked: correct the cause in Floormode. Don’t record that production again; that would count its output twice. - The output was not put away: correct the cause in Floormode. Don’t record it again: the whole output is sent again with the next production you record. - The plan was refused: correct the materials or the targets; the change is sent again. ## Orders Floormode doesn’t execute Two kinds of order at a Floormode warehouse stay outside Floormode. The card says why, and production follows the ordinary [build card] (/features/supply-orders/manufacturing-orders/the-build-card/) path: - “Floormode executes a manufacturing order with one build. Split the builds into separate manufacturing orders.” Split the order if you want Floormode to execute it. - “This manufacturing order is executed by an Assemblified work order, so Floormode does not execute it.” Unlink the work order if you want Floormode to execute it, or keep producing through Assemblified. The reverse is refused: an order Floormode executes can’t be linked to an Assemblified work order once it has started (“Floormode executes this manufacturing order, so an Assemblified work order cannot execute it too.”). ## When Floormode can’t take a step On an order Floormode executes, Logistified refuses a step Floormode could not carry out, before anything is sent or recorded: You see What to do “These materials are not stocked in Floormode at the production location: … Stock them in Floormode there first.” Stock the named materials in Floormode at that warehouse, then try again. “Floormode has not confirmed this material at the new connection yet. Try again in a moment.” Right after the receiving agreement was confirmed again. Wait a moment and record again. “Sub-assemblies are not executed in Floormode yet” Remove the Assemblified sub-assembly from the materials before starting. “Start production first: Floormode picks the materials when the manufacturing order starts.” Start the order, then record. “Production was already recorded through Floormode at another location.” Move the build back to that location, or create a new manufacturing order for this one. “Floormode can only put away products that exist in Shopify.” Record output only for products that exist in Shopify. ## Handing the warehouse back You can’t hand a warehouse back to Logistified while a manufacturing order there is still in production in Floormode. On the Floormode card, Check readiness for a list that no longer includes the warehouse, its activation, and Return to shop-wide receiving all refuse the change and name the order: “Finish or cancel MO-… first: it is still in production in Floormode at a location this change hands back to Logistified.” An order counts as in production until it is completed or cancelled, every unit of output recorded on it is put away in Floormode, and nothing about it is still on its way to Floormode. Finish or cancel it, then check readiness again. ## See also - [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/): recording production when Logistified runs the warehouse. - [Connect Floormode and Assemblified] (/guides/connect-floormode-and-assemblified/): the three-app setup. - [Integrations] (/features/settings/integrations/#floormode): handing warehouses to Floormode. Last updated: 31 October 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/documents-and-exports/ # Documents, exports & manufacturer email Generate a production PDF, attach files, email a subcontractor, export CSV/XLSX, and print finished-goods labels. Everything on this page lives on a Logistified manufacturing order’s Attachments tab, its Actions menu, and the list page’s bulk export, all Elevate-plan features. ## On this page - The production PDF - Attachments - Emailing a subcontractor - Undoing a send - CSV / XLSX exports - Bulk-exporting from the list page - Finished-goods labels ## The production PDF The production PDF is generated per build, not for the whole order; if a manufacturing order has more than one build, each gets its own PDF, so a subcontractor only ever sees their own build’s targets, never another manufacturer’s. It shows: - A build details block: expected completion, execution mode, material source, created date. - Any manufacturing notes you’ve added to the order. - The items being built (name, SKU, barcode and image where available) with the target quantity, and optionally what’s already built and what’s remaining. - The materials the build needs. A subcontract build lists what you’re sending the manufacturer and which document it’s coming on; an internal build shows a shop-floor pick list: required, allocated, arrived and available. - The manufacturer’s details on a subcontract build, or your production location’s details on an internal one. Each of these (the Built quantity, the Remaining quantity, the build details block, the notes, and the materials table) can be switched off independently in the template, so a subcontractor-facing copy can be trimmed down without losing the sections you want to keep. The production PDF never shows a price, no matter how your document settings are configured elsewhere; manufacturing orders don’t carry cost information. To get a PDF: open the order’s Actions menu and choose Export… under Export & tools, or Quick PDF export, which downloads the default template’s PDF immediately. Both use the templates configured at [Settings → Manufacturing Orders → Export] (/features/supply-orders/manufacturing-orders/settings/#export-templates). ## Attachments The Attachments tab holds every file associated with the order: files you upload yourself (drawings, spec sheets, quotes, certificates) plus every document Logistified generates for it (PDFs, exports, labels, and anything sent by email). - Uploading: from the Attachments tab, choose a file and a document type, then upload. Files can be added or removed regardless of the order’s status, so you can still attach a completion certificate to a finished run. - Removing: delete a file from the same tab; this can’t be undone. - Auto-attached files: a PDF or export downloaded with “Attach to my documents” checked, and any file sent by email, are saved here automatically, labeled by type (PDF Export, Excel Export, CSV Export, Email Attachment). Note The Attachments tab is separate from the Documents column shown against each item in the build; that column lists the purchase orders, transfers and other records linked to the build, not files. ## Emailing a subcontractor Send to manufacturer appears on a subcontract build that has a manufacturer assigned; it’s not offered on an internal build, since there’s nobody to email. When you send: 1. Choose the attachment format (PDF, XLSX or CSV) and either reuse a file already on the Attachments tab or generate a fresh one. 2. Logistified emails the production document to the manufacturer’s contact and files a copy on the Attachments tab as an Email Attachment. 3. The first send moves the order from Draft to In Progress. Sending again (a resend) doesn’t change the status. If the order is already Completed or Cancelled, sending is blocked. A record of every send (recipient, status, and timestamps for delivery, bounces or failures) appears on the Email History card at the top of the Attachments tab. If the sender identity used for the email (company name, reply-to address, logo) can’t be loaded, the Send to manufacturer button stays visible but disabled, with a note explaining why; reload the page to try again. ## Undoing a send If a manufacturing order was moved to In Progress by an email send and no production has been recorded against it yet, you can roll it back to Draft. This is offered wherever the send happened, and the confirmation is explicit that it can’t recall the email itself, only reset the order’s status so you can make changes and send again. Rolling back is blocked once any production has actually been recorded against the build. ## CSV / XLSX exports A manufacturing order can be exported at three levels of detail: Export One row per Where to get it Items item being built Export… on the order’s Actions menu Materials material required for the build Export… on the order’s Actions menu Manufacturing order manufacturing order (summary) Export… on the order’s Actions menu, or the list page’s bulk export Each export is template-driven; pick which columns to include and in what order at [Settings → Manufacturing Orders → Export] (/features/supply-orders/manufacturing-orders/settings/#export-templates). As with the PDF, checking “Attach to my documents” during export also saves a copy to the Attachments tab. ## Bulk-exporting from the list page The manufacturing orders list has a selection column and an Export button. Select individual orders (selections carry across pages), the current page, or every order matching your current filters, then export: - Items: one row per item across all the selected orders. - Manufacturing order: one summary row per selected order. The materials grain isn’t available in bulk; it’s a detail-page export only, since “one row per material across many orders” is closer to a reporting question than a bulk download. ## Finished-goods labels Print labels, on the order’s Actions menu under Export & tools, opens the same label printing dialog used elsewhere in Logistified, pre-loaded with the items this run is producing (not its materials). Quantity presets let you set the label count to each item’s target or to what’s actually been built so far. Printed label sheets are saved to the Attachments tab as Labels. See [Printing Studio] (/features/inventory/printing-studio/) for how label templates and designer-mode printing work generally. ## See also - [Manufacturing orders overview] (/features/supply-orders/manufacturing-orders/overview/) - [The build card] (/features/supply-orders/manufacturing-orders/the-build-card/): where the export, email and label actions live on the detail page. - [Subcontracting a build] (/features/supply-orders/manufacturing-orders/subcontracting/): the rest of the manufacturer workflow around the email. - [Settings → Manufacturing Orders] (/features/supply-orders/manufacturing-orders/settings/) - [Purchase orders → Documents] (/features/supply-orders/purchase-orders/documents/) and [Exports] (/features/supply-orders/purchase-orders/exports/): the equivalent surfaces on a purchase order. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/supply-orders/manufacturing-orders/settings/ # Manufacturing order settings Export templates and the manufacturer email template for manufacturing orders, where they live and what they control. In Logistified, manufacturing order settings live at Settings → Manufacturing Orders, with two tabs: Export and Email. Both are Elevate-plan features. ## On this page - Where these settings are opened from - Export templates - Email template - What isn’t here ## Where these settings are opened from You can navigate here directly from Settings, or Logistified deep-links you straight to the relevant tab: the Export… dialog on a manufacturing order links to the Export tab if you choose to manage templates, and Send to Manufacturer links to the Email tab the same way. ## Export templates The Export tab has four template cards, one per document a manufacturing order can produce: - PDF: the production document. Controls which columns appear for items and materials, and lets you switch off the Built quantity, the Remaining quantity, the build details block, the manufacturing notes, and the materials table independently; each is on by default. - Items XLSX/CSV: one row per item being built. - Materials XLSX/CSV: one row per material requirement. - Manufacturing Order Level XLSX/CSV: one summary row per order, used by both the detail-page export and the list page’s bulk export. Each card works like other template editors in Logistified: create a new template, choose which columns to include and in what order, and set one as the default used by quick exports. Manufacturing orders don’t carry cost data, so there’s no price-related toggle or date-mapping card here; unlike purchase orders, they only have one set of dates (created, expected completion) with nothing to map. ## Email template The Email tab holds the template used when you send a production order to a subcontractor. The default is named “Standard Production Order” and greets the manufacturer directly rather than a generic “Team”. Available placeholders you can drop into the subject or body: Placeholder Fills in {MO_NUMBER} The manufacturing order’s number {MANUFACTURER_NAME} The subcontractor’s name {MANUFACTURER_CONTACT_PERSON} The subcontractor’s contact person {EXPECTED_COMPLETION_DATE} The build’s expected completion date {ITEMS_COUNT} How many items are on the build {TARGET_QUANTITY} The build’s total target quantity {REPLY_TO_EMAIL} Your reply-to address {PHONE_NUMBER} Your phone number {COMPANY_NAME} Your company name A placeholder that’s misspelled is left as-is in the preview rather than silently disappearing, so a typo is easy to spot before sending. If you haven’t set a phone number in your sender details, the default “If you have any queries…please call us at …” line is left out of the email; text you wrote yourself around {PHONE_NUMBER} is kept. Note The sender identity used for manufacturer emails (company name, sender address, reply-to, logo) is shared with every other document type and configured once at Settings → Purchase Orders. It isn’t duplicated here. ## What isn’t here - Sender identity: see Settings → Purchase Orders, shared across all document types. - Document types for uploads: the tags offered when uploading a file to a manufacturing order’s Attachments tab are the same shared list used by purchase orders, transfers and return orders. ## See also - [Documents, exports & manufacturer email] (/features/supply-orders/manufacturing-orders/documents-and-exports/): using these templates day to day. - [Purchase orders → Settings] (/features/supply-orders/purchase-orders/settings/): sender identity and document tags. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/accounting/overview/ # Accounting integration Connect Xero to Logistified so supplier bills for your purchase orders flow into your books automatically. Logistified connects to Xero so the supplier bills behind your purchasing land in your accounting system without re-typing. The integration is part of the [Elevate] (/reference/glossary/#elevate-plan) plan; shops on a lower plan see an upgrade prompt in Settings → Accounting. ## On this page - What syncs - Where you’ll see it in the app - In this section - See also ## What syncs In Logistified In Xero A purchase order A supplier bill (ACCPAY), created and updated according to your sync mode and lifecycle mapping A supplier A Xero contact, linked so bills post to the right record A variant A Xero item, linked automatically or by hand; optionally its purchase cost follows your purchase orders Not applicable Tax rates, imported into Logistified so bill lines carry the right tax Two things also flow back from Xero: - Paid status. When a bill is fully paid in Xero, Logistified marks the purchase order as paid. - Contacts and accounts. Supplier contacts, the chart of accounts, and tax rates are read from Xero so you can pick them in Logistified. ## Where you’ll see it in the app - Settings → Accounting: connect or disconnect organisations, choose the bill creation mode, and set the lifecycle mapping and default accounts. Full reference: [Settings → Accounting] (/features/settings/accounting/). - Each purchase order: an Accounting card on the order’s detail page shows the sync state and offers the manual push and connect actions. Full reference: [Purchase Orders → Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/). - Each supplier: an accounting-contact link so bills post to the right Xero contact. Full reference: [Suppliers → Accounting contacts] (/features/suppliers/accounting-contacts/). - Settings → Accounting → Items: link variants to Xero items and choose whether purchase orders update the items’ purchase cost. Full reference: [Xero items and purchase cost] (/features/accounting/xero-items/). Tip New to the integration? Start with the step-by-step guide: [Set up Xero accounting] (/guides/set-up-xero-accounting/). ## In this section - [How bill sync works] (/features/accounting/how-bill-sync-works/): what’s in the bill, when pushes happen, what a push updates, what it never touches, and how paid bills are protected. Read this if you’re wondering “will Logistified overwrite my bill?” - [Connecting existing bills] (/features/accounting/connect-existing-bills/): link purchase orders to bills that already exist in Xero, one at a time or in bulk, so future pushes update them instead of creating duplicates. - [Xero items and purchase cost] (/features/accounting/xero-items/): link your variants to Xero items (exact SKU matches link themselves), keep the list current with a nightly sync or Sync items now, and send your purchase order costs to each item’s purchase cost in Xero. ## See also - [Set up Xero accounting] (/guides/set-up-xero-accounting/): the end-to-end setup walkthrough. - [Settings → Accounting] (/features/settings/accounting/): connection management, bill modes, lifecycle mapping, and account pickers. - [Settings → Tax rates] (/features/settings/tax-rates/): importing tax rates from Xero. - [Purchase Orders → Payments] (/features/supply-orders/purchase-orders/payments/): how payments recorded in Logistified relate to the bill. Last updated: 31 October 2026 --- Source: https://docs.logistified.app/features/accounting/how-bill-sync-works/ # How bill sync works What a purchase order's bill contains, when Logistified creates or updates it, what a push overwrites in Xero, and what it never touches. Every Logistified purchase order can sync to exactly one bill in Xero. This page explains what that bill contains, when it gets created or updated, and (most importantly) what happens when the order and the bill disagree: what a push overwrites, what it leaves alone, and how payments and paid bills are protected. ## On this page - One order, one bill - What the bill contains - When bills are created and updated - What a push updates and what it never touches - If you edit the bill in Xero - Paid bills are final, and paid status flows back - See also ## One order, one bill A purchase order is linked to at most one bill, and pushing never creates a second one: - The first push creates the bill (or, if a bill with the same bill number already exists in Xero, you get an error suggesting Connect existing bill instead, never a silent duplicate). - Every later push updates that same bill in place. - Re-pushing an unchanged order does nothing; a toast confirms “Already in sync.” This also answers a common worry: if the order’s line items no longer match the bill’s, Logistified does not create a new draft bill on the side. The difference shows on the order’s Accounting card as “Local changes not yet pushed”, and the next push brings the existing bill back in line with the order. ## What the bill contains A push writes the order’s current state into the bill: - Bill number: the purchase order’s number. - Contact: the supplier’s linked Xero contact. If the supplier isn’t linked yet, the first push looks for a Xero contact with the exact same name and links it, or creates a new contact if none exists (see [Accounting contacts] (/features/suppliers/accounting-contacts/)). - Bill date and due date: the bill date is the order’s received date, falling back to the date of the push when the order hasn’t been received yet. The due date is that date plus the order’s payment terms (the supplier’s when the order has none), and the payment terms set on the Xero contact win over both when they exist. - Currency: the supplier’s currency; all lines on one bill share it. - Line items: one line per order line, at its unit cost and for the ordered quantity minus anything cancelled (a line with nothing left on it is left off the bill entirely, and an order where every line is cancelled can’t be billed at all), plus a shipping line when the order has a shipping cost, and one line per [additional cost or discount entry] (/features/supply-orders/purchase-orders/additional-costs/) with a non-zero amount (using the entry’s reason as its description (or “Additional cost” / “Discount” when the reason is blank) and carrying the entry’s own purchase tax when one’s configured) posted to the accounts you chose in [Settings → Accounting] (/features/settings/accounting/#accounts). - Bill status: Draft, Submitted for approval, or Authorised, resolved from your [lifecycle mapping] (/features/settings/accounting/#lifecycle-mapping) at the order’s current stage. The status Logistified sends only ever moves forward, never backwards; every push is clamped to at least the status Logistified last sent (see [If you edit the bill in Xero] (#if-you-edit-the-bill-in-xero)). ## When bills are created and updated The [bill creation mode] (/features/settings/accounting/#bill-creation-mode) decides when pushes happen: Mode Bill created Bill updated Manual Only when you push from the order Only when you push Automatic creation Automatically, once, when the order reaches the stage you chose Only when you push: the bill is never touched again automatically Full auto Automatically per the lifecycle mapping Automatically, whenever the order changes Two things never trigger a push on their own: edits made in Xero (Logistified doesn’t react to them), and putting the order On Hold, into Dispute, or Cancelled (automatic pushes stop for such orders; a manual push still works). [anchor: what-a-push-updates--and-what-it-never-touches] ## What a push updates and what it never touches When a push runs, it makes the bill match the order. Concretely: A push rewrites: the bill number, contact, dates, currency, the full set of line items, and (forward only) the bill status. A push never touches: payments recorded on the bill, credit-note allocations, attachments, or anything else you’ve added in Xero that isn’t in the list above. Payments in particular live entirely outside the bill’s content; no push can remove or alter one. Caution The purchase order is the source of truth for the bill’s contents. If someone hand-edits the bill’s dates or line items in Xero, those edits survive only until the next push; then they’re replaced with the order’s version. If you want Xero to be where bills get edited after creation, use Manual or Automatic creation mode, where Logistified never updates a bill without you asking. ## If you edit the bill in Xero - Nothing happens immediately. Xero-side edits don’t trigger any reaction, and the “Local changes not yet pushed” indicator only tracks changes to the order in Logistified; it won’t light up because the bill changed in Xero. - The next push replaces the bill’s dates and line items with the order’s version, as described above. - A push never sends a status earlier than the one Logistified last sent. Logistified remembers the bill status it pushed and clamps every later push to at least that. What it does not track is a status change you make in Xero yourself; if you approve a bill Logistified pushed as a draft, a later push still sends the status the lifecycle mapping resolves to. If a stage should always be approved, set that in the [lifecycle mapping] (/features/settings/accounting/#lifecycle-mapping) rather than by hand in Xero. (Bills brought in with Connect existing bill are the exception: they record the status they were connected at, so they’re never pushed below it.) - Some bills refuse changes entirely. A bill that Xero considers final (fully paid, approved for payment, or in a locked accounting period) is left alone. The push doesn’t force anything and the order’s Accounting card explains why later changes stay in Logistified only. [anchor: paid-bills-are-final--and-paid-status-flows-back] ## Paid bills are final, and paid status flows back When Xero shows the bill fully paid: - Logistified marks the purchase order as paid. - From then on, no push ever touches that bill again, not automatically and not manually. The card reports “The bill is fully paid.” Partially paid bills follow Xero’s own rules: if Xero declines the change, nothing is modified and the card tells you. ## See also - [Accounting overview] (/features/accounting/overview/): everything the integration syncs. - [Connecting existing bills] (/features/accounting/connect-existing-bills/): link orders to bills that already exist in Xero. - [Purchase Orders → Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/): the per-order card, its statuses, and error messages. - [Settings → Accounting] (/features/settings/accounting/): modes, lifecycle mapping, and account pickers. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/accounting/connect-existing-bills/ # Connecting existing bills Link purchase orders to bills that already exist in Xero (one at a time or in bulk) so pushes update them instead of creating duplicates. If you were already creating supplier bills in Xero before connecting Logistified, those bills and your purchase orders don’t know about each other yet. Connecting links a purchase order to its existing bill so future pushes update that bill instead of creating a duplicate. You can connect one order at a time from its Accounting card, or many at once from Settings. ## On this page - What connecting does (and doesn’t do) - Connecting one bill from a purchase order - The first push makes the bill match the order - Connecting in bulk from Settings - Rules and limits - See also ## What connecting does (and doesn’t do) Connecting is link-only: - Nothing is written to Xero. The bill is not modified in any way at the moment you connect it. - The order’s Accounting card switches to “Connected: not yet updated” and its action button becomes Update Bill. - If the bill is already fully paid in Xero, the purchase order is immediately marked as paid. - If the supplier isn’t linked to the bill’s Xero contact yet, the connect dialog offers a checkbox (“Also link [supplier] to [contact]”), so the supplier and contact get linked in the same step. ## Connecting one bill from a purchase order On the order’s detail page, open the Accounting card and click Connect existing bill. A picker dialog opens showing recent bills from the connected organisation: Draft, Submitted, Authorised, and Paid bills; voided bills can’t be connected. Search by bill number, reference, or contact name; each row shows the contact, date, total, and how much is still owed on partially paid bills. Pick the bill and click Connect bill. The bill must be in the same currency as the supplier; a mismatch blocks the connection, since the order’s lines could never post correctly onto that bill. ## The first push makes the bill match the order Connecting doesn’t reconcile any differences between the order and the bill; it only creates the link. The first time you click Update Bill afterwards, the bill’s contents are replaced with the order’s version, exactly as described in [How bill sync works] (/features/accounting/how-bill-sync-works/#what-a-push-updates--and-what-it-never-touches), including renaming the bill’s number to the purchase order’s number. Payments and credit allocations on the bill are untouched, as always. Caution If the existing bill’s line items differ from the order’s, don’t push until you’re happy for the order’s version to win. Until you push, the bill stays exactly as it is in Xero. ## Connecting in bulk from Settings Open Settings → Accounting → General. Once at least one organisation is connected, a Connect existing bills card appears; click Find matching bills on the organisation you want to scan. The review dialog pairs bills with purchase orders automatically when the bill number exactly matches the order number, and lets you pair the rest by hand: - A summary line shows how many bills were checked, how many were already connected, how many had no matching order, and how many had ambiguous numbers (the same bill number appears more than once in Xero; those are never auto-paired; use manual mapping). - Pairs whose currency doesn’t match the supplier’s are shown but can’t be selected. - A Manual mapping section lists unmatched orders with a bill picker on each row, for bills whose numbers don’t line up with order numbers. - Click Connect N bills to apply. Each pair goes through the same validation as the single-order action, and a results summary shows what connected and what failed, with reasons. ## Rules and limits - One bill per order, one order per bill. A bill that’s already connected to another purchase order can’t be connected again. - Voided bills can’t be connected. - Currencies must match between the bill and the supplier. - Bulk matching scans the newest bills first; very old bills may need the single-order dialog instead. ## See also - [How bill sync works] (/features/accounting/how-bill-sync-works/): what a push overwrites once a bill is connected. - [Purchase Orders → Accounting sync] (/features/supply-orders/purchase-orders/accounting-sync/): the Accounting card the connect action lives on. - [Suppliers → Accounting contacts] (/features/suppliers/accounting-contacts/): the supplier↔contact link the connect dialog can create for you. Last updated: 21 July 2026 --- Source: https://docs.logistified.app/features/accounting/xero-items/ # Xero items and purchase cost Link your Shopify variants to Xero items, keep the link list up to date automatically, and send the cost from your purchase orders to each item's purchase cost in Xero. Logistified can link each of your Shopify variants to its item in Xero. Once they are linked, Logistified can keep each Xero item’s purchase cost in step with your purchase orders, so the cost in Xero doesn’t go stale. Everything lives on Settings → Accounting → Items. It’s part of the [Elevate] (/reference/glossary/#elevate-plan) plan. ## On this page - Turning on item sync - The Items page - Automatic matching - Linking and unlinking by hand - Sync items now - Checking linked items - Sending purchase order costs to Xero - Update Xero in Update Unit Cost - Known limits - See also ## Turning on item sync Open Settings → Accounting and click Items. If you have more than one Xero organisation connected, pick the one you want to work with. Nothing happens until you click Turn on item sync. When you turn it on, Logistified imports your Xero items once. A progress line shows how far it has got, for example 120 of 400 items imported. A large catalogue can take a while; you can leave the page and come back. After that first import, Logistified picks up new and changed items every night, so it never has to read your whole catalogue again. Turning on item sync writes nothing to Xero. It only reads your items so you can link them. Note If the import stops before it finishes (for example because Xero asked Logistified to slow down, or your connection needs re-authorizing), the status line says so and Sync items now continues it where it stopped. ## The Items page The page lists your variants with the Xero item each one is linked to. Search by SKU, product, variant, item code or item name, and filter by link status (you can save a filter as a preset): Link status What it means Linked (auto) Logistified linked the variant itself, because its SKU exactly matches one Xero item code Linked (manual) You linked it by hand Unlinked Not linked to any item Blocked from auto-link You unlinked it by hand, so Logistified won’t link it automatically again Conflict More than one variant or more than one Xero item has this SKU or code; link the right one by hand Missing in Xero The linked item no longer exists in Xero; link another item Each linked row also shows the item’s code and name, whether it is tracked as inventory in Xero, when Logistified last checked it, and (once costs are being sent) the last cost sent, for example £12.40 from PO #1042 (Copy from Shopify). If a cost can’t be sent to that item, the row says why and offers the one thing that fixes it. ## Automatic matching A variant links itself when its SKU and a Xero item’s code are exactly the same, including capital letters and leading zeros, and the match is unique on both sides: no other variant has that SKU, no other Xero item has that code, and neither is already linked. Anything less certain is shown as a Conflict instead of guessed. Matching runs after the first import and every time new or changed items come in from Xero. A product you add to Shopify later is matched the next time items sync (at the latest the next night). ## Linking and unlinking by hand - Link: on a row, pick an item from the item list (search by code or name). Items that are tracked in Xero or already linked to another variant are labelled. A Xero item can be linked to only one variant at a time. - Unlink: removes the link. The variant then shows Blocked from auto-link: Logistified will never link it automatically again, even to another matching item, until you link it by hand yourself. That way an unlink you made on purpose stays that way. If someone else changed the same link while you had the page open, Logistified asks you to load the latest link instead of overwriting theirs. Linking and unlinking never change anything in Xero. ## Sync items now Sync items now fetches the items created or changed in Xero since the last sync straight away, instead of waiting for the night. Use it after you add or edit many items in Xero. It also sends any item costs that are still waiting. If a sync is already running, clicking again simply waits for that one. Before the first import has finished, the button starts or continues the import instead. The line under the button tells you the state, for example Up to date. Last checked …, Initial import in progress, or that Xero asked Logistified to pause for a while. ## Checking linked items An item you delete in Xero doesn’t disappear from the list on its own: the nightly sync only sees new and changed items, so it can’t tell a deleted item from one that simply didn’t change. To check, click Check linked items above the list. Logistified looks up the linked items on the current page in Xero, and any item that no longer exists shows Missing in Xero, so you can link that variant to another item. Sending a cost to an item also checks it first. If Xero asks Logistified to slow down partway through, the line says how many items were checked so far, and the next click continues with the ones not checked yet instead of starting over. ## Sending purchase order costs to Xero The Item purchase cost card decides whether Logistified updates the purchase cost of your linked Xero items, and from which cost. Save your choice with the save bar. Mode What Xero’s purchase cost gets Off (the default) Nothing is sent. Copy from Shopify The cost your purchase orders set in Shopify, copied to the linked item each time a purchase order updates the Shopify cost. It needs [automatic cost sync] (/features/supply-orders/purchase-orders/preferences/#auto-sync-costs-on-completion) to Shopify turned on, and only items with a Shopify variant are sent. Set new cost The purchase order’s own cost per item, sent when you complete or re-sync the order, or when you choose Update Xero in Update Unit Cost. Choose Direct cost (the order’s unit cost) or Landed cost (the unit cost plus the order’s share of shipping and other costs). It works whether or not Shopify cost sync is on. Caution Edits made in Xero are replaced by the next PO cost. While a cost mode is on, the next purchase order cost for an item overwrites whatever purchase cost the item has in Xero, even if you changed it by hand there, and even if the new cost is the same as the last one sent. Note Reconnect Xero once to send item costs. Xero stores an item’s purchase cost with your organisation settings, so Logistified asks for permission to manage your Xero organisation settings when you connect. If you connected Xero before item cost updates were available, that permission is missing: the card says Reconnect Xero to allow item cost updates., only Off can be chosen, and nothing is sent to your items. Reconnect Xero on Settings → Accounting, then choose a cost mode. Bills keep syncing either way. A few rules apply to both modes: - The latest update wins. Like Set New Price in Shopify, each new cost replaces the previous one, in the order Logistified receives them. Re-syncing an older purchase order after a newer one therefore puts the older order’s cost back. - Set new cost doesn’t wait for receiving. The order’s cost is sent whether or not anything has been received. Undoing a receipt or reopening an order doesn’t change the cost in Xero by itself; the next completion, re-sync or Update Xero sends the order’s cost again. Logistified never reverts a cost in Xero. - Exchange rates. With Set new cost, an order in another currency uses the exchange rate saved on the order, or otherwise the same market rate the order uses for Shopify. If no rate is available, that item isn’t sent and the order tells you to save a rate. Copy from Shopify uses no exchange rate at all; it copies the Shopify cost as it is. - Switching modes discards costs that were waiting to be sent under the old mode. The next purchase order cost under the new mode is sent. - The two modes can send different costs when Shopify and Xero use different cost sources (for example landed cost in Xero, direct cost in Shopify). Each row shows which mode sent its last cost. When you complete or re-sync an order in Set new cost mode, the confirmation says how many Xero item costs are being updated, and lists any item that couldn’t be sent with the reason. A Xero problem never undoes the completion. ## Update Xero in Update Unit Cost When Set new cost is selected, the purchase order’s Actions → Update Unit Cost dialog offers a third choice under Update, next to the Shopify and supplier costs: Xero item cost. It sends this order’s direct or landed cost per item (whichever the Item purchase cost card says) to the linked Xero items of the rows you selected, whether or not anything was received. Costs you type into the dialog’s PO cost column don’t change what Xero receives; Xero always gets the order’s own cost. The confirm step lists the Xero item cost, and the result says how many Xero item costs are being updated. With Off or Copy from Shopify selected, the choice isn’t shown. See [Update Unit Cost] (/features/supply-orders/purchase-orders/preferences/#update-unit-cost). ## Known limits - Tracked items. Logistified doesn’t change the cost of a Xero item that is tracked as inventory, because Xero values tracked stock itself. Such items can be linked, but their row explains that the cost isn’t sent. Link an untracked item instead. - Items that aren’t purchased. An item not set up as a purchased item in Xero has no purchase cost to update. Mark it as purchased in Xero, then Sync items now; the waiting cost is sent. - Sub-assemblies and virtual materials. Costs of Assemblified sub-assemblies (SKUs starting with ASM-) are managed by Assemblified and are never sent. Virtual materials and other lines without a Shopify product aren’t sent either. - Base currency must match. Xero item costs are sent only in your Xero organisation’s base currency. If it differs from your shop’s currency, every linked row shows that the cost wasn’t sent. - One shop per Xero organisation. A Xero organisation can be connected to one Logistified shop only. Connecting it from a second shop shows Xero organisation already connected; disconnect it from the other shop first. If an organisation was already shared by two shops before this rule, item sync stays off for it and the Items page asks you to contact Logistified support for a review. - Not synced: stock quantities and valuation, item names and sales prices, and item codes on bills. Logistified never creates or deletes Xero items. ## See also - [Accounting integration] (/features/accounting/overview/): what else syncs with Xero. - [Settings → Accounting] (/features/settings/accounting/): connecting Xero and the bill settings. - [Purchase Orders → Preferences] (/features/supply-orders/purchase-orders/preferences/#auto-sync-costs-on-completion): automatic cost sync to Shopify, which Copy from Shopify follows. - [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/): how sub-assembly costs are handled. Last updated: 1 November 2026 --- Source: https://docs.logistified.app/features/reporting/overview/ # Reporting (Beta) Build your own table or chart from any part of your Logistified data: group it, filter it, edit prices right in the grid, and export it. Reporting (top nav → Reporting (Beta)) is a self-serve table and chart builder over your Logistified data, products, stock, purchase orders, and orders. Pick a report, filter and group it the way you want, and export the result. It’s different from [Reports] (/features/reports/overview/), which are scheduled emails: Reporting is the page you open and work in right now. Note Reporting is in beta; the report list and columns are still growing. ## On this page - What Reporting shows - What you can do here - Where to next ## What Reporting shows Opening Reporting shows a hub of report cards: one per report type, covering products, stock on hand, low stock, ABC analysis, best/worst sellers, sale items, purchase orders and purchase order items, stock-take discrepancies, and stock held at your suppliers, plus scorecards for orders and profit. Click a card to open that report as a table (or, on the scorecards, a set of summary tiles). Note ABC analysis counts inventory-tracked variants only by default, so its totals won’t match a count of every variant. Turn Tracked only off in the toolbar to include untracked stock. Note On Stock at Supplier, a variant linked to more than one supplier has its sales and stock figures repeated on every supplier’s row; grouping by supplier gives an accurate per-supplier picture, but adding those numbers up across suppliers overcounts against your shop total. The supplier credit balance column shows blank rather than zero when a supplier’s credits span more than one currency; see [Supplier credits] (/features/suppliers/credits/) for why. Note On SKU / Variant and Products, a Sales channels control in the toolbar lets you narrow the sales columns to specific channels: Online Store, Point of Sale, and so on, plus an “(unknown channel)” option for orders that don’t carry one. It doesn’t hide any rows: every product or variant still shows, but revenue, units sold, and the other sales-based columns only count orders from the channels you picked. Stock, on order, and receipt columns are unaffected. Inside a report you get: - Filters: narrow the rows before totals, tiles, and exports are calculated. - Group by: collapse rows into totals by a dimension (for example, by supplier or vendor), or show one row per record. - Columns: choose which columns are visible and in what order, from the Columns popover. - Date range: on reports that offer it, a picker with Yesterday, Last 7 days, Last 30 days, Last 90 days, Last 365 days, and Custom range. The timezone shown beside the picker is your Shopify store timezone. Rolling presets are inclusive calendar days ending on your store’s today; Yesterday is the immediately preceding store date. Custom endpoints are inclusive too, and selecting one day takes two clicks on that same date. - Locations: see below. - Table or chart view: the same data as a table or a chart, where the report supports it. - Views: save your filter, group, column, and sort combination as a view so it comes back next time. Built-in views ship with each report; save your own alongside them. Note If Logistified is temporarily using your last known Shopify store timezone, a notice appears below the timezone label. If that value is no longer recent enough, the report shows a retry message instead of silently switching its date range to UTC. This timezone applies to the date-range filter; time-based grouping, such as order day or month, still uses UTC. ### Scoping a report to locations Where a report supports it, a Locations control in the toolbar limits the report to the locations you tick. The button reads All locations until you pick some, then the location’s name (or “3 locations”); Clear (all locations) at the bottom of the list resets it. The scope covers stock, incoming, and reorder-point columns and the sales columns: units sold, revenue, refunds, cancellations, the fixed 3-month and 12-month windows, and the unfulfilled backlog. Sales are attributed by the location an order line was fulfilled from. Caution A sale that carries no fulfillment location (an order that was never fulfilled from a location, for instance) counts towards no location at all. So the per-location sales figures won’t necessarily add up to the shop-wide figure you see with All locations selected. Compare like with like: read a location-scoped report on its own terms rather than as a slice of the total. ### Filtering by ID The Shopify ID and Product ID filters (and, on the Purchase order items report, Variant ID) take a whole list at once instead of a single value. Opening one gives three tabs: - Include: paste IDs into the box (Paste IDs: comma, space or newline separated), then click Add N IDs. Each one lands as its own removable entry; Clear included empties the side. - Exclude: the same, for IDs you want left out. - Equals: Enter one ID… for a single exact match. Full Shopify IDs such as gid://shopify/ProductVariant/1234567890 are accepted and reduced to the plain number for you, and duplicates in what you paste are dropped. The whole list is applied once when you close the filter, so pasting 300 IDs costs one refresh, not 300, and the collapsed filter chip reads, for example, “Shopify ID: 300 included”. Substring matching (“contains”, “starts with”) isn’t offered on ID columns, because IDs are system-generated and partial matches are never what you want. Note The Purchase orders and Purchase order items reports show a single Delivery date column by default: the requested delivery date when one has been set, falling back to the expected delivery date. On the line-items report a line’s own requested date wins over the order’s. The raw Expected delivery and Requested delivery dates are still available as separate columns from the Columns popover. Note Filtering by Supplier works in two directions: including a supplier shows only the variants it supplies, using that supplier’s values; excluding one removes every variant it supplies. Excluding the [Default supplier] (/reference/glossary/#default-supplier) removes every variant that doesn’t have a real supplier assigned, since the Default supplier is attached to all of them. Note On Purchase orders and Purchase order items, a Total row sits just under the column headers and sums the money and quantity columns for every row that matches your filters, not just the page in front of you. It fills in a moment after the rest of the table, and hovering it shows how many filtered records it’s totalling. If the matching rows span more than one currency, the money total shows a dash instead of adding unlike currencies together; hover the dash for why, or filter by Currency to get a number. The row only appears when at least one of its columns is visible and there’s at least one matching row. The Purchase order items report also shows a Line total column by default now, since it’s the column the row is built to sum. ### PO numbers and SKUs in grouped reports On Purchase order items, add PO number or SKU from Columns to see the values contributing to each group. One distinct value appears normally. If there are several, the cell shows Multiple: hover over it or focus it with the keyboard to see every value. Press Down Arrow to move into the list and scroll with the keyboard. Shift+Tab returns to the cell; Escape closes the list. The list scrolls so the table rows stay compact. ## What you can do here [Editing prices in a report] (/features/reporting/price-editing/) Click a Price or Compare-at price cell in a report to update it in Shopify directly. [Margins and cost basis] (/features/reporting/margins-and-cost-basis/) What Margin %, Markup %, and Gross profit mean, and which cost they're measured against. [Exporting a report as PDF] (/features/reporting/pdf-export/) A printable A4 document of the report on screen, with a warning when the table is too wide for the page. Beyond that, every report supports: - Export: download the current view as CSV, XLSX or a printable [PDF] (/features/reporting/pdf-export/), or export just the rows you’ve selected. - Saving a view: fork a built-in view into one of your own, or save changes to a view you already own. CSV, XLSX and PDF exports include all the grouped PO numbers and SKUs. They export the full values rather than the word “Multiple”. If a value is too long for an XLSX cell, the export shows an error instead of cutting it off. Choose CSV, or turn on Flatten to item rows to export separate line items. A single item whose text is still too long will also need CSV. ## Where to next - [Reports] (/features/reports/overview/): scheduled email delivery of a saved view, on a recurring cadence. - [Line-item column views] (/features/supply-orders/line-item-views/): the equivalent saved-column-view idea, applied to a single order’s line-item table. Last updated: 15 October 2026 --- Source: https://docs.logistified.app/features/reporting/price-editing/ # Editing prices in a report Click a Price or Compare-at price cell in a report to update it in Shopify directly, no need to leave the page. On Logistified reports that show variants (Products, SKU / Variant, Stock on hand, Low stock, ABC analysis, Best sellers, and Sale items), the Price and Compare-at price columns are live values from Shopify, and you can edit them right in the table. It’s the same editing experience as on a purchase order, transfer order, return, or supplier stock release line-item table. Caution These edits change your storefront. A confirmed price is written to Shopify immediately and is visible to customers straight away. ## On this page - Editing a price - Clearing a compare-at price - Editing many rows at once - When a row can’t be edited - What updates right away, and what doesn’t - Exporting after an edit - See also ## Editing a price Add the Price and/or Compare-at price column from the Columns popover if it isn’t already on screen. Click a price cell, type the new amount, and press Enter; Escape cancels. Before anything is written, Logistified asks “Change the live price?” and shows the old value next to the new one. Confirm with Update price. A Don’t ask again this session checkbox skips the confirmation for the rest of your session; closing the tab brings it back. ## Clearing a compare-at price Leave the Compare-at price cell empty and confirm; that removes the compare-at price on the variant, which removes the “was” price from your storefront. The retail price can’t be cleared the same way; emptying that cell just cancels the edit. ## Editing many rows at once Select rows in the report and choose Bulk edit prices… to change several variants in one go. The dialog lists every selected row with its own Price and Compare-at price fields, alongside the resulting Margin, Markup and Gross profit per unit so you can check each new price before saving. - Type per row. Enter a new price on any row; rows you leave alone stay unchanged and show “Will change” only when something differs. - Change all rows (optional). Tick a field under Change all rows to apply one rule to every row you haven’t typed into. A price you typed on a row always wins over the rule for that row and field, and Undo on a row hands it back to the rule. - Clearing a compare-at price. Empty a row’s compare-at field to remove it from that variant. - Prices that can’t be saved. If any typed price is unusable, the dialog says how many prices need fixing and holds the whole update back until they’re corrected. Nothing is skipped silently. - Below cost. A price under the variant’s cost is flagged on its row. Nothing is written until you confirm Update N variants, and all changes are saved in one run. Closing the dialog with typed prices asks first, with Keep editing to go back. ## When a row can’t be edited A greyed-out price cell explains itself on hover, keyboard focus, or tap: What you see Why “This row has no Shopify product.” The row isn’t linked to a product in Shopify. “Shopify returned no live price for this variant…” Usually a deleted variant. “Prices could not be checked against Shopify…” The live price check failed; use the Retry offered on the banner. Rows in a grouped view (totals by supplier, vendor, and so on) are never editable; a total isn’t one variant, so there’s nothing single to write to. Expand a group to see and edit its individual rows. ## What updates right away, and what doesn’t The cell you edited shows its new value immediately. Everything calculated from it on the rest of the table (Margin, Markup, Gross profit, totals, and the row’s position if you’re sorted by price) stays at its pre-edit value until you ask the page to catch up. Logistified shows a banner after a commit: “Prices updated: the rest of this table has not caught up.” Click Refresh to re-run the report and bring everything current. Refreshing is a deliberate action rather than automatic, so an edit never silently reshuffles the rows you’re looking at mid-review. ## Exporting after an edit An export (CSV, XLSX or [PDF] (/features/reporting/pdf-export/)) always re-runs the report against current data, so a file you download after an edit already reflects the new price and the recalculated Margin / Markup / Gross profit; you don’t need to hit Refresh first. Export is temporarily unavailable while a price save is in progress. ## See also - [Editing retail prices] (/features/supply-orders/editing-prices/): the same editing behavior on a supply order’s line-item table. - [Margins and cost basis] (/features/reporting/margins-and-cost-basis/): what the Margin, Markup, and Gross profit columns mean. - [Reporting] (/features/reporting/overview/): grouping, filters, columns, and export. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reporting/margins-and-cost-basis/ # Margins and cost basis What Margin %, Markup %, and Gross profit mean on a report, and which cost they're measured against. Several Logistified report columns (Margin %, Markup %, Gross profit / unit, Gross profit (stock), and Stock cost) depend on which cost you’re comparing a variant’s price against. Reports that show them let you choose the cost, and name it right in the column so you always know which number you’re looking at. ## On this page - Choosing the cost basis - What each column means - Tax-exclusive retail prices - A cost of zero - Reading the numbers on a grouped row - See also ## Choosing the cost basis On reports where it applies (Products, Low stock, ABC analysis, Stock on hand), a Cost basis control sits in the toolbar with two options: Option What it reads Shopify cost The cost per item stored on the Shopify variant, the Cost price value. Supplier cost The primary supplier’s mapped cost for the variant. A variant with no supplier link shows a dash. Switching the basis rewrites every margin, markup, gross-profit, and stock-value number on screen. To make that unmissable, the affected column headers name the basis in use (for example Margin % (Supplier cost)), so the header and the numbers underneath it always agree, in the table, in an export, and on a scheduled report’s CSV. ## What each column means - Margin %: (price − cost) ÷ price × 100 - Markup %: (price − cost) ÷ cost × 100 - Gross profit / unit: price − cost, per unit - Gross profit (stock): available quantity × (price − cost), for everything currently on hand - Stock cost: available quantity × cost Hover any of these cells to see the exact formula and the operands it used, unrounded. ## Tax-exclusive retail prices If your retail prices include tax (VAT, GST, or sales tax), the raw price-versus-cost comparison overstates every margin; the price is gross while the cost is net. An optional shop-level setting under [Settings → Tax rates] (/features/settings/tax-rates/) (“Margins use tax-exclusive retail prices”, with the tax percentage included in your prices) makes Margin %, Markup %, and the Gross profit columns divide the price by 1 + rate/100 before comparing. When that setting is on, the affected column headers add an “excl. tax” suffix on top of the cost-basis name (for example Margin % (Supplier cost, excl. tax)) in the table, in exports, and on a scheduled report’s CSV, so the header always states both the cost and the price flavour behind the number. Cost-only columns such as Stock cost read no price and keep their plain basis label. ## A cost of zero If a variant’s cost reads as zero (commonly because a cost wasn’t imported for it), the margin family treats that as free goods: a 100% margin, with the full retail price counted as profit. That’s mathematically correct given a zero cost, but it’s worth checking whether the zero is real or just a gap in your cost data before trusting the number. ## Reading the numbers on a grouped row Group a report by a dimension (supplier, vendor, and so on) and the margin-family columns still show, but as a rollup of the rows in that group: an average for Margin %, Markup %, and Gross profit / unit, and a sum for Gross profit (stock) and Stock cost. Hover a grouped cell to see which of the two it is. ## See also - [Editing prices in a report] (/features/reporting/price-editing/): changing the Price or Compare-at price a margin is calculated against. - [Reporting] (/features/reporting/overview/): grouping, filters, columns, and export. - [Settings → Tax rates] (/features/settings/tax-rates/): the “Margins use tax-exclusive retail prices” setting. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reporting/stock-on-hand-assemblified/ # Stock on hand with Assemblified How the Stock on hand report values bills of materials and sub-assemblies when Assemblified is connected. When your store is connected to Assemblified, Logistified’s Stock on hand report values the items Assemblified builds, not just the products Shopify tracks. This page explains the extra columns, how bills of materials are counted, and the note you’ll see on exports. ## On this page - What changes on the report - Extra columns - How the data is kept current - The “as of” note on exports - Sub-assemblies on documents ## What changes on the report For a bill of materials (BOM) that Assemblified tracks, the report counts what is actually on the shelf rather than the capacity figure Shopify publishes. On hand, On hand cost and On hand retail therefore reflect real built stock. If you’re not connected to Assemblified, nothing changes: the report behaves as before and never contacts Assemblified. Logistified treats your store as connected once Assemblified has sent it anything: a virtual material, a sub-assembly or an order. ## Extra columns Column What it shows Item kind Whether the row is a Shopify product, a virtual material, a sub-assembly, or a bill of materials. Published quantity The available number Shopify shows for a bill of materials. Labour cost Labour cost per unit, from Assemblified. On hand labour value On hand × labour cost. On hand value with labour On hand × (cost + labour). On hand total value On hand × (cost + labour + overhead). In production Work in progress. It is kept separate and never counted as on hand. Blank when grouped by location (it has no location). Awaiting quality check Built units waiting on a quality check. Blank when grouped by location. Cost source Whether the unit cost came from Assemblified or from your chosen [cost basis] (/features/reporting/margins-and-cost-basis/). Cost method For a sub-assembly, the cost method set on it in Assemblified: recipe, built, purchased or moving average (other for a method this version of Logistified does not know yet; its costs are still Assemblified’s). Blank otherwise. These columns are offered in the column picker only when your store is connected to Assemblified. Without Assemblified data the labour columns are blank and the with-labour and total values equal the on hand cost. With Assemblified data, the cost columns and the Total cost tile say which cost they use, for example Current cost (Assemblified cost; else Shopify cost): Assemblified’s cost for the items it tracks, your chosen cost basis for everything else. ## How the data is kept current The report fetches fresh figures from Assemblified when you run it and reuses them for a few minutes. If Assemblified can’t be reached, the report falls back to the last data it received; if that is more than 24 hours old, bills of materials show Shopify quantities and costs instead. The dashboard’s inventory value counts built bills at their shelf quantity and the same unit cost too, and its missing-cost count only lists items it actually valued at zero. ## The “as of” note on exports The report shows when the Assemblified data was captured (for example “Assemblified data as of 2026-10-15 11:00 UTC.”), including whether the last known data was used. The PDF export prints the same note under its title, and a scheduled Stock on hand email says it in the email text. CSV and spreadsheet files stay plain tables with no extra line, so anything that imports them keeps working. ## Sub-assemblies on documents Sub-assembly items (SKUs starting with ASM-) can be purchased, transferred, returned, released and counted like any item. Every stock change a document makes is sent to Assemblified, and the quantity in this report follows when Assemblified confirms it. A sub-assembly’s unit cost comes from Assemblified, which costs it with the cost method set on the sub-assembly (its recipe, its last build, the purchase cost Logistified sends for each purchase order (one price per sub-assembly and order, from the received units), or a moving average of built and bought units), so the report shows Assemblified’s cost for it. See [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/). ## See also - [Reporting] (/features/reporting/overview/) - [Margins and cost basis] (/features/reporting/margins-and-cost-basis/) - [Adding line items to a PO] (/features/supply-orders/purchase-orders/adding-line-items/) - [Sub-assemblies from Assemblified] (/features/supply-orders/assemblified-sub-assemblies/) Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reporting/pdf-export/ # Exporting a report as PDF Download the report you are looking at as a printable A4 PDF, same columns, filters, grouping and totals as on screen, with a warning when the table is too wide for the page. Every Logistified report can be downloaded as a PDF that matches what is on screen: the columns you have shown, in your order, the filters and date range you applied, the grouping, and the summary tiles above the table. The document uses the same layout as your purchase order and transfer order PDFs, with your company logo in the header, so it fits alongside them. ## On this page - Exporting a table report - Choosing the orientation, and the “too wide” warning - What ends up in the PDF - Exporting only selected rows - Exporting a scorecard - Limits ## Exporting a table report Open the report, set it up the way you want it, then click the arrow next to Export CSV and choose Export PDF. A small dialog opens: - Orientation: Auto (the default) picks portrait when everything fits, and landscape otherwise. Choose Portrait or Landscape to override. - Include summary tiles: on reports that show headline tiles above the table, switch them on or off in the PDF. On by default. - Flatten to item rows: on a grouped report only. Off exports the group rows exactly as displayed; on exports the individual items instead. This is the same toggle as in the export menu. Below the options the dialog tells you whether the table fits the page and how many rows the PDF will contain, for example All 312 rows or First 2,000 of 4,210 rows. Click Export PDF to download the file. ## Choosing the orientation, and the “too wide” warning Before anything is generated, Logistified estimates how wide your columns will be from the rows currently on screen and states the result: - Fits on A4 portrait. - Wider than portrait: landscape selected. Auto switched to landscape for you. - Too wide even for landscape. The columns will be squeezed and wrapped to fit the page. The export still works, but the text gets small; consider hiding some columns in the Columns popover first. The warning never blocks the export. Nothing is ever cut off at the page edge: when a table is wider than the page, the columns share the width proportionally and long values wrap onto extra lines. ## What ends up in the PDF - Header: your company logo (if you uploaded one under Settings → Purchase Orders → General), the report name and view name, and the report’s scope as plain lines: date range, locations, sales channels, cost basis, any report-specific options, and the active filters. A Generated line records when the file was made and how many rows it contains. - Summary tiles: the headline figures shown above the table, when included. - The table: the columns in the order shown on screen, with the same number, currency, percentage and date formatting you see in the table. Numbers are right-aligned; columns whose values are approximations carry the same ≈ mark as on screen; column headers name the cost basis where the table does. - Grouped reports: the group label and the item count lead each row, exactly like the grouped table. - Every page repeats the column headers, so a table that runs over several pages stays readable. Image columns are not included in the PDF; the dialog says so when your view contains one. Use CSV or XLSX if you need the image links. ## Exporting only selected rows On reports where rows can be selected, select the rows and choose Actions → Export selected (PDF). The same dialog opens, the file name ends in -selected, and the header notes how many variants were selected. The PDF contains only those rows, regardless of the page you are on. ## Exporting a scorecard The Statistics and Profit scorecards have an Export PDF button instead of the CSV menu. The PDF is a portrait page of the tiles you see on screen. When the scorecard shows a comparison with a previous period, each tile also carries its vs Last 7 days line with an up or down arrow, using fresh figures for both periods at the moment you export. A custom date range has no comparison period, so those PDFs show the tiles alone. ## Limits - A PDF contains at most 2,000 rows. When a report has more, the dialog says so before you export, the PDF opens with a notice naming both numbers, and a warning appears after the download. Export CSV or XLSX for the full set. - Charts are not exported. Switch back to the table view; the PDF always contains the table. - Generating a very wide report with many rows can take up to a minute. The dialog stays open until the file is ready. Note Like CSV and XLSX exports, the PDF is generated from your live data at the moment you export, not from the page in your browser. If you changed a price in the table moments ago, wait for the price to finish saving before exporting. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/overview/ # Reports Scheduled email summaries of forecast views, purchase orders, and saved reporting views. Enhanced-plan feature. [Enhanced plan] (/reference/subscription-plans/) Logistified’s scheduled reports are recurring emails, daily, weekly, bi-weekly, or monthly summaries of what’s happening in your shop, sent automatically to people on your team. Four types are available: [View Report] (/reference/glossary/#view-report), [Purchase Order Report] (/reference/glossary/#purchase-order-report), Report View Export, and Multi-Location Report. You’ll find them at Notifications → Scheduled reports. They used to have their own sidebar entry; that entry is gone, and old links forward to the new location automatically. Scheduled reports are not stock notifications. Reports run on a schedule; notifications fire on a threshold (e.g., stock-out). Both go via email, but the trigger model is different. Beyond the schedule, you can Send now to email a report immediately, and every report keeps a History of its runs with the delivery state of each one. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Creating a report] (/features/reports/creating-a-report/) Pick a type, configure it, save. [Report types] (/features/reports/report-types/) View Report, Purchase Order Report, Report View Export, and Multi-Location Report: when to use each. [Recipients & scheduling] (/features/reports/recipients-and-scheduling/) Who gets it and how often. [Cadence and time] (/features/reports/cadence-and-time/) Daily, weekly, bi-weekly, monthly + day and time of day. [Preview, send now, and history] (/features/reports/preview-and-send/) Validate before activating, send immediately, and check delivery. ## Key concepts - [View report] (/reference/glossary/#view-report) / [PO report] (/reference/glossary/#purchase-order-report) / Report View Export / Multi-Location Report: the four available types. - [Recipient] (/reference/glossary/#recipient): someone on your team who gets the email. Recipients live in [Settings → Recipients] (/features/settings/recipients/) and are shared with stock notifications. ## Where to next - [Notifications] (/features/notifications/overview/): the hub these reports live in, and the home of stock-out alerts. - [Settings → Recipients] (/features/settings/recipients/): the shared list of people who receive them. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/creating-a-report/ # Creating a report Pick a type, name it, configure, schedule, save. [Enhanced plan] (/reference/subscription-plans/) You create a scheduled report in Logistified in a few steps: pick a type, name it, configure it, add recipients, set the cadence, and save. ## On this page - Where to start - Steps - See also ## Where to start Notifications → Scheduled reports → Create report. The dialog asks for a Report Type and a Report Name, then Create & Configure opens the editor. ## Steps 1. Pick a type. Purchase Order Report, View Report, Report View Export, or Multi-Location Report. The type is locked once you save: to change types, create a new report. 2. Name it. Short, recognisable. The name appears in the email subject line. 3. Configure by type: - View Report: pick the saved Forecast view, then toggle the dashboard sections you want: Overdue Reorders, Reorder Recommendations (with a horizon-days input, default 14), Coverage Summary, ABC Distribution, Supplier Breakdown. Most sections have an optional nested “show variants” toggle that lists each variant in the bucket. - Purchase Order Report: pick which PO statuses to include (default: Sent / Confirmed / In Progress), toggle the Overdue Orders Alert, toggle the Arriving Soon section (with a days-ahead input, default 7), pick a sort order, and choose which sections to render (Quick Stats / Supplier Breakdown / Status Breakdown / PO Table). - Report View Export: pick a Report type and then the standard or saved View to email as a CSV attachment. There’s no Content tab: the emailed CSV replays that view exactly. - Multi-Location Report: pick a Report type and View the same way (only types with location-dependent columns are listed), then on the Layout tab pick up to 3 locations and, for each location-dependent column, whether it’s Total, Per location, or Both. A live preview shows the resulting CSV header row. 4. Add recipients. On the Recipients tab, tick the people who should get this report. Anyone missing can be created on the spot with Add recipient; they’re added to the shared list and ticked on this report in one step. The full list lives at Settings → Recipients. 5. Set the cadence. Daily, Weekly (pick a starting weekday), Bi-weekly (pick a starting weekday), or Monthly (pick a day of month). Plus a time-of-day (5-minute increments) and a timezone (a searchable list of every named timezone: search by name, abbreviation, offset, or city). 6. Save and activate. Toggle Enable this report and press Save Changes. The status badge flips from “Inactive” to “Active” and the first email arrives at the next scheduled time. Note If a save can’t be put on the schedule, you’ll see a “Saved, but not scheduled” warning instead of a plain success message, and the report keeps a Not scheduled badge on the Reports list until you reopen and save it again successfully. Tip Start with one recipient (you) and verify the contents before adding your team. Press Send now to get a real copy immediately instead of waiting for the schedule; you can even narrow that one send to just yourself. See [Preview, send now, and history] (/features/reports/preview-and-send/). ## See also - [Report types] (/features/reports/report-types/): details on each. - [Recipients & scheduling] (/features/reports/recipients-and-scheduling/): managing who receives what. - [Cadence and time] (/features/reports/cadence-and-time/): the supported schedules. - [Preview, send now, and history] (/features/reports/preview-and-send/): testing and delivery tracking. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/report-types/ # Report types View Report and Purchase Order Report: what each contains and how to configure it. [Enhanced plan] (/reference/subscription-plans/) Logistified offers four scheduled report types: View Report, Purchase Order Report, Report View Export, and Multi-Location Report. Stock-out alerting is no longer a report type; it moved to [stock notification rules] (/features/notifications/rules/), which fire in real time instead of on a schedule. ## On this page - View Report - Purchase Order Report - Report View Export - Multi-Location Report - See also ## View Report A [View Report] (/reference/glossary/#view-report) is an aggregated email dashboard built from a saved Forecast view. It is not a static export of the view’s table; instead, it groups variants into bucketed summaries and per-category breakdowns. Each section can be toggled on or off, and most sections have an optional nested toggle that lists the individual variants in each bucket. Sections you can include: - Overdue Reorders: items past their reorder date. - Reorder Recommendations: items reaching their reorder date inside a configurable window. The “Reorder window (days)” input controls the look-ahead (default: 14). - Coverage Summary: variants bucketed by days of coverage remaining: 0d, 1-3d, 4-7d, 8-14d, 15+d. Optional nested “show variants per bucket” toggle. - ABC Distribution: variants grouped by ABC class. Optional nested “show variants per ABC bucket” toggle. - Supplier Breakdown: variants grouped by supplier. Optional nested “show variants per supplier” toggle. When to use: weekly buyer or operations review tied to a specific Forecast view. “Every Monday morning, send my buyer the Coverage Summary and Reorder Recommendations for their assigned view.” The subject line of the email is {report name} followed by a dash and {view name}. ## Purchase Order Report A [Purchase Order Report] (/reference/glossary/#purchase-order-report) summarises your open purchase orders, with separate sections for orders that are overdue and orders arriving soon. Each section is independently toggleable. Sections you can include: - Quick Stats: total open POs, total value, overdue count. - Overdue Orders: POs whose expected delivery date has passed (no day-count input; uses today’s date as the cutoff). - Arriving Soon: POs expected within the next N days. The “Days ahead to show” input controls N (default: 7). - Supplier Breakdown: which suppliers currently have open orders. - Status Breakdown: count of POs in each status. - PO Table: the full table of matching POs. Two optional column toggles: Expected Delivery Dates and Order Values. Status filter (the 9 available statuses): - Draft - Sent - Partially Confirmed - Confirmed - In Progress - Partially Received - Received - Completed - On Hold Default selection: Sent, Confirmed, In Progress, the active orders on their way to you. Sort options for the PO Table: sort by Expected Delivery Date, Created Date, Order Value, or Supplier Name. Ascending or descending. When to use: weekly buyer / ops review. “Every Friday afternoon, send the team the POs that are overdue or arriving in the next 7 days.” The subject line of the email is the report name. ## Report View Export A Report View Export emails a saved or standard [Reporting] (/features/reporting/overview/) view as a CSV attachment, on the cadence you choose. The attachment replays the view exactly, the same rows, columns, filters, and sorting the Reports page shows you on screen. If an export is large enough to hit the row cap, the email says so. If the Reporting view has a date range, the attachment uses calendar days in your Shopify store timezone at send time. If Logistified cannot confirm that timezone and has no recent last-known value, the run fails rather than silently using UTC. Configure it with two fields: the Report type, then the View, either a standard view or one of your saved views. When to use: getting raw numbers into a spreadsheet on a regular basis. “Every Monday, email finance the sales-by-supplier view as a CSV.” This type has no Content tab and no Preview tab; the view itself is the definition and the preview. ## Multi-Location Report A Multi-Location Report emails a saved or standard [Reporting] (/features/reporting/overview/) view as a CSV attachment, like a Report View Export, but for a view whose numbers vary by location (stock levels, sales, and similar), you choose how each of those columns is split. Date-ranged files use your Shopify store timezone. The Total and every location column in one file use the same calendar-day boundary, even if the report takes long enough to cross midnight. Only report types with at least one location-dependent column are offered, for example Stock on Hand, Low Stock, and Sales reports. A view that groups its rows by location isn’t eligible, since there’d be nothing left to split per location. Configure it with three things, on the General and Layout tabs: - Reporting view: pick a report type, then the standard or saved view to split. Only eligible report types are listed. - Locations: pick up to 3 locations, in the order they should appear in the file. If a chosen location is later deleted from your shop, it’s automatically left out and named in the delivered email; if every chosen location is gone, the run fails instead of sending a file missing data. - Columns: for each location-dependent column in the view, choose Total (summed across the locations you picked), Per location (a separate column for each), or Both. Every other column in the view is included once, unchanged. A live preview on the Layout tab shows the exact header row the emailed CSV will have. When to use: comparing stock or sales side by side across your locations, in one file. “Every Monday, send the ops team on-hand stock at our three warehouses, split by location.” The subject line and cover note match a Report View Export, plus the selected locations and a note on how sales figures are attributed to a location, useful when a split total doesn’t quite match a shop-wide number. If a single location run in the file would come out too large, the run fails with a message suggesting you narrow the view with a product, vendor, supplier, or tag filter. This type has no Content tab and no Preview tab; its Layout tab (locations + column splits) is both the configuration and the preview. ## See also - [Creating a report] (/features/reports/creating-a-report/): the setup flow. - [Reporting] (/features/reporting/overview/): where the views behind a Report View Export or Multi-Location Report are built. - [Purchase Orders → Overview] (/features/supply-orders/purchase-orders/overview/): the workflow summarised by the Purchase Order Report. - [Notifications] (/features/notifications/overview/): the threshold-based counterpart, and the home of stock-out alerts. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/recipients-and-scheduling/ # Recipients & scheduling Who gets the report and where to manage them. [Enhanced plan] (/reference/subscription-plans/) Each scheduled report in Logistified goes to the recipients you pick for it. This page covers what a recipient is, where to manage them, and what happens when an email bounces. ## On this page - Recipients - Two places to manage them - Removing a recipient - Bounced emails - See also ## Recipients A list of people who receive a specific report. Each [recipient] (/reference/glossary/#recipient) has: - First Name (required) - Last Name (required) - Email (required) That’s all the contact data Logistified stores per recipient. There is no per-recipient view filter, no active/inactive toggle, and no consent flow; the same payload is sent to every recipient on a report. ## Two places to manage them Where Scope Settings → Recipients The shared list, everyone Logistified can email, with a Used by column showing which rules and reports each person is on. See [Settings → Recipients] (/features/settings/recipients/). Per-report Recipients tab Just this report’s recipients, ticked from the shared list. The shared list is the directory of people Logistified can email, and it’s the same one [stock notifications] (/features/notifications/overview/) use. Adding someone there doesn’t automatically subscribe them to anything; assignment happens per report, by ticking their box on the report’s Recipients tab. The same person can be assigned to as many reports and rules as you like. Recipients used to be managed under Reports and again under Notifications. There is now one page, under Settings, and the old links forward to it automatically. ## Adding someone without leaving the report If the person you need isn’t in the list, click Add recipient on the report’s Recipients tab. Fill in first name, last name, and email, and they’re created, added to the shared list, and ticked on this report, without losing anything else you’ve typed. The Manage recipients icon beside it opens the full Settings page. Recipients can also be edited now, so a typo or a changed address is a quick fix rather than a delete-and-re-add that would drop every subscription. ## Removing a recipient Two ways to stop someone from receiving a report: - Per report: untick their box on the report’s Recipients tab. - Globally: delete them in Settings → Recipients. This also removes them from every report and every notification rule they were assigned to; the confirmation tells you how many of each before you commit. There is no “deactivate” or “pause” state: only add and remove. ## Bounced emails A report’s History tab shows the delivery state of every run, so a bad address shows up as Bounced without you having to check anywhere else. Logistified doesn’t auto-remove bounced recipients; clean them up manually. No unsubscribe link is rendered in the email. Recipients who want to be removed need to contact you to be taken off the list. Caution Add yourself to a report before adding anyone else, and use Send now to check it. Test before broadcasting. ## See also - [Settings → Recipients] (/features/settings/recipients/): the shared list in full. - [Cadence and time] (/features/reports/cadence-and-time/): when it fires. - [Preview, send now, and history] (/features/reports/preview-and-send/): what you can verify before going live. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/recipient-view-filtering/ # Recipient view filtering for reports One report, many recipients, each receives only their slice. [Enhanced plan] (/reference/subscription-plans/) In Logistified’s scheduled reports, each recipient on a View Report or OOS Report can be tied to a saved Forecast view. When the report runs, that recipient only receives rows matching their view. ## On this page - What it does - Use case - How it works - Deleted views degrade silently - See also ## What it does Attaches a [recipient view filter] (/reference/glossary/#recipient-view-filter) to one report recipient. The report’s global payload is computed once; then for each recipient, their view filter narrows the rows. Each recipient gets a different email. ## Use case You manage three buyers, each responsible for a different category. Instead of three separate reports, create one report and attach the right view per buyer. ## How it works The report computes the global payload (every variant the report’s scope includes). Then for each recipient: - No view filter → recipient gets the full payload. - View filter set → recipient gets only rows matching their view. Five recipients on one report can have five different effective scopes. ## Deleted views degrade silently If a view is deleted after a recipient was attached, the recipient silently starts receiving the unfiltered payload. Check the recipient list periodically. Note This is the recommended way to scale reports to a multi-buyer team. ## See also - [Recipients & scheduling] (/features/reports/recipients-and-scheduling/): managing the recipient list. - [Forecast → Views & filters] (/features/forecast/views-and-filters/): the views being filtered. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/cadence-and-time/ # Cadence and time-of-day When the email goes out: daily, weekly, bi-weekly, or monthly, with a configurable day, time, and timezone. [Enhanced plan] (/reference/subscription-plans/) A scheduled report in Logistified goes out daily, weekly, bi-weekly or monthly, on the day, at the time and in the timezone you set. ## On this page - Supported cadences - Starting weekday (weekly / bi-weekly) - Day of month (monthly) - Time-of-day - Timezone - Editing cadence - Missed runs - See also ## Supported cadences Cadence Example Daily “Every day at 08:00.” Weekly “Every Tuesday at 09:00.” Bi-weekly “Every other Tuesday at 09:00.” Monthly “On the 1st of each month at 07:00.” Note Quarterly is no longer offered (since August 2026): a report on a Quarterly schedule was never sent, and the option has been removed. If one of your reports is still set to Quarterly, its frequency shows as “Quarterly (retired)” and it sends nothing; pick another frequency and save to start receiving it. ## Starting weekday (weekly / bi-weekly) When you pick Weekly or Bi-weekly, a second dropdown appears asking for the Starting Weekday (Sunday through Saturday). It pre-fills with today’s weekday when you switch to a weekly cadence; if no weekday is chosen at all, the day the schedule is activated is used and kept from then on. Bi-weekly reports fire every 14 days on that weekday. ## Day of month (monthly) When you pick Monthly, a Day of Month dropdown appears (1–31). It pre-fills with today’s day when you switch to Monthly; if no day is chosen, the day the schedule is activated is used and kept from then on. Days 29–31 send on the last day of shorter months; a report set to the 31st arrives on February 28 (or 29), April 30, and so on, instead of skipping those months. ## Time-of-day Pick the hour and minute. Minutes are in 5-minute increments (00, 05, 10, …, 55). ## Timezone You pick the timezone explicitly; the report is not auto-derived from your Shopify shop’s timezone. The picker offers every named timezone (around 160 entries, including South Africa Standard Time / SAST), and it’s searchable: type a zone name (“Eastern”), an abbreviation (“SAST”), a UTC offset (“+2”), or a city (“Johannesburg”) to find yours. ## Editing cadence Edit any time. The next scheduled run reflects the new cadence. ## Missed runs If the system is briefly unavailable at the scheduled time, the schedule catches up as soon as it can, typically within minutes. You’ll get the email a bit late. Schedules are also self-healing: a missed run re-arms itself automatically. ## See also - [Creating a report] (/features/reports/creating-a-report/): where the cadence is set. - [Preview, send now, and history] (/features/reports/preview-and-send/): testing without waiting, and checking delivery. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/reports/preview-and-send/ # Preview, send now, and history Check a report's layout before activating, send it immediately without waiting for the schedule, and see how past runs were delivered. [Enhanced plan] (/reference/subscription-plans/) Before a scheduled report in Logistified goes out on its schedule, you can preview its layout, send it right away, and check how past runs were delivered. ## On this page - The Preview tab - What Preview does NOT do - Send now - The History tab - Schedule state on the Scheduled reports list - What the delivery states mean - See also ## The Preview tab Purchase Order Reports and View Reports have a Preview tab. It renders the email body using sample data so you can validate the layout (which sections are included, how the headings read, whether the table columns look right) before activating. The Report View Export and Multi-Location Report types have no Preview tab: they email a CSV attachment of exactly the rows and columns your saved view shows, so the view itself (plus, for Multi-Location Report, the header preview on its Layout tab) is the preview. ## What Preview does NOT do - It does not pull your live shop data. The numbers, variants, and order IDs shown are placeholder samples. - It does not send anything to anyone. - It does not appear in the report’s History. For real content and a real delivery, use Send now. ## Send now Send now sends the report immediately, with your live data, independent of the schedule. It’s available two ways: the button at the bottom of the report editor, and the Send now item in the row menu on the Scheduled reports list. 1. Click Send now. A confirmation dialog opens: “This sends a real email immediately, independent of the schedule.” 2. Narrow the recipients if you want. The report’s saved recipients are listed with checkboxes; untick anyone who shouldn’t get this particular send. A running count reads “Sending to 2 recipients”. 3. Add a one-off address in the Also send to field if you’d like a copy to go somewhere that isn’t on the report, a colleague, or yourself. It applies to this send only and isn’t saved to the report. 4. Click Send now to confirm. Narrowing recipients here changes nothing permanent; the report’s saved recipient list and its schedule are untouched. A report with no saved recipients can still be sent this way by typing an address into Also send to. Note Send now is disabled while you have unsaved changes, with the tooltip “Save your changes first”, so what goes out always matches what’s saved. This replaces the old workaround of setting a report to Daily a few minutes ahead just to see one real copy. ## The History tab Every report has a History tab: “The last runs of this report, scheduled and manual, with their delivery state.” Column What it shows Executed at When the run happened. Source Manual for a Send now, Schedule for a scheduled run. Recipients How many people it went to. Status The delivery state (below). Error What went wrong, when something did, including which addresses failed. Otherwise a dash. Until a report has run at least once the tab reads “No runs yet.” The Last sent column on the Scheduled reports list shows the same thing in miniature: how long ago the most recent run was and how it was delivered, or Never for a report that has never gone out. ## Schedule state on the Scheduled reports list Two more columns on that list tell you whether a report is actually going to run: - Status: the on/off switch plus a badge: Active, Inactive, or a Not scheduled warning. The warning means the report is switched on but isn’t on the schedule; open it and save to put it back on. - Time: the send time in the report’s own timezone, with a Next: date underneath showing when the next run is due. A disabled report shows a dash. Saving a report always succeeds, even if arming its schedule doesn’t; you’ll see a message saying it was saved but couldn’t be scheduled, and the row shows Not scheduled until you save again. Changing a report’s cadence, time, or on/off state re-arms or cancels the schedule for you; there’s nothing to press. ## What the delivery states mean Status Meaning Pending The run has started and the email hasn’t been handed over yet. Sent The email was accepted for delivery. Delivered The receiving mail server confirmed delivery. This is the one you want. Bounced The receiving server rejected it, usually a wrong or closed address. Fix or remove it in [Settings → Recipients] (/features/settings/recipients/). Failed The run itself couldn’t complete, or at least one address errored. Check the Error column. Caution Once a report is enabled, every scheduled tick fires. If you misconfigured the schedule, switch Enable this report off. ## See also - [Creating a report] (/features/reports/creating-a-report/): where Preview and Send now live. - [Cadence and time-of-day] (/features/reports/cadence-and-time/): when the scheduled send happens. - [Recipients & scheduling] (/features/reports/recipients-and-scheduling/): managing who receives what. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/overview/ # Notifications The home for stock alerts and scheduled email reports: real-time rules that fire when inventory crosses a trigger, plus recurring report emails. Enhanced-plan feature. [Enhanced plan] (/reference/subscription-plans/) Notifications is the home for everything Logistified emails you about stock. It holds two things: Stock notifications, which are real-time alerts that fire the moment a variant’s inventory crosses a trigger, and Scheduled reports, which are recurring summaries sent daily, weekly, bi-weekly, or monthly. Both go out by email, but the trigger model is different. Stock notifications are event-driven: they fire on the inventory change that crossed your trigger, usually within seconds. Scheduled reports run on a clock: use them for recurring overviews. ## On this page - The Notifications hub - Stock notifications - Scheduled reports - Where things moved - Key concepts - Where to next ## The Notifications hub Opening Notifications in the sidebar lands you on a hub with two cards (Stock notifications and Scheduled reports), each showing how many are currently active. Click a card to open that list. Below the cards is an Activity panel: “Recent alerts and upcoming report runs”. It’s a single table covering both halves of the feature, so you can see at a glance what has gone out and what is queued up next: Column What it shows Type Alert for a stock notification, Report for a scheduled report. Test sends carry an extra Test badge. Item The product and variant that alerted, or the report’s name. Detail For an alert: the trigger that fired, the quantity, and the threshold. For a report: Manual run or Scheduled run, plus the report type. Location The location the alert came from, or a dash for shop-wide alerts. Status Delivery state (Pending, Sent, Delivered, Bounced, Failed) or Scheduled for a run that hasn’t happened yet. When How long ago it went out, or how far off the next run is. View All Rules and View All Reports in the panel header jump straight to the two lists. ## Stock notifications You can create as many rules as you like. Each rule is independent and carries its own name, on/off switch, triggers, monitored variants, and recipients, so “low stock on bestsellers, emailed to the buying team” and “anything out of stock in the Berlin warehouse, emailed to that warehouse’s manager” are two separate rules that don’t interfere with each other. Every rule also picks a scope: shop-wide (Global) or Per location. See [Notification rules] (/features/notifications/rules/). ## Scheduled reports Scheduled reports now live inside Notifications too, at Notifications → Scheduled reports. Everything about them is unchanged apart from the location and two additions: a Send now button and a History tab. See the [Reports overview] (/features/reports/overview/). ## Where things moved Note Old bookmarks keep working; Logistified forwards them to the new pages automatically. What you used to do Where it is now Scheduled reports in the sidebar Notifications → Scheduled reports: the separate sidebar entry is gone. Notifications → Recipients Settings → Recipients Reports → Recipients Settings → Recipients The single shop-wide notification rule Notifications → Stock notifications: your existing settings were carried over into a rule you can keep using, rename, or copy. ## Key concepts - Rule: one named stock-alert configuration: triggers, variants, recipients, and an on/off switch. - Scope: whether a rule watches your shop-wide stock (Global) or each location separately (Per location). - [Stock-out alert] (/reference/glossary/#stock-out-notification): fires the moment on-hand crosses to zero. - [Stock threshold] (/reference/glossary/#threshold-notification): fires the moment on-hand crosses below a configured value. - [Days from reorder point] (/reference/glossary/#days-from-reorder-notification): fires when forecast-projected days until reorder drop to or below a configured value. - [Recipient] (/reference/glossary/#recipient): someone on your team who gets the email. The recipient list is shared with [scheduled reports] (/features/reports/overview/) and lives in [Settings → Recipients] (/features/settings/recipients/). ## Where to next [Notification rules] (/features/notifications/rules/) Creating rules, choosing a scope, and sending a test email. [Triggers] (/features/notifications/three-scenarios/) The seven things a rule can watch for. [Monitored variants] (/features/notifications/monitored-variants/) Pick, scan, or upload the variants a rule watches. [Recipients] (/features/notifications/recipients/) Who gets the alerts. [When alerts fire] (/features/notifications/cadence-and-rate-limits/) Real-time triggering and built-in de-duplication. [Scheduled reports] (/features/reports/overview/) The schedule-based counterpart. - [Guides → Configure notifications] (/guides/configure-notifications/): end-to-end walkthrough. Last updated: 5 September 2026 --- Source: https://docs.logistified.app/features/notifications/rules/ # Notification rules Create as many stock-alert rules as you need, each with its own scope, triggers, variants, and recipients, and send yourself a test email before going live. [Enhanced plan] (/reference/subscription-plans/) In Logistified, a notification rule is one named stock-alert configuration. Your shop can have as many as you like, each with its own triggers, its own monitored variants, its own recipients, and its own on/off switch, so different teams can watch different things without stepping on each other. ## On this page - The rules list - Creating a rule - The rule editor - Scope: Global or Per location - Narrowing what a rule covers - Send a test email - Enabling, disabling, and deleting - See also ## The rules list Notifications → Stock notifications lists every rule you’ve created, above two counters: Total rules and Active rules. Column What it shows Rule The rule’s name, with All variants in view or Specific variants underneath. Scope Global or Per location. View The Forecast view that scopes the rule, or All variants if none is set. Triggers A one-line summary of what’s switched on, e.g. Stock-out · ≤ 25 units · Constants: min, reorder point. Reads No triggers when nothing is enabled. Recipients How many people are subscribed to this rule. Status A switch plus an Active / Inactive badge: flip a rule on or off without opening it. Updated When the rule last changed. The search box filters by name. Each row’s Actions menu offers Edit rule, Enable rule / Disable rule, Send test email, and Delete rule. Tick several rows to delete them together. ## Creating a rule 1. Click New rule. 2. Give it a Rule name: this is what you’ll see in the list and in every alert email. “Low stock: bestsellers” is more useful than “Rule 2”. 3. Click Create & configure to open the editor. ## The rule editor Five tabs, plus an Enable this rule switch and an Active / Inactive badge in the header: Tab What’s on it General Rule name, Scope, Forecast view, and (on per-location rules without a view) the Locations picker. Triggers Monitoring scope, the default triggers, and the variant-constant triggers. See [Triggers] (/features/notifications/three-scenarios/). Variants The variants this rule watches and any per-variant overrides. See [Monitored variants] (/features/notifications/monitored-variants/). Recipients Who gets this rule’s emails. See [Recipients] (/features/notifications/recipients/). Preview A live preview of each alert email using sample data. Changes are not saved as you type; press Save at the bottom when you’re done. If you try to navigate away with unsaved work, Logistified asks first. [anchor: scope--global-or-per-location] ## Scope: Global or Per location The Scope setting on the General tab decides what “stock” means for this rule. Pick one: Global (shop-wide inventory): triggers are evaluated against your total available stock across every location. One number per variant, one alert per variant. This is how notifications have always worked, and it’s the right choice when you sell from a single pool and don’t care where the units sit. Per location (inventory at each location): triggers are evaluated separately at each location, so a variant can alert for the warehouse where it ran out without going quiet just because another warehouse still has plenty. Choosing this also unlocks the [four variant-constant triggers] (/features/notifications/three-scenarios/#the-four-variant-constant-triggers). Note Switching a rule back to Global clears its location list and its variant-constant selection, since neither applies shop-wide. Alerts from a per-location rule name the location that crossed the boundary, and the location appears in the Activity table on the Notifications hub. ## Narrowing what a rule covers Two independent controls, both optional: - Forecast view: pick a saved view and the rule only watches the variants in it (on a per-location rule, only that view’s selected locations, too). Choose No view: all variants to watch your whole catalog. A view is only required for the days-from-reorder trigger. - Locations: on a per-location rule with no view selected, pick the locations to watch. Leave it empty and every location is monitored; the help text under the picker tells you which of the two you’re in (“All locations are monitored. Pick locations to narrow the rule.” or “Monitoring 2 of 5 location(s).”). ## Send a test email Every rule has a Send test email button, at the bottom of the editor and in the list’s Actions menu. It sends a real email, right now, so you can check the wording and confirm delivery before you switch the rule on for your team. 1. Click Send test email. The dialog tells you which triggers will be tested: one email per enabled trigger. 2. Choose a variant. Click Choose a variant and pick a real product from your catalog. The test uses that variant’s actual current stock against this rule’s thresholds, so what you receive matches what a real alert would look like. 3. Pick a location, per-location rules only. The test then reads stock and constants at that location. If the rule watches exactly one location, it’s chosen for you. 4. Choose recipients. Tick anyone from the rule’s saved recipients, and/or type a one-off address into Also send to. The dialog keeps a running count: “Sending to 2 recipients”. 5. Click Send test email. Test emails are marked [Test] in the subject so nobody mistakes one for a real alert. They also never affect cooldowns; sending a test won’t suppress the genuine alert that follows, and won’t consume the 24-hour days-from-reorder window. If the rule has no trigger enabled there is nothing to test, and the dialog says so. ## Enabling, disabling, and deleting - Enable this rule at the top of the editor, or the Status switch in the list, turns a rule on and off. A disabled rule keeps its whole configuration; nothing is lost. - Delete rule removes the rule permanently, along with its recipients, its variant overrides, and its alert history. It asks for confirmation first. ## See also - [Triggers] (/features/notifications/three-scenarios/): what a rule can watch for. - [Monitored variants] (/features/notifications/monitored-variants/): choosing the variants. - [Recipients] (/features/notifications/recipients/): who gets the emails. - [When alerts fire] (/features/notifications/cadence-and-rate-limits/): timing and de-duplication. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/three-scenarios/ # Notification triggers Stock-out, stock threshold, days from reorder point, and the four variant-constant triggers: what each one watches and when it fires. [Enhanced plan] (/reference/subscription-plans/) In Logistified’s stock notifications, a trigger is the condition that makes a rule send an email. Each rule has its own set, switched on and off independently on the rule’s Triggers tab, and each one is evaluated separately every time Shopify reports an inventory change for a monitored variant. Three triggers are available on every rule. Four more (the variant constants) unlock when the rule’s scope is set to Per location. ## On this page - Stock-out alert - Stock threshold - Days from reorder point - The four variant-constant triggers - Monitoring scope - Per-variant overrides - Do I need a Forecast view? - See also ## Stock-out alert Fires the moment a variant’s on-hand inventory reaches 0. No configuration value, just switch it on. - Triggers when inventory drops from a positive number to zero. - Will not re-fire while the variant stays at zero; it only re-arms after stock rises above zero again. Use it for the loudest alerts: “tell me the second something goes out of stock.” ## Stock threshold Fires when a variant’s on-hand inventory falls below a number of units you configure (the default is 50). - Triggers when inventory crosses from above the threshold to at or below it. - Will not re-fire while inventory stays below the threshold; it only re-arms once stock rises above it again. Use it for early warnings on slow-moving items, before they hit zero. ## Days from reorder point Fires when the forecast-projected number of days until a variant hits its reorder point drops to or below a number you configure (the default is 14). - Logistified uses your forecast to estimate when each variant will reach its reorder point. When that estimate gets short enough, the trigger fires. - A 24-hour per-variant cooldown prevents the same variant from re-alerting if the forecast wobbles. After 24 hours it can fire again if the estimate is still inside your window. - Variants without enough forecast data are silently skipped. Use it for “what should I order this week?” alerts that catch slow drift before it becomes a stock-out. Note This is the only trigger that needs a Forecast view. Its switch stays disabled until you pick one on the rule’s General tab; hover it and you’ll see “Select a view on the General tab to use forecast-based triggers”. ## The four variant-constant triggers A rule scoped to Per location gets a Variant constants card on its Triggers tab. Switch it on and tick any combination of four boundaries. Instead of one shared number for the whole rule, each variant is compared against its own constants (the values you already maintain per variant) at the location whose stock just changed. Trigger Fires when Below minimum inventory Stock at a location drops to or below the variant’s minimum. Below reorder point Stock at a location drops to or below the variant’s static reorder point. Below target inventory Stock at a location falls under the variant’s target; landing exactly on it is fine. Above maximum inventory Stock at a location reaches or exceeds the variant’s maximum. This one is an overstock warning, not a shortage. The values come from Settings → Variant Settings → Variant constants. A variant with no value for a given boundary simply never alerts on that boundary, so you can roll these out gradually, filling in constants for the items you care about first. On a Global rule the card explains that these triggers are per-location only, and points you at the scope selector. Tip Set your minimums, reorder points, targets, and maximums per variant first, then let one per-location rule watch all four. It replaces a pile of hand-maintained thresholds with values you already keep up to date. See [Forecast → Variant constants] (/features/forecast/variant-constants/). ## Monitoring scope The Triggers tab opens with a Monitoring scope card (“Choose which variants this rule watches”): - Monitor all variants: the triggers you set below apply to every variant the rule covers. You can still override individual variants on the Variants tab. - Monitor only specific variants: only the variants listed on the Variants tab are watched, and the default triggers are ignored. If you pick “Monitor only specific variants” and haven’t added any yet, the card warns you: “No variants configured yet. Add variants on the Variants tab.” ## Per-variant overrides Whichever mode you choose, any individual variant can carry its own trigger values, a tighter threshold for an A-tier item, for instance. Overridden rows are badged Custom in the variants table. See [Monitored variants] (/features/notifications/monitored-variants/). ## Do I need a Forecast view? No, not any more. A view is optional on every rule, and only the days from reorder point trigger requires one. - No view: the rule watches everything. On a per-location rule you can then narrow it with the Locations picker instead. - With a view: only the variants in that view are watched, and on a per-location rule only that view’s selected locations. If you clear the view while the days-from-reorder trigger is on, Logistified switches that trigger off for you. ## See also - [Notification rules] (/features/notifications/rules/): scope, locations, and the rest of the editor. - [Monitored variants] (/features/notifications/monitored-variants/): choosing what a rule watches. - [When alerts fire] (/features/notifications/cadence-and-rate-limits/): timing and de-duplication. - [Forecast → Variant constants] (/features/forecast/variant-constants/): where the four constants come from. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/monitored-variants/ # Monitored variants Choose the variants a rule watches (search your catalog, scan barcodes, or upload a spreadsheet) and give individual variants their own trigger values. [Enhanced plan] (/reference/subscription-plans/) The Variants tab on a Logistified notification rule is where you decide which products it watches and where you give individual variants their own trigger values. Its heading changes with the rule’s monitoring scope: Monitored Variants when the rule watches only specific variants, Variant-Specific Triggers when it watches everything and you’re only adding exceptions. ## On this page - The variants table - Three ways to add variants - Per-variant trigger overrides - Uploading a spreadsheet - Downloading the current list - See also ## The variants table Column What it shows Product / Variant The product and variant name. SKU The variant’s SKU, or a dash. Locations All locations, or the specific location this row applies to. Triggers Using default triggers, or the values that override them. Rows with overrides get a Custom badge. Status Whether this row is actively monitored. Actions Edit or remove the row. Use the search box to find a variant in a long list, and the checkboxes plus Configure Selected to apply one set of triggers to many variants at once. ## Three ways to add variants The Add variants button opens a short menu: - Search products: the familiar product picker. Search your catalog and tick the variants you want. - Scan barcode: opens “Scan variants to monitor”. Scan a barcode or SKU with a hand scanner or your device camera (or type one), and each match is added to the rule. Quantities are ignored; this is a picking aid, not a count. Variants added this way inherit the rule’s default triggers. - Upload CSV/XLSX: bulk-load a whole list from a spreadsheet, complete with per-variant trigger values. See below. Note Scan barcode and Upload CSV/XLSX are the fast paths when your thresholds already live in a spreadsheet or on a shelf label. The product picker is best for a handful of items. ## Per-variant trigger overrides Adding variants opens Configure Triggers for N Variant(s), where you set the trigger values that apply to just those variants: Days from Reorder Point, Stock Threshold, and Stock-Out Alert, plus the four variant constants on a per-location rule. Leave everything off and the variants simply follow the rule’s defaults. Use the pencil icon on a row to open Edit Triggers and adjust one variant later. On a per-location rule that dialog also has a Location field: leave it on All locations for a row that governs everywhere, or pick a location to add a second, location-specific row. Where both exist, the location-specific row wins for that location and the all-locations row covers the rest. ## Uploading a spreadsheet Add variants → Upload CSV/XLSX opens Import variants from CSV/XLSX. It’s the same upload flow used everywhere else in Logistified: download the template, fill it in, upload, map your columns, review, import. 1. Download the template from the upload step and fill it in, or upload your own file and map the columns yourself. 2. Upload the CSV or XLSX. 3. Check the mapping. Logistified matches your column headers automatically; Change mapping lets you correct it. 4. Review variants to import. Every row is matched against your catalog by SKU or Variant ID and labelled Rows saved, Changed, Unchanged, Rows removed, or Skipped. Rows that don’t match anything are flagged as errors, and the import is blocked until you fix or remove them. 5. Decide merge or replace. By default the file is merged into the rule’s current list. Tick Replace existing list and any variant on the rule that isn’t in your file is removed. 6. Click Import. The buttons on the review step run Change mapping → Upload a different file → Import, left to right. ### The template columns Column What to put in it SKU The variant’s SKU. Use either SKU or Variant ID per row. Variant ID The Shopify variant ID. Wins over SKU when both are filled in. Location ID Optional. Blank means the row applies to every location. Location name Used when Location ID is empty. Must match exactly one of your locations. Import action UPDATE (or blank) saves the row; DELETE removes it from this rule. Enabled Blank or TRUE monitors the variant; FALSE keeps the row but mutes it. Stock-out alert Alert when stock reaches 0. Leave every trigger column blank to inherit the rule’s triggers. Stock threshold Alert when stock falls to this many units. Blank switches the trigger off. Days before reorder point Alert this many days before the reorder point. Blank switches it off. Needs a Forecast view on the rule. Below minimum inventory\nBelow reorder point\nBelow target inventory\nAbove maximum inventory The four variant-constant triggers. Per-location rules only: they’re ignored on a global rule, and the review step tells you so. Caution Imported rows are written to the rule immediately. Any other unsaved changes on the page still need Save. ## Downloading the current list Download current list exports the rule’s saved variants as CSV or XLSX, in exactly the same columns as the import template. That makes it a round trip: download, edit the thresholds in your spreadsheet, upload the same file back. It’s also the quickest way to audit a big rule, or to copy a tuned variant list from one rule into another. ## See also - [Triggers] (/features/notifications/three-scenarios/): what the trigger columns mean. - [Notification rules] (/features/notifications/rules/): the rest of the editor. - [Guides → Import data from CSV or XLSX] (/guides/import-data-csv-xlsx/): how the upload flow works everywhere in Logistified. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/recipients/ # Recipients of a notification rule Choosing who receives a rule's alerts, and how the shared recipient list under Settings works. [Enhanced plan] (/reference/subscription-plans/) A Logistified notification rule emails the recipients you subscribe to it. This page covers what a recipient is, where the shared list is managed, and how to add or remove people on a rule. ## On this page - What a recipient is - Two places to manage them - Subscribing people to a rule - Adding someone without leaving the rule - Removing recipients - Previewing what they’ll receive - Unsubscribing and bounces - See also ## What a recipient is A [recipient] (/reference/glossary/#recipient) is a person Logistified can email. Each record has three fields, all required: - First name - Last name - Email That’s the whole record. There’s no per-recipient view filter, no active/inactive toggle, and no per-recipient delivery setting; you control who gets what by subscribing them to individual rules and reports. ## Two places to manage them Where What you do there Settings → Recipients Add, edit, and delete people in the shared list. The same list powers stock notifications and [scheduled reports] (/features/reports/overview/), and the Used by column tells you which rules and reports each person is on. See [Settings → Recipients] (/features/settings/recipients/). A rule’s Recipients tab Tick the boxes next to the people who should receive this rule’s emails. Untick to unsubscribe them from this rule without deleting them. Adding someone to the shared list doesn’t subscribe them to anything; subscription happens per rule. Note Recipients used to be managed under Notifications and again under Reports. There is now one place, Settings → Recipients, and the old links forward to it automatically. ## Subscribing people to a rule Open the rule, go to the Recipients tab, and tick the people who should receive it. The card shows a running N selected badge, and a search box helps on a long list. At least one recipient is required before a rule can be saved. ## Adding someone without leaving the rule If the person you need isn’t in the list yet, click Add recipient right there on the Recipients tab. Fill in first name, last name, and email, and they’re created, added to the shared list, and ticked on this rule automatically, without losing anything else you’ve typed into the rule. The icon next to it, Manage recipients, opens the full Settings → Recipients page when you’d rather work there. ## Removing recipients - From a single rule: untick the box on the rule’s Recipients tab. - From the shared list entirely: delete them in Settings → Recipients. The confirmation tells you exactly how many rules and reports they’ll be removed from before you commit. ## Previewing what they’ll receive Two options, and they answer different questions: - The rule’s Preview tab renders each alert email with sample data, so you can check the layout and wording. - Send test email sends a real email using a real variant’s current stock. Use this one when you want to confirm delivery actually works. See [Notification rules] (/features/notifications/rules/#send-a-test-email). Tip Add yourself first, send yourself a test, then add the rest of the team. ## Unsubscribing and bounces The emails don’t carry an unsubscribe link; to stop sending to someone, untick them on the rule or delete them from the shared list. Logistified doesn’t automatically remove addresses that bounce, but it does show you when it happens: bounced sends appear as Bounced in the Activity table on the Notifications hub, and in a report’s History tab. Clean up problem addresses yourself. ## See also - [Settings → Recipients] (/features/settings/recipients/): the shared list in full. - [Triggers] (/features/notifications/three-scenarios/): what makes an email fire. - [Reports → Recipients & scheduling] (/features/reports/recipients-and-scheduling/): same list, scheduled reports. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/recipient-view-filtering/ # Recipient view filtering for notifications Per-recipient scope on a notification rule. [Enhanced plan] (/reference/subscription-plans/) In a Logistified notification rule, each recipient can be tied to a saved Forecast view. They’ll only receive alerts for variants matching their view. ## On this page - What it does - Use case - Deleted view degrades silently - See also ## What it does Attaches a [recipient view filter] (/reference/glossary/#recipient-view-filter) to one notification recipient. When the notification fires, the recipient only sees variants from their view. ## Use case You manage three buyers, each responsible for a different category. One stock-out rule, three recipients, three different view filters: each buyer sees only their category. ## Deleted view degrades silently If you delete the view a recipient is tied to, they silently start receiving unfiltered alerts. Check the recipient list periodically. Note This is the recommended way to scale notifications to a multi-buyer team. ## See also - [Recipients] (/features/notifications/recipients/): managing the list. - [Forecast → Views & filters] (/features/forecast/views-and-filters/): the views being filtered. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/notifications/cadence-and-rate-limits/ # When alerts fire How real-time triggering works and how Logistified prevents the same alert from repeating. [Enhanced plan] (/reference/subscription-plans/) Logistified’s stock notifications are real-time. There is no daily run and no schedule to wait for; emails go out within seconds of the inventory change that triggered them. ## On this page - The flow - Built-in de-duplication - Per-location rules alert per location - Test sends never affect cooldowns - When alerts do not fire - Downgrading from Enhanced - See also ## The flow 1. A variant’s inventory changes in Shopify (sale, restock, manual edit, receiving a purchase order, and so on). 2. Shopify tells Logistified about the change. 3. Logistified evaluates each enabled rule’s triggers against the new and previous quantities, shop-wide for a Global rule, at the affected location for a Per location rule. 4. If a trigger condition just crossed, the email is queued and sent within seconds. ## Built-in de-duplication You won’t get spammed if a variant stays in the alert state. Each trigger fires once per crossing: - Stock-out alert fires the moment on-hand goes from positive to zero. It does not re-fire while the variant stays at zero; it re-arms only when stock rises back above zero. - Stock threshold fires the moment on-hand crosses from above your threshold to at or below it. It does not re-fire while inventory stays below the threshold; it re-arms only when stock rises back above it. - The four variant-constant triggers behave the same way: one email when the boundary is crossed, then quiet until stock moves back to the other side of it. - Days from reorder point fires when the forecast-projected days-until-reorder drops to or below your value. To absorb daily forecast jitter, a 24-hour per-variant cooldown blocks a repeat alert for the same variant. After 24 hours it can fire again if the variant is still inside your window. In practice a long-running stock-out sends one email when the item first hits zero, not one every day. ## Per-location rules alert per location On a Per location rule the crossing is tracked separately for each location. The same variant can alert for one warehouse today and a different one next week, and going out of stock in Berlin doesn’t stop a later alert for the same variant in Hamburg. Each email names the location that crossed the boundary. A Global rule tracks one crossing per variant, against your total available stock across all locations. ## Test sends never affect cooldowns Send test email is completely separate from the real alert path. A test never marks a trigger as fired, never consumes the 24-hour days-from-reorder window, and never suppresses the genuine alert that follows. Test as often as you like. Test emails are marked [Test] in the subject line, and appear in the Activity table with a Test badge. ## When alerts do not fire A few conditions silently skip a variant: - The rule’s Enable this rule switch is off. - No triggers are enabled on the rule. - No recipients are ticked on the rule (nobody would receive it anyway). - The rule has a Forecast view selected and the variant isn’t in it. - The rule is per-location, has locations selected, and the change happened at a different location. - For the variant-constant triggers: the variant has no value saved for that boundary. - For the days-from-reorder trigger: there isn’t enough forecast data yet, or the projected days are zero or negative. - The shop isn’t on the Enhanced plan at the moment the stock changed. ## Downgrading from Enhanced Disable your rules before downgrading. On a non-Enhanced plan, rules stop being evaluated, so no emails go out, but every configuration stays exactly as it was, and upgrading again re-activates it. If you want a clean break, switch each rule off. Note If alerts feel too noisy, switch the rule’s Monitoring scope to Monitor only specific variants and list just the items you actually want to watch, or narrow the rule with a Forecast view or a shorter location list. ## See also - [Triggers] (/features/notifications/three-scenarios/): what’s being watched. - [Notification rules] (/features/notifications/rules/): scope, locations, and test sends. - [Reports → Cadence and time] (/features/reports/cadence-and-time/): the scheduled counterpart for recurring summaries. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/pos/overview/ # Shopify POS Receive transfer orders and purchase orders and count stock takes from the Logistified tile in Shopify POS. Logistified adds a tile to Shopify POS so the people standing next to the stock can do the inventory work there, on the till or on a phone, without a Shopify admin account and without walking back to a desk. It’s available on every plan. Shopify POS is not [Cloud Platform] (/features/cloud-platform/overview/): Cloud Platform is a separate browser surface you share with a warehouse tablet by link, while this lives inside the Shopify POS app your retail staff already use. ## On this page - The Logistified tile - Everything happens at the device’s location - Receive transfers - Receive purchase orders - Stock takes - Scanning and counting - What POS deliberately can’t do - Who can use it - See also ## The Logistified tile On the POS home screen, the smart grid carries a Logistified tile reading “Receive and count inventory”. Tapping it opens the hub, which lists the Workflows: Workflow What it’s for Receive transfers Count incoming transfer orders at this location. Receive purchase orders Count supplier deliveries against their purchase order. Stock takes Count what is on hand at this location. Label checking Scan printed labels against their expected item. Marked Coming soon: the row is there but not yet tappable. Each workflow opens a list of the open documents you can work on, with a Refresh button above it; a transfer sent while you were standing on the screen only appears once you re-fetch. ## Everything happens at the device’s location Every list and every count is scoped to the location the POS device is currently signed in to. You never pick a location in Logistified on POS; the till’s location is the location. That means: - Receive transfers shows only transfers headed to this location. - Receive purchase orders shows only orders being delivered to this location. - Stock takes shows only takes running at this location, and a new take you start is created there. If someone switches the device’s location while a document is open, the screen stops and says so (“This device switched to a different location. Go back and reopen.”) rather than counting stock into the wrong place. Note Only the newest documents fit on a device. On stock takes and purchase orders the list says so when there are more and points you at the Logistified admin for the rest. ## Receive transfers Open transfers headed to this location are listed with where they came from, their status, how much has already been received, and a badge reading how many units are still outstanding (or Complete). Open one and count what actually arrived per line, with the stepper, the keypad, or the scanner. Each row shows what’s already been received and what was expected, and an All button fills in everything still outstanding. The button at the bottom counts up with you (Receive 42 units). A transfer can’t be over-received on POS: a line accepts at most what’s still outstanding. The result is an ordinary partial or full receipt, with the same statuses, the same inventory effects, and the same audit trail as receiving in the admin. ## Receive purchase orders Supplier deliveries work the same way, listed with the expected delivery date, the product count, the order status, and a received / expected badge. Each line shows what’s already been received and what was ordered, plus an All button that fills in everything still outstanding, and the bottom button reads Receive 42 units as you count. Over-receiving is allowed, but never silently. If your counts exceed what the order expects, tapping Receive raises a confirmation first (“You are receiving more than expected for N items. Continue?”) listing each affected line as received of expected. Choose Receive anyway to go ahead, or Review quantities to go back and fix the counts. Note Purchase orders [delivered to another supplier] (/features/supply-orders/purchase-orders/deliver-to-supplier/) and transfer orders [shipped to a supplier] (/features/supply-orders/transfer-orders/supplier-destination/) never appear on POS; those goods don’t arrive at a retail location, so there’s nothing to receive at the till. ## Stock takes Open takes at this location are listed with their reason, when they were created, and how many of their items are counted. New stock take starts one on the spot: pick a reason from your shop’s saved list, or choose Count without a reason and set one later in the admin. Counting on POS is blind. Each line shows the product, an Uncounted badge or the count you’ve already saved, and a quantity field, and nothing else. There’s no expected quantity, no unit cost, and no variance, so the count you write down is what you see on the shelf, not a number nudged toward what the system expected. The footer keeps a running “N of M counted” and an “N items changed” tally, and Save counts commits them. Scanning an item that isn’t on the take yet adds it automatically; start from an empty take, walk the shelf, and the take builds itself as you scan. On an empty take the screen says as much: “Scan an item to add it. Only what you count ends up on this stock take.” If a manager completes the take in the admin while you’re still counting, the device says so plainly (“A manager completed this stock take. Your unsaved counts were not saved.”) and offers the only sensible way out, back to the list. Nothing you typed is quietly written into a closed document. ## Scanning and counting - Quantity fields are steppers. Tap − / + for one at a time, or tap the number to bring up the numeric keypad and type the whole figure, faster than 24 taps for a box of 24. - Barcode scanners just work. An external or built-in POS scanner needs no setup: point it at a barcode and the matching line counts up by one. Two scans of two identical units both count. - The camera is a scanner too. Where the device offers a camera, the scan panel has a toggle to open it; this is the camera scanning the admin app doesn’t have. - Each screen echoes the scan. A “Last scan” line names the item you just scanned, or warns you that nothing matched, so you don’t have to look up from the shelf. - Long documents get a filter. Past a handful of lines, a search box appears above the list. The “Items (n)” heading keeps showing the whole document’s count, so filtering never looks like lines went missing. ## What POS deliberately can’t do POS is a counting surface, not a management one. The following stay in the Logistified admin: - Applying a stock take to Shopify. Counting on POS never writes on-hand to Shopify; a manager reviews the discrepancies and runs Apply to Shopify in the admin. - Cost, value change and variance on a stock take. Blind counting, by design. - Rejections and cancellations when receiving a purchase order. POS records what arrived; the rest is an admin workflow. - Creating documents other than stock takes. Transfers and purchase orders have to exist already. - Anything on a document delivered to or held at a supplier (see the note above). ## Who can use it Anyone who can sign into your Shopify POS. Staff don’t need access to the Shopify admin, or a Logistified login of their own; the POS session is the credential. The documents they can see and touch are limited to the device’s location, which keeps a shop-floor device scoped to the shop floor. ## See also - [Stock takes] (/features/inventory/stock-takes/): the full stock-take feature in the admin, including Apply to Shopify. - [Transfer orders → Shipping & receiving] (/features/supply-orders/transfer-orders/shipping-receiving/): what a receipt does to inventory. - [Purchase orders → Receiving stock] (/features/supply-orders/purchase-orders/receiving/): receiving in the admin. - [Cloud Platform] (/features/cloud-platform/overview/): the separate device surface for label checking. Last updated: 14 September 2026 --- Source: https://docs.logistified.app/features/cloud-platform/overview/ # Cloud Platform (Beta) A separate browser interface for warehouse devices: Label Checker is the first action. [Enhanced plan] (/reference/subscription-plans/) [Cloud Platform] (/reference/glossary/#cloud-platform) is a separate browser-based interface for warehouse devices: tablets, phones, handheld scanners. You set up sessions inside Logistified, share a link or QR code with a tablet, and the device shows a dedicated warehouse workflow. The first available action is [Label Checker] (/reference/glossary/#label-checker). Cloud Platform is not Shopify POS. They’re unrelated. Cloud Platform is Logistified’s own browser surface for warehouse work that doesn’t belong inside the Shopify admin iframe. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Label Checker] (/features/cloud-platform/label-checker/) The first available action: scan incoming labels against an expected list. [Creating a session] (/features/cloud-platform/creating-a-session/) Pick scope, expiry, credentials, operators, generate QR + URL. [Sharing with the device] (/features/cloud-platform/sharing-with-device/) QR code or URL: how the device gets access. [Using the device] (/features/cloud-platform/using-the-device/) The operator's workflow: login, runs, modes, offline, install. [Operators & PINs] (/features/cloud-platform/operators-and-pins/) Name your staff, give each a PIN, attribute scans to a person. [Scan statistics] (/features/cloud-platform/scan-statistics/) Review and export what a device scanned, by day and run. [Item look-up] (/features/cloud-platform/item-lookup/) Scan or type a code to see how many times it's been scanned, and when. [Scan reports] (/features/cloud-platform/scan-reports/) Email a daily CSV of a session's scans to recipients. [Revoking sessions] (/features/cloud-platform/revoking-sessions/) Ending access early. [Sounds] (/features/cloud-platform/sounds/) Per-shop audio feedback for success and failure. [Plan gate] (/features/cloud-platform/plan-gate/) What's gated, what's browsable. ## Key concepts - [Cloud Platform] (/reference/glossary/#cloud-platform): the device-side product, branded “P&H Cloud Platform (Beta)” in the top nav. - [Label Checker] (/reference/glossary/#label-checker): the first action. - [Session link] (/reference/glossary/#session-link): the encrypted URL (with paired QR code). - [Session credentials] (/reference/glossary/#session-credentials): optional username + password. - Operators: named warehouse staff, each with a 4-digit PIN, who can gate a session so scans are attributed to a person. - Scan statistics: the admin view of what a device scanned, by day → run → individual scan, exportable. - Item look-up: search one session’s scan history for a single barcode or SKU. - [Success sound] (/reference/glossary/#success-sound) / [Failed-scan sound] (/reference/glossary/#failed-scan-sound): per-shop audio feedback. ## Where to next - [Guides → Set up the Label Checker on a tablet] (/guides/set-up-label-checker-on-tablet/): worked walkthrough. Last updated: 17 August 2026 --- Source: https://docs.logistified.app/features/cloud-platform/label-checker/ # Label Checker The first Cloud Platform action: scan incoming labels against an expected list. [Enhanced plan] (/reference/subscription-plans/) Label Checker is the first action on Logistified’s Cloud Platform: a warehouse device scans incoming labels against a list of the variants you expect to receive. ## On this page - What Label Checker does - Typical workflow - What it’s not - See also ## What Label Checker does Open a Cloud Platform session on a device. The device shows: - A list of variants you expect to receive (built from a saved Forecast view or an ad-hoc filter you defined in Logistified), each shown with its product photo so operators can visually confirm what they’re checking, however large the expected list is. - A scanner-friendly input: point a camera at a barcode, or scan with a hardware reader. - Visual feedback when a label matches an expected variant. - Audio feedback: a success sound on match, a failed-scan sound on miss. Operators can sign in (by name, or by PIN if you’ve assigned [operators] (/features/cloud-platform/operators-and-pins/)), scan in named runs, switch between standard and count-to-target modes, and keep scanning even when Wi-Fi drops; scans queue on the device and sync automatically, and aren’t lost on reload. See [Using the device] (/features/cloud-platform/using-the-device/) for the full operator walkthrough. ## Typical workflow A receiving operator at the warehouse: 1. Opens the Cloud Platform link on their tablet. 2. Scans the first incoming label. 3. The app says “match”: green tick plus success sound. Move to next. 4. A label doesn’t match: red mark plus failed-scan sound. Manually verify, contact supplier if needed. 5. Continue until the expected list is fully checked. ## What it’s not - Not a receiving flow into Shopify. Label Checker validates labels; the PO receiving flow (in Logistified admin) records what was actually received. - Not a stock counting tool. For stock takes, use [Inventory → Stock takes] (/features/inventory/stock-takes/). Note Label Checker is the first Cloud Platform action. Others will follow. ## See also - [Creating a session] (/features/cloud-platform/creating-a-session/): the setup flow. - [Sharing with the device] (/features/cloud-platform/sharing-with-device/): handing the link to the tablet. - [Using the device] (/features/cloud-platform/using-the-device/): the operator’s hands-on workflow. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/creating-a-session/ # Creating a session Pick scope, expiry, credentials, then generate the QR + URL. [Enhanced plan] (/reference/subscription-plans/) A Label Checking session in Logistified’s Cloud Platform is what a warehouse device opens to scan labels. You pick its name, length and credentials, then generate the QR code and URL that open it on the device. ## On this page - Where to start - Step-by-step - Editing a session - See also ## Where to start P&H Cloud Platform (Beta) → Label Checking → click “Create session” (top-right of the page). The button opens a two-step dialog: Details first, then View. ## Step-by-step 1. Set the session name. Pre-filled as LC-YYYY-MMDD-HHMM (date + time stamp). Override with anything that helps you find the session later. 2. Pick the session length (TTL). 1 hour, 8 hours, 24 hours (default), 7 days, Custom date, or No expiry (company device). Shorter is safer; the TTL is your time-bound security control. - Custom date reveals an Expiry date picker. Pick the last day the session should work and it stays usable through that whole day, expiring at 23:59:59 in your shop’s timezone (the one set on the Scanning day boundary card; see [The scanning day] (/features/cloud-platform/scan-statistics/#the-scanning-day)). The picker won’t accept a day in the past. - No expiry (company device) never auto-expires and lives until you revoke it manually: “recommended for a shared company device. Stays logged in and rolls days automatically.” It can only be chosen at creation, not when editing a session later. Custom date has no such restriction. 2. Choose whether target scans count toward the standard total. “Include target results in standard totals” is ticked by default, so scans made in target mode also count toward the plain running total shown to the operator and in reports. Untick it to keep the two separate; see [Scan statistics → Runs, and standard vs. target] (/features/cloud-platform/scan-statistics/#runs-and-standard-vs-target) for what that changes. This can also be changed later when editing the session. 5. (Optional) Assign operators (PIN gate). Under “Operators (PIN gate)”, tick which operators may scan this session. Pick one or more and each must enter their PIN on the device, and their scans are attributed to them; leave it empty and the session scans anonymously. Operators are defined in [Settings → Cloud Platform → Operators] (/features/cloud-platform/operators-and-pins/). 6. (Optional) Set access controls. Under “Optional access controls”, type a Username and/or Password. To have Logistified pick the password for you, tick “Auto-generate” next to the Password field: the input goes disabled, and on save a 12-character password is generated and shown to you once in an amber callout (“shown once: won’t be shown again”). Copy it then; it can’t be retrieved later. 7. (Optional) Set “Issued by”. An email address recorded against the session for audit purposes. Pre-filled with your Shopify login email. 8. Click “Next”. The dialog moves to the View step. 9. (Optional) Create an empty session. Tick “Create empty session” to issue a session with no products; operators add SKUs from the device later. Leave it unticked to build the expected list from a view (next step). 10. Pick the View. Choose an existing saved Forecast view: every variant in that view becomes the expected list, and the view is used as-is: its own filters and location are locked and shown read-only (pick “Create (new) custom filters” if you need to change them). Or pick “Create (new) custom filters” to build an ad-hoc filter on the spot; custom mode has its own optional Location selector (defaults to “All locations”). There’s no separate mandatory location step: location either comes from the saved view or is an optional filter in custom mode. The expected list isn’t practically capped. 11. Click “Generate QR code”. A “Resolving products” progress bar runs (empty sessions skip it), then the dialog lands on the issued state with the QR code, the URL, the scanning-day timezone, and (if you used Auto-generate) the one-time password. ## Editing a session Open the Settings icon on the session row to edit: - Rename. Change the session name. - Set a fresh TTL. Editing offers the timed windows and Custom date, but not “No expiry (company device)”; a session already set to “No expiry” stays that way unless you pick something else here (which downgrades it). Saving with a timed window resets expiry to now + the selected window; it does not add time onto the existing expiry. Saving with a Custom date sets expiry to 23:59:59 on the day you picked, in your shop’s timezone, and the date already on the session is shown so you can see what you’re changing. - Refresh products from source view. Only available for view-sourced sessions: re-evaluates the saved filter and rebuilds the session’s expected list with the current SKUs and barcodes. - Change operators. Add or remove operators from the session’s [PIN gate] (/features/cloud-platform/operators-and-pins/). Unlike credentials, the operator list can be changed after creation. - Change whether target scans count toward the standard total. Flip “Include target results in standard totals”; see step 3 under [Step-by-step] (#step-by-step) above. The Edit dialog also has a “Revoke session” button at the bottom-left (two-click confirm pattern). Caution If the session’s QR code was already printed or handed out, re-open View QR after switching it to Custom date and share the new code. A code shown before the change stops working 7 days after the session was created, whatever date you picked. Caution Auto-generated passwords are shown only once. Copy now or create a new session. Note Credentials are set once at creation. Edit doesn’t let you change the username or password, or add/remove auth on an existing session. To change credentials, create a new session. Note You can’t change a session’s underlying source (saved view vs. ad-hoc) or its location after creation. ## See also - [Sharing with the device] (/features/cloud-platform/sharing-with-device/): handing the link over. - [Revoking sessions] (/features/cloud-platform/revoking-sessions/): ending access early. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/sharing-with-device/ # Sharing with the device How a tablet or scanner gets into a Cloud Platform session: QR or URL. [Enhanced plan] (/reference/subscription-plans/) A tablet or scanner joins a Logistified Cloud Platform session through a QR code or a URL. This page covers both, and what the device does the first time and when it comes back. ## On this page - Two share methods - What the link is - First-time access - Returning to the device - Re-displaying the QR - See also ## Two share methods - QR code: scan from the device camera. Best for tablets. - URL: copy and paste, or send via DM / email. Best when devices can’t scan QRs. ## What the link is An opaque, encrypted, time-limited URL. The link itself contains no identifying information (no shop name, no action type). Cloud Platform decodes it server-side. ## First-time access If credentials are set: 1. Device opens the link. 2. Prompted for username + password. 3. On correct entry, the session starts. If no credentials are set: 1. Device opens the link. 2. Session starts immediately. ## Returning to the device The device caches the session in a cookie. Within the TTL, reopening the URL resumes without re-entering credentials. ## Re-displaying the QR The View QR icon (a scan-line icon) on the session row re-displays the QR code and URL for the same session (same session, same expiry). The URL keeps working until the session expires or is revoked. Caution Treat the URL as a credential. Anyone holding it (and any credentials, if set) can use the session. Don’t post it publicly. Note To give an operator more time, edit the session and pick a new TTL. The same URL keeps working, and the expiry resets to now + the new window; it does not add time onto the existing expiry. ## See also - [Revoking sessions] (/features/cloud-platform/revoking-sessions/): locking out a device. - [Plan gate] (/features/cloud-platform/plan-gate/): why the link is a bearer credential. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/using-the-device/ # Using the device What an operator sees and does on the Label Checker device: logging in, scanning runs, modes, adjusting counts, working offline, and installing the app. [Enhanced plan] (/reference/subscription-plans/) This page is the operator’s side of Logistified’s Label Checker: what your warehouse staff see once they open a session on a tablet or phone. Use it to understand the device workflow and to train operators. ## On this page - Logging in - Scanning - Runs - Standard vs. target mode - Adjusting counts - Working offline - Reviewing past days - Installing to the home screen - See also ## Logging in When the device opens a session, the first thing the operator does is identify themselves. There are three cases, depending on whether you’ve [assigned operators] (/features/cloud-platform/operators-and-pins/) to the session and which [sign-in mode] (/features/cloud-platform/operators-and-pins/#sign-in-mode) you’ve chosen: - With operators assigned, Name + PIN (the default). A “Who’s scanning?” screen asks the operator to pick their name and enter their 4-digit PIN, then tap Unlock scanning. - With operators assigned, PIN-only. There’s no name step; the operator enters their 4-digit PIN on the keypad and Logistified matches it to the right person automatically. On a correct PIN the device briefly shows “Welcome, Name” before scanning starts, so a mistyped PIN that happens to land on a colleague is caught right away. - Without operators (name only). The operator just types their name and taps Start scanning, no PIN. The PIN is always checked on the server, and wrong attempts are throttled: a run of wrong guesses locks scanning out for a short cooldown that grows the longer it continues, and the device tells the operator how long to wait. Either way, every scan is attributed to whoever is signed in. A badge in the corner shows their initials, with a Change operator option to hand the device to someone else. If you’ve set a [re-login timeout] (/features/cloud-platform/operators-and-pins/#the-pin-re-login-timeout), the PIN gate reappears after the device has been idle for that long. ## Scanning The operator points the camera at a barcode (or uses a hardware scanner). A match plays the [success sound] (/features/cloud-platform/sounds/) and adds to the on-screen tally; a miss plays the failed-scan sound. The tally lists each item with its running count. ## Runs A run is one batch of scanning: a box, a pallet, a delivery. The operator: - Taps Start run to begin. - Scans items into the run. - Taps Finish run to close it. A dialog confirms “N scan(s) will be saved to this run. The on-screen tally then clears for the next run.”, and lets them add an optional run name (e.g. “Box 12 / Pallet A”) and notes before Finish & save. Finishing a run is non-destructive; it’s saved, and the screen clears for the next batch. Each run appears separately in [Scan statistics] (/features/cloud-platform/scan-statistics/). ## Standard vs. target mode - Standard: straight label-checking against the expected list. - Target: counting toward a target quantity per item. Switching mode while a run is open prompts “Switch to … mode?” with three choices: Finish & save the current run, Keep open to park it and resume later, or Cancel. If a target session is already parked, entering target mode offers to Resume it or start a New session. When a target run finishes, a summary screen asks whether those target-mode results should also count toward the day’s standard totals (pre-checked to match the session’s own default), but the operator can flip it just for that finish. See [Scan statistics → Runs, and standard vs. target] (/features/cloud-platform/scan-statistics/#runs-and-standard-vs-target) for what that changes. ## Adjusting counts Each item row has a stepper: − / + to change the count by one, or tap the number to type an exact value. A trash icon removes a row from the tally. To start a batch over, the operator finishes the run and starts a fresh one. ## Working offline The device is built for unreliable warehouse Wi-Fi: - Scans keep working offline. Each scan is saved on the device and counted on screen immediately, then synced automatically when the connection returns (and periodically in the background). - Nothing is lost on reload. Scan data is stored on the server against the session, so reloading the page, reinstalling the app, or a dropped connection won’t wipe the tally. - If a sign-in expires mid-shift, an amber banner appears (“N scan(s) pending: sign in again to sync. Your scans are saved on this device.”) with a Retry sync button. The queued scans flush once the operator signs back in. Tip Because scans are stored server-side, an operator can safely close and reopen the session, or hand the device to a colleague, without losing the day’s counts. ## Reviewing past days From the device, the operator can open Run history to review earlier work. It opens to a list of days (the current (open) day first, then the rest newest-first): - Tapping a day shows that day’s runs, split into Standard and Target groups, plus a per-item tally for the day. - Tapping a run inside a day shows its totals, lets the operator edit the run’s name and notes inline, and offers Resume run for parked runs. - Each run shows a status: Active, Parked (open, resumable), or Finished / Auto-closed. - Past (closed) days are read-only; the current day updates live. - Occasionally a day shows scans with no runs of its own; a note explains that those runs started on an earlier day and links you there. A run that started on an earlier day and carries into this one is marked Carried over. - The operator can export (a whole day, one run, or several runs selected at once) as Full stats or Scanning history, CSV or Excel. This is the same activity, organized the same way, you can review and export from the admin in [Scan statistics] (/features/cloud-platform/scan-statistics/). ## Installing to the home screen The device app is installable. Using the browser’s Add to Home Screen (or the Android install prompt) adds it as a standalone, full-screen app named “Scanner”, no browser chrome, portrait orientation, ready to reopen with a tap. ## See also - [Operators & PINs] (/features/cloud-platform/operators-and-pins/): set up who can sign in. - [Scan statistics] (/features/cloud-platform/scan-statistics/): the admin view of the same scans. - [Sounds] (/features/cloud-platform/sounds/): the audio cues the operator hears. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/operators-and-pins/ # Operators & PINs Name your warehouse staff, give each a PIN, and gate sessions so scans are attributed to a person. [Enhanced plan] (/reference/subscription-plans/) By default a Logistified Label Checker session scans anonymously; anyone holding the link can scan, and scans aren’t tied to a person. Operators let you name your warehouse staff, give each a 4-digit PIN, and require a PIN to scan in a session. Every scan is then attributed to whoever entered the PIN. ## On this page - Managing operators - Adding and editing - Deleting an operator - Gating a session with operators - The PIN re-login timeout - Sign-in mode - See also ## Managing operators Settings → Cloud Platform → Operators tab. The list is searchable (by name, email, or employee number) and sortable by any column. Each operator has: - Employee number: optional. A numeric identifier for the operator, useful for teams that use staff IDs. Stored as entered (leading zeros are preserved). Operators without an employee number sort to the bottom of the list. - Name: required, and must be unique. - Email: optional. - 4-digit PIN: required; exactly four digits (0000–9999). Each active operator needs a distinct PIN: Logistified checks a new or changed PIN against every other active operator’s and blocks the save (“This PIN is already used by another operator. Choose a different PIN.”) if it clashes. The PIN is stored hashed and is never shown back to you. In the list it appears as •••• (set); you can replace it, but you can’t read it. ## Adding and editing - Add operator: click Add operator, enter an optional employee number, a name, an optional email, and a 4-digit PIN, then confirm. - Edit: the pencil icon. Change the employee number, name, email, or PIN. Leave the PIN field blank to keep the existing one (it shows •••• (unchanged)). When you change an operator’s PIN or name, Logistified immediately re-syncs every active session that includes them, so a changed PIN takes effect right away. You’ll see a Security sync confirmation telling you how many active sessions were updated (and flagging any that failed). ## Deleting an operator The trash icon, with a confirmation. Deleting an operator removes them from every active session’s PIN gate so they can no longer scan, but their past scan history keeps their name, so your records stay intact. Note Deleting is the way to take an operator offline. Their attribution on historical scans is preserved either way. ## Gating a session with operators When you [create] (/features/cloud-platform/creating-a-session/) or edit a session, an Operators (PIN gate) picker lets you choose which operators may scan that session: - Pick one or more operators: only those people can scan, and each must enter their PIN on the device. Scans are attributed to them. - Pick none: the session scans without a PIN gate (anonymous), the original behavior. Assigning operators is optional and independent per session. If you haven’t created any operators yet, the picker points you to the Operators tab. For a longer operator list, the picker adds a search box (by employee number, name, or email), a “Select all” checkbox that applies to whichever operators are currently visible (the full roster, or just your search matches) and a “Clear all (N)” action to empty the selection outright. A running “N of M selected” count sits below the list. If an operator is no longer shown (for example, they’ve since been deactivated) but was already selected, they stay selected even though they’re out of view. ## The PIN re-login timeout For sessions with operators assigned, the device stays unlocked for a while after a PIN is entered, then asks for the PIN again once the device has been idle. Configure how long under Settings → Cloud Platform → Label Checking → PIN re-login timeout: - Idle timeout (seconds): default 30 seconds, minimum 5 seconds. - Never re-prompt: the operator stays logged in until the page is reloaded or the session is revoked. - Update all active sessions immediately: apply the new timeout to sessions that are already issued, not just future ones. Note Operators, PINs, and the re-login timeout are part of the Enhanced Plan, like the rest of Cloud Platform. ## Sign-in mode Settings → Cloud Platform → Label Checking → Sign-in mode. By default, a session gated by operators uses Name + PIN: the operator picks their name, then enters their PIN. Switch to PIN-only and the device drops the name step; the operator types just their 4-digit PIN on the keypad, and Logistified matches it to the right person on its own. On a correct PIN the device briefly shows “Welcome, Name” before scanning starts, so a mistyped PIN that happens to match a colleague is caught immediately instead of silently attributing scans to the wrong person. The change applies to sessions already issued as well as new ones; there’s no need to reissue a session after switching modes. Caution PIN-only sign-in needs every active operator’s PIN to be unique. Logistified can’t check that retroactively; if two operators already share a PIN from before you turned the mode on, both are blocked from signing in until you change one of their PINs. Going forward, a duplicate PIN is blocked at save time (see above). ## See also - [Creating a session] (/features/cloud-platform/creating-a-session/): where you assign operators. - [Scan statistics] (/features/cloud-platform/scan-statistics/): see which operator ran which scans. - [Plan gate] (/features/cloud-platform/plan-gate/): what Enhanced unlocks. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/scan-statistics/ # Scan statistics Review what a Label Checker device scanned (by day, by run, down to the individual scan) and export it. [Enhanced plan] (/reference/subscription-plans/) Logistified records every scan an operator makes on a Label Checker device. Scan statistics is the admin-side view of that activity for one session (a drill-down from days, to the runs inside a day, to the individual scan log) with a CSV or Excel export at every level. ## On this page - Opening scan statistics - The three levels - The scanning day - Runs, and standard vs. target - Exporting - When it says “not available yet” - See also ## Opening scan statistics P&H Cloud Platform (Beta) → Label Checking → click the Scan activity icon (bar-chart) in a session row’s Actions column. ## The three levels Scan statistics is one page that drills down through three levels: 1. Day report: one row per day the session was used: Day · Runs · Scans · Matched · Unmatched · Open/Closed. Click a day to open it. 2. Day detail: that day’s totals (matched / unmatched; runs and scans each broken out standard vs. target) and a table of the runs inside the day, each with its operator. Click a run to open it. 3. Run detail: the run’s metric cards plus the scan log: one row per scan: Time · Outcome · SKU · Barcode · Product · Scanned. The log is paginated for long runs. The day a scan belongs to is assigned by the device at scan time, so the grid matches exactly what the operator saw on the device. Looking for one specific item instead of browsing by day? See [Item look-up] (/features/cloud-platform/item-lookup/). ## The scanning day A scanning day rolls over at your shop’s own local midnight (not a fixed universal time), so an evening shift’s scans land on the day your team actually worked, not the next one. Where the timezone comes from. It is a setting you own, on the Scanning day boundary card in Settings → Cloud Platform → Label Checking. The first time you open that tab, Logistified fills it in from your Shopify store’s timezone; from then on you can change it with the searchable picker (or reset it to your Shopify value with Use Shopify’s). Every new session picks up whatever is stored. If nothing is stored yet, the card says so and scanning days roll at UTC midnight until you pick a zone. Changing it later. Click Save and the new zone is stored and pushed onto every session that is already issued: no reissue needed. (Already saved and just want live devices to pick the stored zone up again? Use Re-apply to active sessions under the picker.) Each device adopts the change at its next day roll, so the day of the switch runs a little long or short just that once. Days already recorded keep the dates they were recorded under. ## Runs, and standard vs. target A run is a continuous stretch of scanning within a day; an operator can start a fresh run, and a run still open at the end of the day is finished automatically at day close. Each run is in one of two modes: - Standard: straight label-checking against the expected list. - Target: counting toward a target quantity. By default, target-mode scans also count toward the plain running total, on the device and in the daily [scan report] (/features/cloud-platform/scan-reports/) email. Untick “Include target results in standard totals” when [creating] (/features/cloud-platform/creating-a-session/) or editing a session to keep them separate instead: the device’s on-screen tally and the scan-report email then split standard and target into two totals rather than merging them. ## Exporting Every level offers a complete download (the whole day (all its runs) down to a single run) in CSV or Excel (.xlsx): Level Where What you get Day report per-row Export menu the whole selected day Day detail Download day menu (header) + per-run menu the whole day, or one run Run detail Export run menu that run The export is always the full scan log for the chosen scope; it is not limited to the page you’re looking at. Each row carries the day, run, mode, operator, time, outcome, SKU, barcode, product, and scanned quantity. ## When it says “not available yet” Scan statistics reads the scan history back from the device platform. If the page shows “Scan statistics not available yet”, the platform side isn’t live for your shop yet; this is expected before the feature is fully rolled out, and the page degrades gracefully rather than erroring. Note Scan statistics is read-only; it reflects what was scanned, and never changes inventory. ## See also - [Item look-up] (/features/cloud-platform/item-lookup/): search for one item’s scan history instead of browsing day by day. - [Scan reports] (/features/cloud-platform/scan-reports/): get this activity emailed on a schedule. - [Operators & PINs] (/features/cloud-platform/operators-and-pins/): attribute scans to a named operator. - [Label Checker] (/features/cloud-platform/label-checker/): where the scans happen. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/item-lookup/ # Item look-up Scan or type a barcode or SKU to see how many times it's been scanned, and when, within one Label Checker session. [Enhanced plan] (/reference/subscription-plans/) Item look-up in Logistified’s Cloud Platform answers one question: how many times has this item been scanned, and when? Scan a barcode or type a SKU and get a day-by-day breakdown for one label-checking session, useful for planning future production runs or auditing a specific item’s activity. ## On this page - Opening item look-up - Searching - Reading the results - Exporting - Scope: one session at a time - See also ## Opening item look-up Item look-up lives on the same page as [Scan statistics] (/features/cloud-platform/scan-statistics/): P&H Cloud Platform (Beta) → Label Checking → the Scan activity icon in a session row’s Actions column. The Item look-up card sits at the top of the day report, and stays visible once you’ve run a search. ## Searching - Barcode or SKU. Scan the item with a hardware scanner, or type the code, into the search field and press Enter (or click Search). Toggle Barcode / SKU to tell Logistified which one you’re entering. - Date range. Use a preset (This week, This month, This year, All time) or set custom From / To dates. Leaving the range open searches the whole session. ## Reading the results - Summary tiles: total scans, successful scans, days with any scans, and unmatched scans (scans of that code that didn’t match anything in your catalog; see below). - Item identity: the matched product’s name, SKU, and barcode, plus the timestamps of the first and last scan in range. If the same code is shared by more than one item in your catalog, results are split into a per-item table instead of being combined. - Per-day table: one row per day with any activity, showing scans and successful scans, plus a Total row. Days with zero scans in the range are shown too, so gaps are visible rather than hidden. Note Unmatched scans (a code that didn’t match anything in your catalog) are called out separately and are never folded into the totals; an item’s real count should never look inflated by scans it didn’t actually get. ## Exporting Export CSV downloads the results currently on screen: the per-day breakdown and the per-item split, if there is one. ## Scope: one session at a time Item look-up only searches within the session you opened it from. Scans made in a different label-checking session live in that session’s own history and aren’t included; search each session separately if you need the full picture across more than one. Item look-up keeps working even after a session has expired or been revoked, so you can still audit what it scanned after the fact. ## See also - [Scan statistics] (/features/cloud-platform/scan-statistics/): browse the same session’s activity by day and run instead of by item. - [Scan reports] (/features/cloud-platform/scan-reports/): get daily activity emailed on a schedule. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/scan-reports/ # Scan reports Email a daily CSV of a session's label-checking activity to the recipients you choose. [Enhanced plan] (/reference/subscription-plans/) In Logistified’s Cloud Platform, a scan report is a once-a-day email summarising a label-checking session’s scans, with a CSV attached. Set one up per session and pick who receives it. ## On this page - Where to configure - Setting up a schedule - What the email contains - Sending a test - Things to know - See also ## Where to configure Settings → Cloud Platform → Scan Reports tab. Schedules are per session; each label-checking session has its own. ## Setting up a schedule 1. Session: pick the label-checking session to report on. 2. Send time (UTC): the time of day the report is emailed, in UTC (default 08:00). The picker is always UTC, so allow for your local offset. 3. Recipients: tick who should receive it. The list comes from Settings → Recipients, so add recipients there first if the list is empty. 4. Click Enable daily report (or Update schedule if one already exists). To turn it off, click Disable. You need at least one recipient selected before the schedule can be enabled. ## What the email contains - Subject: Label-checking scan report: YYYY-MM-DD - Body: a short cover note naming the session and date. - Attachment: a CSV of that day’s scans aggregated per SKU: the SKU, barcode, product, scan mode (standard/target), and counts. It ends with a summary: if the session has “Include target results in standard totals” on (the default; see [Scan statistics → Runs, and standard vs. target] (/features/cloud-platform/scan-statistics/#runs-and-standard-vs-target)), the summary is one merged total; if it’s off, the summary shows two subtotals instead, one for standard and one for target. The scheduled email always covers the most recently completed day, not the day in progress. Days are bucketed by the device’s recorded scan time, so a scan made just before midnight counts on the day it happened even if it synced after midnight. ## Sending a test Send test now emails the report immediately to the selected recipients, using the current day’s scans (including ones still coming in). It doesn’t change the schedule or the real daily send; it’s just a preview. ## Things to know - Needs recipients. Configure them under [Settings → Recipients] (/features/settings/recipients/) first. - Needs scan data. If the session has no completed day yet, the scheduled send is skipped (no empty email) and a test reports that there’s nothing to send. - Revoked sessions stop automatically. If you revoke a session, its schedule stops: no orphan emails. - One email per day. A given day is only sent once, even if the scheduler runs more than once. Note Scan reports require the Enhanced Plan. ## See also - [Scan statistics] (/features/cloud-platform/scan-statistics/): the same data, browsable on demand. - [Settings → Recipients] (/features/settings/recipients/): where recipients are managed. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/revoking-sessions/ # Revoking sessions Ending Cloud Platform session access early. [Enhanced plan] (/reference/subscription-plans/) Revoking a Cloud Platform session in Logistified ends a device’s access before the session expires. ## On this page - What “revoke” means - How to revoke - Propagation time - Revoke vs. expiry - The session list - See also ## What “revoke” means Marks the session as revoked. Any device that hits the URL after revocation is rejected. ## How to revoke There’s no session detail page; revoke is reachable two ways from the Label Checking table: - Inline (fastest). P&H Cloud Platform (Beta) → Label Checking → click the PowerOff icon in the row’s Actions column → confirm in the “Revoke this session?” dialog. - From Edit. Click the Settings icon on the row → click “Revoke session” at the bottom-left of the Edit dialog → click again to confirm (two-click pattern). ## Propagation time The admin UI tells the operator the link stops working immediately. In practice it can take up to ~30 seconds because the Cloud Platform side caches session reads for 30s, usually much faster. ## Revoke vs. expiry Both end the session. Revoke is for “lock out now”; waiting is for “let it expire naturally.” ## The session list Two tabs: - Active: sessions currently usable (within TTL, not revoked). - All: every session including expired and revoked. Useful for audit. Note A revoked session can’t be unrevoked. Create a new session instead. Caution If a device is compromised, revoke immediately. The 30-second propagation is the worst case; usually it’s much faster. ## See also - [Creating a session] (/features/cloud-platform/creating-a-session/): the setup that gets revoked. - [Plan gate] (/features/cloud-platform/plan-gate/): why TTL is the security model. Last updated: 19 November 2026 --- Source: https://docs.logistified.app/features/cloud-platform/sounds/ # Sounds Per-shop audio feedback for Cloud Platform devices: success and failed-scan sounds. [Enhanced plan] (/reference/subscription-plans/) Logistified’s Cloud Platform devices can play a sound for each scan: one when it matches, one when it fails. The sounds are set per shop, and you upload them yourself. ## On this page - What the device plays - No defaults: bring your own - Uploading sounds - Where files are stored - See also ## What the device plays Two audio cues: - [Success sound] (/reference/glossary/#success-sound): when a scanned label matches an expected item. - [Failed-scan sound] (/reference/glossary/#failed-scan-sound): when it doesn’t (no match, or a duplicate scan). [anchor: no-defaults--bring-your-own] ## No defaults: bring your own If no sound is uploaded, the device plays nothing: silence on both match and miss. Upload a success sound and/or a failed-scan sound to get audio feedback. ## Uploading sounds Settings → Cloud Platform → Label Checking tab. There are two upload cards: Success sound and Failed-scan sound. Each card is a drag-and-drop zone; drop a file on it or click “browse files”. After upload, the card shows the filename, size, an