Stock can look fine in one location and fail in another when transfers and repack mappings are not controlled.<\/p>\n
When that happens, businesses face:<\/p>\n
This workflow is built to protect operational control.<\/p>\n
If repack mappings are enabled, child packs are sellable when the system can resolve a valid parent stock route and enough effective parent stock exists on that route.<\/p>\n
That gives owners more peace of mind, but it is not magic. Good setup and disciplined transfer completion still matter.<\/p>\n
dynamic<\/code> uses the sale location as parent source<\/li>\nfixed<\/code> uses a specific parent stock location<\/li>\n- Mapping priority is set intentionally (lowest priority number is checked first)<\/li>\n
- Ratio (
parent_qty_per_child_unit<\/code>) is valid and greater than zero<\/li>\n- Safety buffer is set where needed to protect minimum parent stock<\/li>\n
- Transfer locations (Warehouse, Packing Room, Department) already exist<\/li>\n
- Team permissions for stock transfer create\/update\/complete are assigned<\/li>\n<\/ul>\n
Steps<\/h2>\n\n- Confirm route design before operations start.<\/li>\n<\/ol>\n
Use dynamic routes where each branch should depend on its own parent stock. Use fixed routes where one warehouse must control parent stock for many selling points.<\/p>\n
\n- Set priority and ratio correctly for each child variation.<\/li>\n<\/ol>\n
The resolver checks routes by priority first, then mapping ID. The first valid route is used at sell time.<\/p>\n
\n- Create Warehouse -> Packing Room transfer.<\/li>\n<\/ol>\n
Set products, quantities, and correct variations. Keep status in pending<\/code> or in_transit<\/code> until physical receipt is confirmed.<\/p>\n\n- Complete transfer only after physical receipt.<\/li>\n<\/ol>\n
Stock moves in ledgers only when transfer is completed.<\/p>\n
\n- Record repack conversion in Packing Room.<\/li>\n<\/ol>\n
Reduce parent\/bulk variation and increase child\/sellable variation correctly. Do not convert above parent availability.<\/p>\n
\n- Create Packing Room -> Department transfer for sellable units.<\/li>\n<\/ol>\n
Transfer only finished sellable units to departments that will sell.<\/p>\n
\n- Mark department transfer as completed on physical receipt.<\/li>\n<\/ol>\n
This is what makes department-level sellability reliable.<\/p>\n
\n- Run daily control checks.<\/li>\n<\/ol>\n
Review transfer backlog, mismatch report, and stock movement exceptions before close of day.<\/p>\n
How sellability is decided<\/h2>\n
For repack-enabled businesses, the system decides child sellability using these checks:<\/p>\n
\n- Mapping exists for the child variation<\/li>\n
- A valid route resolves (dynamic or fixed)<\/li>\n
- Ratio is valid and greater than zero<\/li>\n
- Parent variation and parent location are valid<\/li>\n
- Effective parent stock is enough:<\/li>\n
effective_parent_stock = parent_qty - safety_buffer<\/code><\/li>\n- requested child qty is converted to parent consumption using ratio<\/li>\n<\/ul>\n
Important edge cases:<\/p>\n
\n- Parent stock may exist but child can still fail if route is invalid<\/li>\n
- Parent stock may exist but child can still fail if safety buffer leaves insufficient effective stock<\/li>\n
- Parent stock may exist but child can still fail if selected parent location does not match resolved route<\/li>\n<\/ul>\n
Scope note:<\/p>\n
\n- This guide is verified for POS and direct sale transfer workflow.<\/li>\n
- Other channels can behave differently depending on flow configuration.<\/li>\n<\/ul>\n
Real live scenarios<\/h2>\n\n- Multi-branch distributor (fixed parent warehouse).<\/li>\n<\/ol>\n
A Lagos warehouse is the fixed parent source. Branch sells only after completed transfer and valid resolved route. This prevents branch teams from assuming parent stock can always be sold locally.<\/p>\n
\n- Repack-heavy health brand (dynamic route by branch).<\/li>\n<\/ol>\n
Each branch repacks and sells from its own local parent stock. Dynamic route keeps branch autonomy while still enforcing ratio and buffer control.<\/p>\n
\n- POD-heavy team with temporary transfer backlog.<\/li>\n<\/ol>\n
Orders spike, but transfer is left in pending<\/code>. Goods are physically moved, yet system availability is still low. Completing transfer clears the gap and restores trust in available quantities.<\/p>\n\n- Staff enters wrong variation during transfer.<\/li>\n<\/ol>\n
Quantity moved physically, but wrong SKU\/variation was completed. Department appears short. Daily mismatch check catches it early and team recreates the correct transfer.<\/p>\n
\n- Online spike during low parent buffer.<\/li>\n<\/ol>\n
Parent stock is present, but safety buffer protects minimum reserve. Child sale is blocked before oversell. Team either replenishes parent stock or adjusts approved buffer policy.<\/p>\n
\n- Founder audit week after recurring disputes.<\/li>\n<\/ol>\n
Founder reviews transfer completion discipline, stale in-transit records, and mismatch trends. Within a cycle, transfer errors drop and weekly control reports become cleaner.<\/p>\n
Founder peace-of-mind outcomes<\/h2>\n
When this workflow is followed consistently, founders usually gain:<\/p>\n
\n- Fewer stock surprises across branches<\/li>\n
- Faster decision-making during demand spikes<\/li>\n
- Better confidence that staff actions are traceable<\/li>\n
- Better customer availability planning by location<\/li>\n
- Lower operational noise from repeated transfer disputes<\/li>\n<\/ul>\n
These are operational outcomes, not guaranteed promises.<\/p>\n
Common mistakes<\/h2>\n\n- Assuming child stock is always sellable because parent stock exists somewhere<\/li>\n
- Running multiple routes without intentional priority<\/li>\n
- Using invalid ratio values<\/li>\n
- Ignoring safety buffer impact<\/li>\n
- Leaving transfers in
pending<\/code> after physical receipt<\/li>\n- Completing transfer with wrong variation<\/li>\n
- Bypassing conversion logs in packing room<\/li>\n<\/ul>\n
Verification checklist<\/h2>\n
Before completion:<\/p>\n
\n- [ ] Correct source and destination locations selected<\/li>\n
- [ ] Correct parent\/child variation selected<\/li>\n
- [ ] Ratio and safety buffer are valid for mapped items<\/li>\n
- [ ] Quantity entered matches physical movement<\/li>\n<\/ul>\n
After completion:<\/p>\n
\n- [ ] Source stock reduced as expected<\/li>\n
- [ ] Destination stock increased as expected<\/li>\n
- [ ] Department sellability reflects completed transfer<\/li>\n
- [ ] No unresolved mismatch is left for end-of-day<\/li>\n<\/ul>\n
Weekly owner check:<\/p>\n
\n- [ ] Stale in-transit transfers are near zero<\/li>\n
- [ ] Repeat mismatch root causes are tracked and reduced<\/li>\n<\/ul>\n
Escalation<\/h2>\n
Escalate when any of these persist after first checks:<\/p>\n
\n- Route resolves as mapped but child still cannot sell<\/li>\n
- Transfer is completed but destination does not reflect stock<\/li>\n
- Repeated variation mismatch from same staff or same route<\/li>\n<\/ul>\n
Send support:<\/p>\n
\n- Transfer ID<\/li>\n
- Child variation and mapped parent variation<\/li>\n
- Sale location and resolved parent location (if known)<\/li>\n
- Requested qty vs available qty seen<\/li>\n
- Screenshot of transfer status and stock detail<\/li>\n<\/ul>\n
Related workflow links<\/h2>\n\n- Fixing Stock Mismatches (Daily Reconciliation)<\/a><\/li>\n
- End-of-Day Sales Reconciliation<\/a><\/li>\n
- Founder Weekly Control Reports<\/a><\/li>\n<\/ul>\n
CTA<\/h2>\n
Book Operations Fit Call<\/a><\/p>\nView Pricing<\/a><\/p>\nLast reviewed<\/h2>\n
2026-02-23<\/p>\n","protected":false},"excerpt":{"rendered":"
How to Transfer Stock Between Warehouse, Packing Room & Departments (Without Losing Track) Problem Stock can look fine in one location and fail in another when transfers and repack mappings are not controlled. When that happens, businesses face: Out-of-stock surprises at the sales desk Customer frustration from unavailable packs Founder stress from numbers that cannot … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"doc_category":[8],"doc_tag":[],"class_list":["post-61","docs","type-docs","status-publish","hentry","doc_category-multi-location-operations"],"year_month":"2026-05","word_count":1019,"total_views":"91","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"IGFirstERP","author_nicename":"igfirsterp","author_url":"https:\/\/igfirst.com.ng\/resources\/author\/igfirsterp\/"},"doc_category_info":[{"term_name":"Multi-Location Operations","term_url":"https:\/\/igfirst.com.ng\/resources\/docs-category\/multi-location-operations\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/docs\/61","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":12,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/docs\/61\/revisions"}],"predecessor-version":[{"id":224,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/docs\/61\/revisions\/224"}],"wp:attachment":[{"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/doc_category?post=61"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/igfirst.com.ng\/resources\/wp-json\/wp\/v2\/doc_tag?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}