Inventory¶
Jumpmind Commerce Inventory is built as a Micro-capability and supports the following functions:
- Shipping
- Receiving
- Adjustments
- Ticket Printing
- Store Counts
POS Integration¶
Enable the Inventory micro-cap in the POS by adding a button to the POS interface which will remotely load the Inventory module into the client app.
| button_group_id | button_id | button_name | button_type | button_value | enabled |
|---|---|---|---|---|---|
| home | LaunchInventory | key:home:home.inventory | action | LaunchInventory | 1 |
The following application-*.yml parameters govern technical behavior for the Inventory module:
| Key | Purpose |
|---|---|
| openpos.micro-caps.configs.inventory.server-url | names the URL of the server hosting Inventory services when running in Integrated mode |
| openpos.micro-caps.configs.inventory.remote-entry | names and locates the script invoked to serve the Inventory micro-cap when accessed from another application |
Remote Service Config¶
The Inventory micro-cap may need to invoke Commerce services published by external modules. These services will need to be configured in the
appropriate application.yml file so they may be located by the dependent Inventory function at runtime:
| Inventory Feature | Service Required | Configuration Key |
|---|---|---|
| Ticket Printing | Item | openpos.services.specific-config.item |
Integrated Data¶
The following tables are used by all Inventory functions:
| Table | Purpose |
|---|---|
jmci_itm_item |
merchandise items which can be operated on by inventory functions. Sync'd with itm_item |
jmci_itm_item_id |
supplier-assigned IDs for items; e.g. UPCs Sync'd with itm_item_id |