# NG WMS — full text NG WMS runs goods from an announced receipt to loading: every pallet has a location, lot and expiry are recorded from the first scan, and every line is checked before dispatch. Accurate stock, fewer delivery errors — and NG Copilot to answer questions about your goods, with AI agents that keep up with the routine and propose the next step. Publisher: Konis Software Doo, Beograd, Serbia. Contact: office@konissoftware.com. ## NG Copilot, AI agents and MCP: an AI that knows where the goods are — and what is late AI built into NG WMS. Shift leads, sales and management ask in their own words and get an answer with the document it is based on, while AI agents keep up with the warehouse routine and prepare proposals for confirmation. - AI agents for the warehouse routine: Shift overview, dispatch blockers, pick-face replenishment, count variances, expiry dates and the ERP exchange — on a schedule or on an event, always as a proposal that waits for a person. - Answers from your warehouse: Stock, lots, expiry dates, orders and waves — without custom reports and without calling the warehouse. - Blockers before the truck: Orders waiting for stock, empty pick locations and goods waiting for put-away come to light in time. - Proposals a person confirms: Copilot proposes replenishment, a priority or a check; the task is created only after confirmation, with a trail. - MCP for your team’s AI tools: AI assistants connected through the MCP server work with the same data, under the same user permissions. ## What you get with NG WMS - A clear split: the ERP keeps the books, purchasing and invoicing; NG WMS runs the goods and sends it verified data. - One system for multiple warehouses and goods owners, with rules per item, location and document. - NG Copilot, AI agents and MCP on the same data and under the same permissions — AI that follows your rules. - A rollout on your own flows of goods: receiving, picking and dispatch are configured to your warehouse. ## FAQ Q: What is NG WMS? A: NG WMS is a warehouse management system with an AI assistant: receiving, outbound with picking waves and a control and packing station, stock and pick-face replenishment, cycle counts, a warehouse model with a 2.5D view, labels, kitting, a scanner app, reports and traceability, NG Copilot with AI agents and an MCP server, and an ERP connection through an API. Q: Does NG WMS have AI? A: Yes. NG Copilot is the AI assistant built into NG WMS: it answers questions about stock, orders and waves with the document the answer comes from, flags dispatch blockers and proposes replenishment. AI agents keep watch over the shift, dispatch, replenishment, counts and expiry dates on a schedule or on an event and prepare proposals for confirmation, and through the MCP server your team’s AI assistants work with NG WMS too, under the same permissions. Q: How does an NG WMS rollout start? A: With a demo on your own flows of goods. We then set up the warehouse model, items and rules together, connect your ERP and prepare the warehouse team to work with scanners. Q: How much does NG WMS cost? A: We prepare an offer after the demo, based on your warehouse, your flows of goods and the connections to your other systems. Q: Does NG WMS connect to our ERP? A: Yes. The connection runs through API clients, webhooks and an outbox with message retries, and the data mapping is configured for your ERP. Every message stays in the log, so the exchange can be monitored and checked. Q: Is there an app for scanners? A: Yes. The scanner app covers receiving, dispatch, transfers, counts and stock and location checks, with sign-in by QR code or badge. Devices are matched to the equipment you use. Q: How does NG WMS relate to NG One? A: NG One is the ERP of the same NG family and has its own warehouse features. NG WMS is a standalone warehouse system that connects to NG One or any other ERP through the same API. --- ## Inbound URL: https://ngwms.app/en/inbound (sr: https://ngwms.app/sr/ulaz-robe) Goods arrive with a notice, and any difference shows at once. The receipt order carries what was announced, and the warehouse records what actually arrived. Lot, serial number and expiry are attached to the line at receipt, so traceability starts at the dock rather than later in the office. ### What receiving covers - Receipt orders with a notice: Lines announced by a supplier or by production are entered before the goods arrive. The same order shows announced lines, received lines and a summary of the difference. - Receipt types by origin: Receipts have subtypes: from a supplier, from production, packaging, spare parts, internal locations, returns from production and goods for customs clearance. - Receiving without a notice: When there is no advance notice, a separate order type is used: lines are entered directly as received, with the same lot, serial and expiry data. - Lot, serial number and expiry: Each line carries a lot, a serial number and an expiry date. Per item you set what is mandatory, the serial number format and the minimum remaining shelf life at receipt. - Excel order import: One row holds the header and a line, and rows are grouped by external order number. Along with item and quantity, lot, production date, expiry, quality status and serials are imported. - Order cloning: A repeat receipt is created by copying an existing order. The number, the change history and the ERP link are not carried over, so the copy starts as a new document. - Customs data: For goods under customs supervision, the order holds the warehouse and customs reference, the number of packages and the gross weight, and each line can hold the country of origin. - Printing at receipt: From the order you print the receipt document, declarations — including for lines that are only announced — and EAN labels. - Goods waiting to be put away: Reports show goods still on the dock or at a receiving location, and deviations of the actual location from the proposed one, with reason, device and user. ### How one receipt runs 1. Recorded — The order is created by hand, by Excel import or as a copy of an existing one. Owner of the goods, supplier, expected date and priority, from low to urgent, are entered. 2. Verified — Verification releases the order for receiving. From that point receiving is in progress and lines can be received. 3. Receiving in progress — Received quantities are entered per line, with lot, serial number and expiry. Depending on settings, receiving above the announced quantity is not allowed. 4. Comparison — The summary puts announced and received side by side, so a shortage or overage is visible before the order is closed. 5. Completed — Once the goods are received, the order is completed. A separate view shows the stock created by that order. 6. Closed — A closed order stays in the history, with an audit log of changes. An order that should not be executed is cancelled, not deleted. ### Good to know - Reports show goods waiting to be put away and every deviation from the suggested location, so nothing is left forgotten at the dock. - The announcement arrives from your ERP through the API, and a confirmed receipt goes back as a webhook event — with a trace in the message log. - The receiving flow is configured during rollout, to fit your suppliers, items and way of working at the dock. ### FAQ Q: Can goods that were not announced be received? A: Yes, as a separate order type for receiving without an advance notice. Lines are then entered directly as received, with the same lot, serial number and expiry data. Q: How do you see the difference between the notice and what arrived? A: The summary on the order shows announced and received quantity per line. A setting can prevent receiving more than the announced quantity. Q: Can receipt orders be imported from Excel? A: Yes. One row contains the header and a line, and rows with the same external order number become one order. Along with item and quantity, lot, dates, quality status, serial numbers and country of origin are imported. Q: Does NG WMS hold data for a customs warehouse? A: At receipt you record the warehouse and customs reference, the number of packages and the gross weight. Locations carry a customs status, and outbound has subtypes for customs clearance and re-export. Q: What happens to the goods after receipt? A: The goods are recorded in stock with lot, serial and expiry. Reports show what is still on the dock or at a receiving location and where goods were put away differently from the proposal. --- ## Outbound URL: https://ngwms.app/en/outbound (sr: https://ngwms.app/sr/izlaz-robe) Waves are released deliberately, parcels leave checked. Outbound orders are grouped into waves only after reservations, replenishments and blockers have been reviewed. Every line is checked by scanning before it goes into a box, and both box and pallet get their own labels. ### What outbound covers - Delivery notes by purpose: Subtypes for customers, suppliers, internal locations, production, customs clearance and re-export. A delivery note is verified, approved and locked, and verification can be reversed. - Pre-picking: An order list with quick filters for today, delivery rounds, orders with shortages and postponed deliveries. In bulk you change priority, assign a round and create a wave. - A wave in five steps: Selection review, configuration, reservation, replenishments and exceptions, then release. A wave can stay a draft until the decision is made. - Discrete and Cluster: One order per picker, or several orders at once with sorting while picking. Optionally several pickers on the same wave, a sorting step and sub-tasks per zone. - Manual reservation: For a line you choose a location or LPN with available quantity, lot and expiry. Blocked goods and goods awaiting a quality decision are not offered, and the manual choice is recorded. - Check-and-pack station: Lines are checked by scanning and packed into a box with a printed LPN. Serial numbers are assigned during checking, and boxes are stacked onto outbound pallets. - Transport label and parcels: A packed unit gets a transport label with an SSCC number. Order parcels are kept with LPN, weight, dimensions and closing time. - Consolidation by shipping zone: Rules assign the shipping location by postcode range, with a priority, separately for each warehouse. - Issue rule per item: The issue order is set per item: FIFO, LIFO, FEFO or by location sequence. Delivery can go to the customer, another partner or a private individual. ### The path of one order 1. Pre-picking — The order enters pre-picking with a priority and a round. An order stopped from the ERP carries a flag and a reason, both visible in the pre-picking list. 2. Wave — Selected orders become a wave. Reservation is full or with a shortage, and blockers are kept apart from warnings. 3. Release — Until release the wave is an editable draft. A released wave can be closed, returned to draft or cancelled, and an order can go back to pre-picking. 4. Picking — The status tracks picking in progress and partially picked orders. Shortages show in the shortage report, not only at loading. 5. Check and pack — A box is opened from a printed LPN, lines are packed and confirmed, and serial numbers are assigned where needed. 6. Ready for dispatch — The transport label carries the SSCC, packing is completed with the number of parcels, and the goods wait in their shipping zone. ### Good to know - Waves run on the Discrete or Cluster strategy, and the issuing rule — FIFO, LIFO, FEFO or location sequence — is set per item. - The dispatch location is chosen by postal-code rules, so an order ends up where the carrier collects it. - Dispatch data goes to your ERP through the API and webhooks, with a log of every message. - NG Copilot points out orders waiting for stock or carrying an ERP stop while there is still time to act. ### FAQ Q: Which wave strategies are there? A: Discrete, where one picker handles one order, and Cluster, where a picker handles several orders at once and sorts them while picking. Cluster is the default, and several pickers can be put on the same wave. Q: Can an order with a shortage go into a wave? A: Yes. Reservation is made in full or with a shortage, the order is flagged as partially reserved, and shortages are tracked in a separate report. Q: How does the check-and-pack station prevent wrong deliveries? A: The steps run in order: a box from a printed LPN, packing and confirming lines by scanning, a transport label with an SSCC number, and only then completion of packing. Q: How is the shipping zone decided? A: By rules based on postcode ranges, with a priority, separately for each warehouse. The order thus ends up at the shipping location intended for that area. Q: Can a specific lot or LPN be reserved? A: Yes, through manual reservation: locations and LPNs with available quantity, lot and expiry are offered. Blocked goods and goods awaiting a quality decision are not. --- ## Stock and replenishment URL: https://ngwms.app/en/stock-and-replenishment (sr: https://ngwms.app/sr/zalihe-i-dopuna) The pick face is refilled before it runs empty. For an item and its pick location you set a minimum and a maximum. The replenishment proposal offers stock from reserve locations, the proposal becomes a task, and every deviation from the plan is recorded with a reason. ### What stock covers - Stock by location and LPN: Search by warehouse, item, position and container. A stock row carries the owner of the goods, unit of measure, LPN and transport LPN, stock type, lot, serial number, expiry and receipt date. - Quantity correction: Quantity is corrected per stock row. Voiding a row is a separate action with its own permission, so it cannot happen in passing. - Blocking and unblocking: Goods are blocked by a document with lines and a reason from a code list. A quality status has a priority and a flag saying whether release is required to continue. - Replenishment proposal: For a pick location you see available and reserved quantity, open tasks, min and max and the proposed quantity, along with source locations and the stock available there. - From proposal to task: Replenishment is generated for the whole warehouse or for selected items, or created by hand, including for a specific LPN. A task is started, closed, cancelled or returned to new. - Actual location with a reason: When goods are taken from or placed somewhere other than planned, the actual location and a reason are recorded. The status history stays on the task. - Replenishment on reservation: Reserving an order can trigger replenishment automatically; it stays linked to that order and is visible when a wave is built. - Reserved and missing: A per-item view shows required, reserved and available quantity, and what is still missing for a full reservation. - Replenishment reports: One shows replenishments executed differently from the plan, the other items with replenishment switched on but no pick location or min/max value. ### Replenishment, step by step 1. Rule — Per item you switch replenishment on and set min and max for the pick location, a critical value and the replenishment quantity. 2. Proposal — The proposal compares the pick location with the rule and offers source locations with available stock. 3. Task — Generating for the warehouse or for selected items turns the proposal into a replenishment task. A manual task can also be created for a specific LPN. 4. Execution — The task is started and closed. If goods were taken from another location, the actual location and a reason are recorded. 5. Exception — A task that should not be executed is cancelled or returned to new, and its status history stays with it. 6. Review — Reports show deviations from the plan and items whose replenishment settings are incomplete. ### Good to know - You set minimum and maximum per item and location, to match your issuing rhythm; NG Copilot proposes replenishment when a pick location runs low. - Corrections and voids are made by users with the right, and every change stays in the history with a reason. - Blocked stock and stock awaiting quality release are not offered in manual reservation, so they cannot reach a customer by mistake. ### FAQ Q: How is it decided when a pick location needs replenishing? A: Per item you set a minimum and a maximum for the pick location, plus a critical value and a replenishment quantity. The replenishment proposal compares stock with those rules and offers source locations with available stock. Q: Can an order reservation trigger replenishment by itself? A: Yes. Replenishment created during reservation stays linked to the order and is visible in the replenishments and exceptions step when a wave is built. Q: What if a warehouse operative takes goods from another location? A: They record the actual source or target location and a reason. The report of replenishments with deviations later shows the difference between plan and execution. Q: How are goods blocked for quality reasons? A: With a block document that has lines and a reason from a code list. The quality status has a priority and a flag saying whether release is required, and blocked goods are not offered in manual reservation. Q: Who can void a stock row? A: Only a user with a dedicated permission. Voiding is separate from quantity correction, so someone who corrects quantities does not need that permission too. --- ## Cycle count URL: https://ngwms.app/en/cycle-count (sr: https://ngwms.app/sr/popis) Count the part of the warehouse that matters, and settle variances before posting. A count is set up for the whole warehouse or just a zone, a location range, an item or an LPN. Before release you see what falls into the scope and which open documents touch it, and variances are resolved on a worksheet before the result goes to the ERP. ### From scope to an approved result - A scope that fits: The whole warehouse, the whole warehouse including empty locations, only locations holding stock, or targeted: by area, sub-area, zone, location, location range, item, brand, category, group, LPN or serial number — with include or exclude. - A preview before tasks: Before tasks are generated you see which locations are in the count: those holding stock, empty ones and those where confirming an empty location is mandatory. - Open-document pre-check: The system lists documents still open within the scope. In strict mode the count cannot be released while they exist; in tolerant mode it can, with the list kept visible. - Blind counting: The counter does not see the expected quantity. You also set whether a new LPN or an item outside the scope may be added, whether stock type is mandatory and whether the goods owner is recorded. - Tasks and progress: Tasks per location, with assignment, attempts and sequence. Progress is shown as counted locations out of all locations in the scope. - Scope from Excel: The count list is imported from a file: first a check, then an all-or-nothing import. Errors are shown by row number, so the file can be fixed without guesswork. - Variance worksheet: Shortage, surplus, location mismatch, net zero, unknown, not counted or OK. The decision — accept, recount, ignore or set to zero — is made per line or in bulk, with a reason. - Reserved stock needs a decision: A variance that affects stock already reserved does not pass silently: it requires an explicit decision. The net variance per item is shown next to the per-location variances. - Analysis after counting: Cross-zone analysis pairs a shortage with a surplus of the same item, an EAN scan anomaly report singles out suspicious reads, and the count audit keeps cancelled attempts too. ### How one count runs 1. Scope — Choose the count type and criteria, or import the scope from an Excel file. 2. Preview and pre-check — Check what falls into the count and which open documents touch it; strict mode blocks the release. 3. Tasks and counting — Tasks go to counters, and counting is done with a scanner, blind where required. 4. Variance review — The worksheet sorts the variances, and each one gets a decision with a reason. 5. Recount — Disputed locations go back for counting before the result is accepted. 6. Approval and ERP — The count is approved in the WMS, sent to the ERP and closed once the ERP confirms receipt. ### Good to know - Counting is done in the scanner app; setting up, reviewing and approving counts happens in the web application. - The approved result goes to the ERP, and the “Sent to ERP” and “ERP confirmed” states show that the variance has been posted. - For every variance NG Copilot gathers the location’s history — receipts, issues and transfers — so the decision to recount comes faster. ### FAQ Q: Do I have to count the whole warehouse at once? A: No. The scope is set by area, zone, location, location range, item, brand, LPN or serial number, so only what is needed is counted. Before release, the pre-check shows open documents within that scope. Q: What is blind counting? A: The counter records what they counted without seeing what the system expects. The counted quantity is therefore independent of the expected one, and the variance only appears on the worksheet. Q: What happens when a variance affects reserved stock? A: Such a variance is not applied automatically. The worksheet singles it out and asks for an explicit decision, because a change would affect orders the stock is already reserved for. Q: Can I import a list of locations to count? A: Yes, from an Excel file. The file is checked first, and the import only goes through if every row is valid; errors are shown by row number. Q: When does the count result reach the ERP? A: After the variance review and approval in the WMS. The count then moves to “Sent to ERP” and is closed once the ERP confirms receipt. --- ## Warehouse model URL: https://ngwms.app/en/warehouse-model (sr: https://ngwms.app/sr/skladisni-model) A warehouse described the way it really is. Each warehouse is divided into areas, sub-areas and locations. A sub-area knows what it is for and what may be stored together, a location carries its dimensions, levels and picking sequence, and the 2.5D view shows occupancy and blocks without walking the racks. ### The structure the whole goods flow runs on - Warehouse hierarchy: Warehouse, area, sub-area and location, across several warehouses. Warehouse types: ramp, dock, chamber, storage and building, with storage zones and priority zones. - Sub-area purpose: Picking, storage, reserve, receiving, dispatch, quarantine or returns. A sub-area has an A–D category and a list of permitted stock types. - Stock mixing rules: You decide what may share a location: the same item, lot, owner, block status, stock type or receipt order — at three levels of strictness. Plus multiple LPNs and a virtual LPN per sub-area. - Locations with dimensions and sequence: Dimensions, row, column and level, number of levels, maximum handling units, picking sequence and a pick-face flag. A location can be dedicated to a customer or an item, and blocked with a reason. - Handling units: A pallet, carton or other unit with weight, maximum weight, volume and dimensions (length, width, height). - Items with rules: Mandatory lot, serial number format, shelf life and minimum remaining shelf life at receipt and at issue. An issue rule per item: FIFO, LIFO, FEFO or by picking sequence; ABC and ADR class and a temperature range. - Customs status: Locations and sub-areas carry a customs status — commercial, customs or mixed — so goods under customs supervision are kept apart from free goods. - 2.5D view and free locations: An isometric view of locations by row, column and level, coloured by occupancy, block, location type or customs status, filtered by area and sub-area. Plus a list of free locations. - Master data import from Excel: Items, warehouses, areas, sub-areas, handling units and quality statuses are imported from a file, so the model is not entered by hand, location by location. ### How a warehouse is described 1. Warehouses and types — Enter the warehouses, their types and zones, plus goods owners if the warehouse holds stock for several companies. 2. Areas and sub-areas — Each sub-area gets a purpose, a category and its permitted stock types. 3. Mixing rules — Decide what may share a location and how strictly that is checked. 4. Locations — Dimensions, levels, picking sequence, pick-face and any dedication to a customer or item. 5. Items and handling units — Lot, serial number, shelf life, issue rule and unit dimensions, imported or entered. 6. Review in 2.5D — Occupancy, blocks and customs status are visible on the isometric view. ### Good to know - The 2.5D view gives an overview of occupancy and blocks by location, straight from the warehouse model. - Reports on goods waiting for put-away and on deviations from the suggested location keep put-away under control. - The model grows with you: a new warehouse, area or location is added without changing the rest of the model. - The customs status of locations and sub-areas supports customs warehousing, while your customs agent handles procedures with customs. ### FAQ Q: Can I run several warehouses? A: Yes. Each warehouse has its own areas, sub-areas and locations, and warehouse types cover ramp, dock, chamber, storage and building. Q: What are mixing rules? A: Rules set per sub-area that decide what may share a location: the same item, lot, owner, block status, stock type or receipt order. Strictness is chosen at three levels. Q: What does the 2.5D view show? A: An isometric view of locations by row, column and level. It is coloured by occupancy, block, location type or customs status, and filtered by area and sub-area. Q: Can I import existing master data? A: Yes, from an Excel file: items, warehouses, areas, sub-areas, handling units and quality statuses. Q: Does NG WMS support customs warehousing? A: Locations and sub-areas carry a customs status, receiving records customs data, dispatch has sub-types for customs clearance and re-export, and there is a customs label template. --- ## Labels URL: https://ngwms.app/en/labels (sr: https://ngwms.app/sr/nalepnice) A label the scanner reads and a person understands. Templates for LPN, EAN, shipping, customs and other labels are laid out in a visual designer, in millimetres, and checked as a PDF before printing. Each goods owner or supplier can have its own template, and each workstation its own printer. ### From template to the label on the carton - Eight template types: LPN, EAN, shipping, declaration, serial number and customs labels, plus a packing list and a warranty card in A4 format. - Visual designer: Elements are placed on a canvas in millimetres. A type can have several templates, with one set as default. The preview opens as a PDF. - Barcodes and QR: Text, QR and Code128, EAN-13, EAN-8, UPC-A, UPC-E and ITF-14 (GTIN-14) barcodes. The shipping label carries an SSCC. - Templates per owner and supplier: When a goods owner or supplier requires its own label layout, a dedicated template is linked to it, so staff do not choose by hand which one to print. - Printing from the barcode register: LPN, EAN with EAN code generation, serial numbers, declarations, an SKU declaration per LPN and printing a barcode range in advance. - Printing from documents: From a receipt: the document, declarations and EAN. From a delivery note: the advance notice, packing list, declarations and EAN. - Printers and workstations: A register of printers — network, local, browser or system — and of workstations. A printer is assigned per workstation and label type, and the user’s choice is remembered. - Server-side printing: The server sends the label PDF to a named printer. Where that is not possible, printing from the browser remains the fallback. - List export: Lists from the barcode register export to CSV and Excel, for checking or further processing. ### How a label reaches the goods 1. Template — The layout is built in the designer per label type, and where needed for a specific goods owner or supplier. 2. Printer — Each workstation is assigned a printer for every label type printed there. 3. Print — The label is printed from a document or from the barcode register, as a PDF on the assigned printer. ### Good to know - Every label is checked as a PDF before printing and sent to the printer assigned to the workstation. - A template for a carrier or retail chain is built in the designer to its requirements and saved for reuse. - Your company obtains its GS1 prefix and GTIN numbers from the GS1 organisation, and NG WMS uses them on labels. - Warehouse printers are checked on your own equipment as part of the rollout. ### FAQ Q: Which barcodes do the labels support? A: Code128, EAN-13, EAN-8, UPC-A, UPC-E and ITF-14 (GTIN-14), as well as QR codes. The shipping label carries an SSCC. Q: Can different goods owners have different labels? A: Yes. A template is linked to a goods owner or a supplier, and each label type can have several templates with one default. Q: How is the printer chosen? A: A printer is assigned to a workstation for a given label type, and the user’s choice is remembered. The server can send the PDF straight to a named printer, with browser printing as the fallback. Q: Can I print LPN labels in advance? A: Yes. The barcode register prints a range of barcodes, so labels can be prepared before receiving or packing. --- ## Kitting URL: https://ngwms.app/en/kitting (sr: https://ngwms.app/sr/dorada) Repacking and kitting with a lot that has a history. When the warehouse assembles, repacks or reworks goods, a work order records what was planned for consumption, what was actually consumed and what was produced. Produced goods get a lot automatically, so you can later tell what they were made from. ### What kitting covers - Work order: The order separates planned consumption, planned output, consumed items and produced items. Plan and execution sit side by side. - Operation types: Operations are defined in a code list — sorting or packing, for example — and chosen on the work order. - Packing specification: A specification per item lists which components, in which unit of measure and in what quantity make up the finished item. - Automatic lot: Produced items get a lot automatically, so the batch reference does not depend on someone typing it in. - Operators on the order: The order records the operators who carried it out, and a code list links operators to the operations they perform. - Items and operations: A code list links items to the operations performed on them, so it is clear which kitting step belongs to which goods. - Production lot traceability: For a lot created by kitting you see the source documents and consumed materials, and for an incoming lot — where it went and what was made from it. - Material into kitting and back: Delivery notes for production, receipts from production and returns from production are separate document subtypes, so material movements stay in stock. ### One work order 1. Specification — The finished item has a packing specification: components, units of measure and quantities. 2. Plan — The work order announces what will be consumed and what will be produced, with the operation type. 3. Issuing material — Components are issued with a dedicated delivery note subtype — the delivery note for production. 4. Work — The operators carrying out the operation are recorded on the order. 5. Result — Consumed and produced items are recorded, and the produced goods get a lot automatically. 6. Back into stock — For finished goods coming in and unused material going back there are receipt subtypes from production and returns from production. ### Good to know - Kitting covers assembling, repacking and reworking goods in the warehouse; production planning and costing stay in your ERP. - The specification is a list of components per item, so a work order knows straight away what to consume. - Produced goods get a lot automatically and enter the same traceability as the rest of the stock. ### FAQ Q: What is kitting in NG WMS? A: Work on goods inside the warehouse — sorting, packing or assembling kits, for example — run through a work order that records planned and actual consumption and the items produced. Q: How do you know what a produced lot was made from? A: Backward traceability of the production lot shows the source documents and consumed materials, and forward traceability of an incoming lot shows what was made from it. Q: What is a packing specification? A: A list of components for one item: which item goes into it, in which unit of measure and in what quantity. Q: Does NG WMS plan production? A: No, kitting is warehouse work: assembling, repacking and reworking goods through work orders. Production planning, capacity scheduling and costing are handled by your ERP. --- ## Scanner app URL: https://ngwms.app/en/scanner-app (sr: https://ngwms.app/sr/skener-aplikacija) Work is confirmed where the goods are. Alongside the web application for the office, NG WMS has a dedicated app for work on the warehouse floor. Receiving, dispatch, transfers, counting and stock and location checks are confirmed by barcode scanning — where the goods are, without paper or retyping. ### What work with the scanner covers - Receiving and dispatch: Goods receiving and dispatch with scanning. A delivery note is worked in manual or guided mode, depending on the warehouse setting. - Transfers: Moving stock between locations is recorded in the scanner app, and the transfer history is available in the web application’s reports. - Counting: Counting by count task. The office sees who counted, on which device and which code was scanned. - Stock and locations: Checks of stock, container location, free locations and empty containers, plus barcode checks. - Waves for pickers: Once the office releases a wave, pickers see it in the app straight away and can start picking. - Sign-in without typing: With a username and password, a QR code or the user’s RF/NFC badge — the code is linked to the user in administration. ### How work is split between office and floor 1. The office releases work — A picking wave, a count task or a receipt order becomes visible in the scanner app. 2. Staff scan — Location, container and item are confirmed by scanning rather than copied from paper. 3. The trail stays in the WMS — Who worked, on which device and what was scanned is visible in the office and in reports. ### Good to know - Devices and network coverage are matched to your warehouse and equipment as part of the rollout. - The app is delivered and configured for your devices as part of the NG WMS rollout. - An RF/NFC badge or QR code gives staff a quick sign-in on shared devices. ### FAQ Q: Is the scanner app part of NG WMS? A: Yes. It is a dedicated app for work on the warehouse floor, alongside the web application for the office — on the same orders, waves and tasks. Q: How do staff sign in? A: With a username and password, a QR code or an RF/NFC badge. The code or badge is linked to the user in administration, so every scanned step is recorded under their name. Q: What can staff do in the app? A: Receiving, dispatch, transfers, counting, and checks of stock, container location, free locations and empty containers, plus barcode checks. Pickers see a released wave straight away. Q: Which devices does it run on? A: Devices are matched to the equipment you use or plan to buy and checked in your warehouse as part of the rollout. Q: How does the scanner app reduce errors? A: Location, container and item are confirmed by scanning instead of being copied from paper, and guided dispatch mode enforces a strict sequence where mistakes are costly. --- ## NG Copilot and MCP URL: https://ngwms.app/en/ng-copilot-and-mcp (sr: https://ngwms.app/sr/ng-copilot-i-mcp) An AI that knows where every pallet is — and asks before it acts. NG Copilot answers questions about stock, orders, waves and lots and says which document each answer comes from. AI agents keep watch over the shift, dispatch, replenishment, counts and expiry dates on their own and prepare proposals, while the MCP server connects your team's AI tool to the warehouse. Every action waits for a person's confirmation. ### Every AI capability, one set of rules - AI agents for the warehouse routine: Agents run on a schedule or on an event: shift overview, dispatch blockers, pick-face replenishment, count variances, expiry dates and hold-ups in the ERP exchange. The result is a proposal that waits for a person. - MCP server: The Model Context Protocol is an open standard for connecting AI assistants and agents to business systems. Through it, Claude, ChatGPT and other MCP clients read stock, orders and goods history, with no separate integration for each tool. - Questions in your own words: “Where is lot L-0915?”, “What is late for dispatch today?”, “How much of this item is in reserve?” — Copilot answers briefly and names the document, location or wave the answer comes from. - A shift overview in a minute: Open receipts, waves being picked, orders with blockers and pick locations below minimum — in one summary, at the start of a shift or before a meeting. - Blockers before the truck: Copilot points out orders waiting for stock, waves with warnings and goods that have waited too long for put-away, with the reason and the document. - Replenishment and priority proposals: When a pick location runs low, Copilot proposes replenishment from reserve and an order of work. The task is created once a user confirms it. - Count variances, explained: For every variance Copilot gathers the location’s history — receipts, issues and transfers — so the decision to recount or approve comes faster. - Lot and expiry: Which goods expire in the next 30 days, where a given lot is and who it was shipped to — the answer comes with the receipt and dispatch documents. - Same rights, same trail: Copilot, agents and every MCP client act on behalf of the signed-in user and see only the warehouses and goods owners that user may see. Questions and confirmed actions stay in the trail. - Control over AI: Administrators decide for which warehouses and users the AI is enabled and who uses MCP access, with a key that can be revoked. ### From a question to a confirmed action 1. You ask — or an agent starts on its own — In NG WMS or from an AI assistant connected through MCP, in your own words, in Serbian or English. An agent starts the same flow on a schedule or on an event. 2. The AI checks — It goes through orders, waves, locations and the movement history of goods, only in the warehouses your account may see. 3. It answers with a source — A short answer and the documents it comes from — wave, order, location or lot, one click away. 4. You confirm — A proposed replenishment, priority or check becomes a task only after you confirm it, with a record of who confirmed. ### Good to know - Copilot and AI agents propose and a person decides: tasks, corrections and approvals are created after confirmation by a user with the right. - MCP access is enabled per user, with a key the administrator can revoke at any time. - NG Copilot also works in NG CRM and NG DMS, so your team uses the same assistant across the NG family. ### FAQ Q: What is NG Copilot in NG WMS? A: NG Copilot is the AI assistant built into NG WMS. It answers questions about stock, orders, waves, lots and locations, summarises the state of a shift, explains count variances and proposes replenishment and priorities — always with the document the answer comes from. Q: What do AI agents do in NG WMS? A: AI agents run on a schedule or on an event: they prepare the shift overview, watch for dispatch blockers, propose pick-face replenishment, explain count variances and keep track of expiry dates and hold-ups in the ERP exchange. They work with the user's permissions, and anything that changes data arrives as a proposal for confirmation. Q: Can Copilot or the agents change stock on their own? A: No. Copilot and the agents propose; corrections, replenishment tasks and approvals are created when a user with the right confirms them. Every confirmation stays in the document history. Q: What is MCP and what is it for? A: MCP (Model Context Protocol) is an open standard for connecting AI assistants and agents to business systems. NG WMS has an MCP server, so the AI tool your team uses reads stock, orders and goods history — only with the permissions of the user working with it. Q: Does Copilot see every warehouse? A: Copilot sees only the warehouses, goods owners and documents the signed-in user may see in NG WMS. The same applies to AI agents and to every MCP client. Q: How does Copilot help with stock counts? A: For a variance at a location it gathers receipts, issues and transfers from the history, so it is quicker to see whether it is a counting error, an unrecorded movement or a real shortage. --- ## Reports and traceability URL: https://ngwms.app/en/reports-and-traceability (sr: https://ngwms.app/sr/izvestaji-i-sledljivost) Every lot has a history, and it reads both ways. From receipt to dispatch, every movement of stock is recorded: on which document, at which location, in which container and by whom. The same records produce lot traceability, the item card, productivity and the outbound overview. ### Answers a warehouse owes its customers, auditors and itself - Incoming lot traceability: From the receipt, through delivery notes to production, to the manufactured items the lot ended up in. - Production lot backwards: For a finished product: the source documents and the raw materials consumed in it. - Item card: Warehouse, position, container, document type, document, quantity, date, worker and status — every movement of an item, in order. - Transfer history: Filter by container, item, location or warehouse type, with the from and to locations and the worker who moved the stock. - Stock list and stock position: A stock list and a pivot of stock by lot, serial number, expiry date and pallet, with totals received and sold. - Receiving and picker productivity: Receiving per worker: documents, lines, quantity, serial numbers and lots, and how serials were entered. Pickers: lines, units, orders, time span and shortages. - Outbound under control: Shortages, a wave overview with progress, zones, pickers and deadline, cut-off and delays, packed parcels and control station activity. - Audit: An audit log per document and an outbound activity audit: which field changed, the old and new value and the device the change came from. - Users, roles and branches: Roles with privileges per function; menus and screens follow the user’s permissions. Branches, configurable document actions and transitions, sign-in by QR code or RF/NFC badge. ### How the trail is created 1. Receiving records the origin — Lot, serial number, expiry date and quality status are entered at receipt or arrive with the Excel order import. 2. Every movement is recorded — Transfers, picking, packing and dispatch each leave a record with location, container and worker. 3. Queries in both directions — From an incoming lot to production and manufactured items, or from a finished product back to raw materials and source documents. ### Good to know - Reports on goods waiting at the dock and on deviations from the suggested location keep put-away under control. - Reports measure the work, and you set the standards and targets for your warehouse. - Traceability covers every step of the goods through the warehouse, and your ERP keeps what happened before receipt and after dispatch. - NG Copilot answers questions about a lot and its expiry with the receipt and dispatch documents. ### FAQ Q: How do I find where a single lot went? A: The incoming lot traceability report starts from the receipt and follows the lot through delivery notes to production, to the manufactured items. For a finished product there is the reverse report, back to source documents and consumed raw materials. Q: What does the item card show? A: Every movement of the item: warehouse, position, container, document type and document, quantity, date, worker and status. Q: Can I track productivity per worker? A: Yes, for receiving and for picking. Receiving shows documents, lines, quantities and serial number entry per worker; picking shows lines, units, orders, time span and shortages. Q: Who sees which reports and screens? A: Roles decide that. Each role has privileges per function, and menus and screens are shown according to the user’s permissions. Q: Can I see who changed a value? A: Yes. The audit log follows every document, and the outbound activity audit records the field, the old and new value and the device. --- ## ERP integration URL: https://ngwms.app/en/erp-integration (sr: https://ngwms.app/sr/erp-integracija) Your ERP and the warehouse, on the same numbers. The link with the ERP runs through the API, webhooks and an outbox. Every API client has its own key with an expiry date, every message leaves a trace in the log, and a message that was not delivered waits in the outbox and can be sent again, with the same ID. ### Integration you can see and control - API clients and keys: Each connecting system gets its own API client: a key with a prefix, a label and an expiry date, in the Active, Expired or Revoked state. A key can be revoked before it expires. - The secret is shown once: The key secret is shown only when it is created, and only its fingerprint is stored. A token is issued through the OAuth2 client credentials flow; an inactive client gets no token. - Call statistics: Per client: requests, successful, rejected and failed calls, average response time, by day and by endpoint, with the latest errors. - Webhooks: A URL and a subscription to events from the catalogue. Authentication: none, Bearer, Basic, OAuth2 password or OAuth2 client credentials. A test message and delivery counters. - Outbox: Outgoing messages are Pending, Sent or Undeliverable, with the number of attempts, the time of the next attempt and the last HTTP status. - Retry with the same ID: An undelivered message is resent manually with the same message ID, so the receiving side can recognise the repeat and not process it twice. - Message log in both directions: Incoming and outgoing messages in the Processing, Done, Failed or Under review state, with a correlation ID and contract version. Messages under review are resolved manually. - Developer documentation: An OpenAPI description of the API, opened through Swagger UI, and a Postman collection for test calls. ### What one connection looks like 1. Connect — Create an API client, collect the secret once, and the system obtains a token through the OAuth2 client credentials flow. 2. Exchange — Incoming messages arrive through the API, and catalogue events leave by webhook, via the outbox. 3. Monitor — The log, statistics and latest errors show the state, and undelivered messages are sent again. ### Good to know - The link works with your ERP, including NG One, through the API, webhooks and the outbox; the mapping of fields and events is configured for your system. - Accounting and invoicing stay in the ERP, and NG WMS sends it verified data about the goods. - Webhooks send events from the catalogue — receipts, dispatches, counts and other stock changes. - Alongside the API link, NG WMS has an MCP server for your team’s AI assistants. ### FAQ Q: Which ERP does NG WMS work with? A: With yours. The link runs through the API, webhooks and the outbox, so NG WMS works with NG One as well as other ERP systems; which fields and events are exchanged is configured for your system. Q: How does another system authenticate to the WMS? A: Through an API client: it receives a key and a secret, then a token via the OAuth2 client credentials flow. The key has an expiry date and can be revoked; an inactive client gets no token. Q: What if the ERP is unavailable when the WMS sends an event? A: The message stays in the outbox with its number of attempts and the time of the next attempt. A message that remains undeliverable is resent manually, with the same message ID. Q: Is there API documentation? A: Yes: an OpenAPI description through Swagger UI and a Postman collection for test calls. Q: How can I see what arrived from the ERP? A: The message log records incoming and outgoing messages with their state, correlation ID and contract version. Messages that need checking stay “Under review” until someone resolves them.