Inventory management is a core part of the CORESense Connect™ Retail (CORESense). This section is designed to provide a high-level overview of inventory management within the system.
The following are the basic principles of inventory management in CORESense:
Every SKU has a Default Fulfillment Type (aka Build Type in the dBase). The Default Fulfillment Type can be Stock Inventory, Just-In-Time or Drop Ship. It is used by inventory sourcing automation and, by default for manual sourcing, to determine how to source the inventory during order fulfillment.
Stock Inventory is stored in inventory locations. An inventory location is defined as a warehouse or store and optionally, a sub-location as defined by the warehouse's topology. A typical warehouse topology would include aisle, rack, shelf and bin.
Vendor available inventory is used to determine the quantity if inventory available for Just-in-Time (JIT) or Drop-Ship Fulfillment. The Vendor Stock Type can be limited with the quantity available import manually or via scheduled data feed or unlimited.
Stock Inventory can be added in CORESense in a number of ways:
Stock Inventory can be added in CORESense in a number of ways:
Every change in inventory is recorded as an inventory transactions. Inventory Transaction reports are available from the SKU record in the Inventory Manager and from Accounting>Inventory Transactions Report.
In CORESense, a Warehouse represents a location where inventory is stored, like a stock room, retail store, or a physical warehouse. They are associated with an address, which is generally the postal address for the purpose of shipping goods to and from that warehouse. Warehouse are created and managed using the Warehouse Manager.
A warehouse can be designated as available for fulfillment, backorder or for pickup and they can be assigned a fulfillment priority by sales channel to be used in multi-warehouse scenarios.
CORESense supports the creation of multiple warehouses and each warehouse can, optionally, have its own internal sub-location topology. Sub-location topologies can be defined up to 4 levels, typically:
All Warehouses are associated with a location and locations are organized into a Location Hierarchy of up to 4 levels, typically:
Finally, warehouses an be designated as a centralized distribution center or as fulfilled by a centralized distribution center.
Central Distribution allows you to designate a warehouse as the source of fulfillment for other warehouses. A central distribution warehouse receives all purchased inventory and then transfers that inventory to other warehouses or stores as inventory reorder points are reached.
Inventory can be Transferred using between and within warehouses and sub-locations in a number of ways:
Grid Transfer Builder - Used for Grid Products. e.g. apparel, footwear that have been set up using CORESense Grid functionality.
Standard Transfer Builder - Used for Transfer of individual SKU's typically associated with Non-Grid ir simple products.
Barcode Transfer Builder - Scan SKU via barcode label into the transfer.
Overstock Transfer Builder = Move inventory from non-pickable locations to pickable locations base on Default Pick Location settings. Non-pickable locations are those 'not available for fulfillment.'
See Transfers Overview for more information building and managing transfers.
Purchase orders can created in CORESene using the Purchase Order Builder or via data import and then from the CORESense to your vendors using print/fax/mail, email delivery or EDI. CORESense supports multiple vendors per SKU, case sizes, purchasing levels and incentives. One vendor is set as the default vendor to used in JIT and Drop-Ship Fulfillment as well as reordering automation.
Purchasing information (shipment method, purchase order delivery method, document or email template, cost, terms, etc.) can set globally or per vendor allow for pre-population of purchase order data when creating purchase order manually or through production or reordering automation.
Goods can be received into a warehouse against a purchase order by creating and completing a receiver. Receivers can be created entering an EDI ASN or Advance Shipping Notice. The receiver will display the items on the purchase order and allow for recording receipt in multiple ways.
Received items can be stocked into their default sub-locations or, optionally, a different sub-location selected during receiving. Items received but not on the Purchase Order can be added and received into stock as well. Finally, items will be received at their purchase cost or, optionally a different cost, entered during the receiving process.
See Purchasing Overview for more information.
Reordering Automation allows for the automated replenishment of stock inventory from a designated Distribution Center or the default SKU Vendor. Reordering automation runs daily and adds SKUs to existing purchase orders or creates a new purchase if none exists. Replenishment Purchase Orders are visible in the Purchase Order Queue where they can be edited and transmitted to the vendor.
A Physical Inventory Count Project can be created to count inventory in one or more locations or sub-locations in a warehouse and, optionally, by Merchandise Hierarchy (Department, Class, Subclass) and/or Vendor. One or more counts can be taken manually or by barcode scanning, entered into CORESense and reconciled against the count in CORESense.
© 2023 CORESense · info@coresense.com · 125 High Rock Avenue, Saratoga Springs, NY 12866