The Products section in Starshipit WMS is where you define how each SKU behaves in the warehouse. This configuration controls how stock is received, tracked, allocated and picked.
When you first set up Starshipit WMS, you will typically:
- Sync products from your existing Starshipit account
- Review and adjust product settings for bundles, units of measure and tracking
- Choose an allocation strategy per product
Getting product configuration right up front helps avoid receiving errors, allocation failures and unnecessary manual work later.
Syncing products from Starshipit
Starshipit WMS connects to your Starshipit account to pull in product data so you do not have to recreate your catalogue from scratch.
- Go to the Products section in Starshipit WMS.
- Use the Sync products action to import products from Starshipit.
- Once the sync is complete, you will see your SKUs listed with their basic details. From here you can configure WMS-specific options such as bundles, tracking types and allocation rules.
After the initial sync, products can be kept up to date by running further syncs or by editing individual records directly in WMS.
Importing multiple products at once
When importing products from a dialog, you can enter comma-separated SKUs to import multiple specific products at once, rather than importing one at a time.
Importing products from Shopify
If you have a Shopify store connected to your Starshipit account, you can import products directly from Shopify using the Shopify Sync dialog. Selectable fields include SKU, name, image, barcode, price, weight, HS code, country of origin and Shopify IDs. A live progress bar shows import status.
When syncing from Shopify, the system also captures HS codes and country of origin data from the Shopify product record.
Product records and core fields
Each product in WMS has a set of core fields used across inbound, stock management and outbound flows.
- SKU – the unique code for the product (must match your ecommerce/Starshipit SKU).
- Name – human-readable product name.
- Barcode – product barcode for scanning during picking, packing and stocktake.
- On hand / Available / Committed / Incoming – inventory metrics shown in the inventory dashboard. Committed represents stock reserved for pending orders. Available is the quantity that can still be allocated (On hand minus Committed).
- Bundle configuration – whether the SKU is a bundle and how it should be fulfilled.
- Unit of measure setup – parent/child relationships for cartons vs eaches, etc.
- Tracking type – Standard (none), Batch or Serial.
- Allocation strategy – FIFO, LIFO, FEFO or LEFO.
You can edit these settings from the product detail page in WMS. Changes affect how future stock movements and orders behave, so it is best to review them carefully during onboarding.
Bundle products
Starshipit WMS supports bundle or kit SKUs made up of other SKUs. These are configured as bundle products and can be handled in two ways:
| Exploding bundles | Require stock bundles | |
|---|---|---|
| How it works | Breaks down into component SKUs when an order is processed | Bundle SKU has its own inventory that must be on hand |
| Inventory tracking | At component level | At bundle level |
| Picking | WMS picks individual component SKUs | WMS picks the bundle SKU directly |
| Kitting | Components assembled at fulfilment | Pre-built kits stored on shelf; kitting jobs create bundle stock |
| Best for | Never store pre-made kits, always pick components | Keep pre-built packs on shelf and track as separate inventory |
Parent/child SKUs and units of measure
WMS allows you to link products in parent/child relationships to represent different units of measure for the same item. For example:
- A case of 24 could be the child
- A single unit could be the parent (what the inventory is ultimately tracked in)
Each child SKU stores:
- Its own SKU and description
- A conversion factor (for example, 24 eaches per case)
Inventory is tracked at the child SKU level, while transactions can be recorded in any defined unit. This is useful when:
- You purchase in cartons or pallets
- You sell in smaller units (e.g. eaches or inner packs)
- You want consistent visibility of the same underlying stock
Tracking types
Each product can be configured with one of three tracking types. This controls what information is required during receiving, stocktake and picking.
| Tracking type | Description |
|---|---|
| Standard | Inventory is tracked purely by quantity. The system does not require or store any batch or serial identifiers. Use this for products where it is enough to know how many you have, not exactly which units. |
| Batch | Records stock by lot or batch. Common examples include food and beverage with expiry dates, cosmetics and pharmaceuticals, and manufactured goods requiring traceability. WMS will prompt for a batch/lot number during receiving, optionally capture an expiry date, and show stock at the level of product + batch + location. |
| Serial | Each individual unit is uniquely identified by a serial number. WMS will require one serial number per unit during receiving, prompt for serials during picking/packing, and track movements per serial for a detailed audit trail. |
Allocation strategies
Allocation strategies define which specific stock is reserved first when orders are released. You can configure this per product to match your operational and compliance needs.
| Strategy | Description |
|---|---|
| FIFO (First In, First Out) | Allocates the oldest stock first, based on when it entered the warehouse. This is typically the default setting and suits most non-perishable products. |
| LIFO (Last In, First Out) | Allocates the newest stock first. Useful in specific operational scenarios where newer stock is more accessible or preferred. |
| FEFO (First Expiry, First Out) | Allocates stock with the earliest expiry date first. Commonly used with batch-tracked products to reduce write-offs due to expired stock. |
| LEFO (Last Expiry, First Out) | Allocates stock with the latest expiry date first. A specialised option for when you intentionally want to ship the longest-dated stock first. |
The chosen allocation strategy is used when orders are released. WMS looks at the available stock (including batch and expiry where applicable) and reserves the correct units according to that rule.
Product lookup and management
Looking up products by barcode
On both the Inventory and Products pages, you can look up products by scanning or entering a barcode. This supplements the existing SKU and name search and is useful for quickly finding a product on the warehouse floor.
Cloning a product
A Clone action button is available on the products list. This creates a copy of an existing product with all its settings, allowing faster creation of similar products. You can then edit the cloned product to change the SKU, name and any other fields that differ.
Bulk editing products
You can select multiple products and open a Bulk Edit dialog to update fields across all selected products at once. This currently supports updating the Country of Origin field in bulk, and is useful when preparing products for international shipping compliance.
CSV stock on hand report
An Export SOH Report action on the inventory dashboard generates a CSV file of current stock-on-hand levels across all products and locations. This is useful for reporting, reconciliation with finance systems, and sharing stock data with external partners.
Best-practice configuration
- Decide tracking rules per product family.
For example, all perishable items use Batch + FEFO, all electronics use Serial + FIFO, and accessories use Standard + FIFO. - Keep bundles simple where possible.
Use exploding bundles when you never hold pre-kitted stock. Use require-stock bundles when you do and want kitting to be a planned activity. - Align units of measure with purchasing and selling.
Set up parent/child SKUs so receiving, storage and selling match how you operate day to day. - Test with a small subset first.
Configure a small group of high-volume SKUs, run through a full inbound and outbound cycle, and only then roll out to the full catalogue.
FAQ
No. Bundles are optional. If you do not sell kits or sets, you can leave all products as standard SKUs.
Yes, but changing tracking type after stock has been received can cause extra work. It is best to decide tracking requirements before you start using WMS in production, especially for regulated or perishable items.
Orders will still allocate, but not in the way you expect (for example, newer stock may be used before older stock). If you update the allocation strategy, it will apply to future allocations. Existing allocations are not automatically reallocated.
For exploding bundles, stock is tracked at the component level and bundle availability is derived from components. For require stock bundles, the bundle SKU has its own on hand quantity and behaves like a normal product.
It is recommended to use distinct barcodes for each unit of measure to avoid confusion during scanning. If you must share a barcode, ensure your processes clearly distinguish which unit is being picked or received.
Yes. If you have a Shopify store connected to your Starshipit account, you can import products directly from Shopify using the Shopify Sync dialog. This also imports HS codes and country of origin data from Shopify.
Yes. On both the Inventory and Products pages, you can scan or enter a barcode to find a product. This works alongside the existing SKU and name search.