Order management that works directly on your ERP: Allegro, shipping labels, returns and emoWMS on Zebra terminals.
We are preparing emoms to meet Amazon's requirements for protecting buyers' personal data. In installations with an Amazon shop: a password of at least 12 characters, mandatory two-factor authentication and hidden buyer data on Amazon orders.
How it works ›A kit line (WAPRO) is coloured by the stock of the kit itself: teal – an assembled kit is in the order's warehouse, crimson – it has to be assembled. The “…” window also shows components in the shop's other warehouses.
How it works ›Kit lines on the order list have a “…” button showing the components, their stock and how many kits can be assembled. WAPRO kit stock sent to the shop is now also counted from components.
How it works ›A click on a line's SKU copies it and the auction number opens the Allegro offer. Kit components on the delivery note are indented and the shipping cost can be left out. The order completion refresh task can assemble kits by itself.
How it works ›Orders go to Fakturownia as an order and the invoice is issued from it. The VAT map picks WDT or OSS, foreign-currency invoices use the NBP rate, and a marketplace payment carries its transaction id.
How it works ›More orders can be added to an open picking basket. The Invoice/Receipt action (WAPRO) can set the salesperson. Creating a waybill no longer produces duplicate shipments after a save error.
How it works ›The VAT rate map of a Fakturownia shop accepts every EU country (e.g. Slovakia). The “Pair all” dialog shows offers paired with A2C only separately.
How it works ›An automation rule shows who changed what and when. A button rule with an invoice or receipt can be saved after explicit consent – it runs at most once per order.
How it works ›The action “Send proforma (order PDF) to shop” uploads the ERP order printout to the a2c.online shop order – the customer downloads it in their account.
How it works ›Received invoice lines with an EAN code are matched to the ERP item automatically, and issued invoices carry the item index (symbol) and EAN – like Nexo.
How it works ›UPO downloads show in the order history, missing UPOs are fetched automatically, and street names that start like a prefix (“Aleja”, “Alpejska”) are no longer cut.
How it works ›Since 18 Oct 2026 e-mo.pl invoices are issued and filed with KSeF by emoms – without the paid KSeF module in Nexo.
How it works ›After KSeF accepts an invoice emoms stores its UPO and lets you download it. Automations no longer react to old events from history.
How it works ›The Sent list also shows invoices the ERP filed with KSeF. The invoice QR code points to production KSeF, and the Nexo print template map lists all templates.
How it works ›On the Mapping screen, “Add to ERP” creates a new card (service or goods) and maps the invoice line to it right away.
How it works ›New setting “Who files invoices with KSeF” (emoms or the ERP) and a choice how many days back the first received-invoice download reaches.
How it works ›In the Allegro carrier account you choose how InPost parcels are sent: any Paczkomat or PaczkoPunkt, a Paczkomat, a PaczkoPunkt or courier pickup.
How it works ›A reservation above the stock of one warehouse is deducted from the shop's other warehouses, also those of another ERP database.
How it works ›The same action sets the A/B/C (S/M/L) size for parcel-locker orders and dimensions with weight for courier orders.
How it works ›Custom event buttons with the "Orders list" placement appear on the /orders action bar and work on all selected orders.
How it works ›A new rule action sets the parcel size just like clicking the size letter on the orders list - the letter matches the order's carrier.
How it works ›Invoices issued in the ERP can be sent to Amazon (without Amazon VCS) with the same action as for other shops; emoms checks that Amazon accepted them.
How it works ›The picking screen lists baskets in one grid with Take/Return buttons, and basket orders have their own view with locks and links to orders.
How it works ›Before the couriers pick up, scan waybills into the carrier box (InPost, DHL, DPD, Allegro One, ORLEN...). A parcel of another carrier is rejected; an order with all parcels in the box gets the chosen status.
How it works ›With “Printer visibility for users” on, every printer picker lists only printers marked green - also for administrators and in automation actions.
How it works ›Permissions as a grouped grid (all order actions visible), an “Unlock user” button, the WZ code works on Packing and Picking too, printer settings recompute the label width.
How it works ›When the print agent reports an error or does not pick up the job, the order shows up on the dashboard in the group “Document print failed”. A successful print is no longer labelled “E-mail error” in the history.
How it works ›New event “Parcel size changed (manually)” and condition “Parcel size (changed manually)” - clicking A/B/C or S/M/L in orders can move the order to a size folder and issue the invoice, waybill and WZ.
How it works ›An invoice filed with KSeF by WAPRO gets the QR code, the Ministry of Finance verification link and the KSeF number on its PDF - in preview, print, e-mail and Allegro.
How it works ›Collect several orders in one click, natural rack and shelf order, and manual put-away of shortages also for barcoded goods.
How it works ›Mouse-free stations: the scan that completes the order's last line finishes packing right away - no PACKDONE code needed.
How it works ›When packing several orders at once, a complete parcel can be closed on its own and shipped right away - no need to wait for the whole batch.
How it works ›In the “Print from template” window you can pick a printer and click “Print” - the PDF goes straight to the print agent, no file download. The {NICK} token prints the buyer's Allegro nick.
How it works ›A shop that sums stock from several Nexo databases now sees the second database's warehouses on the product card (Stock tab) and as badges on the product list - the same way stock is sent to the shop.
How it works ›Users, permissions and monitoring screens have a new, clearer layout. Automation rules react to a printed document and to a WZ code scan. The order list immediately hides an order that left the view after a status change.
How it works ›The menu shows how many orders wait in each order view. Copy the Allegro nickname or phone with one click, and the Allegro order number opens the order in Sales Center. New filter: orders without an assigned packer.
How it works ›On the printout you can place both WAPRO product indexes - {INDEKS_KATALOGOWY} and {INDEKS_HANDLOWY} - regardless of what is configured as SKU. Events 60/61 in automation rules have correct names.
How it works ›In the “Create waybill” action with the “Take from the order” service you can now choose the work mode - including locker size A (S), B (M) or C (L).
How it works ›On the order printout you can place the real WZ document number from WAPRO (field {NUMER_WZ}), and rotate a barcode vertically so it fits next to the shipping label.
How it works ›In an automation rule you set retry times (e.g. 16:00, 10:00, 16:00) - when the ERP rejects the document because of missing stock, emoms tries again, giving time to receive the goods.
How it works ›After packing an order the list and basket cards refresh without reloading the page, a basket shows "2/3", and batch picking lets you fix a quantity with +/- buttons.
How it works ›Each size button (S, M, L) shows its dimensions, e.g. 8 × 38 × 64 cm - the packer knows right away which one to pick.
How it works ›Each shipment on the order page has a "Print" button, and when there are several - also "Print all".
How it works ›When Allegro rejects resuming an ended offer (missing responsible producer, mandatory parameter or a duplicate), the dashboard shows a group with an "Edit in Allegro" button.
How it works ›See when a product was last sent to the shop: today, within 24/48/72 hours, within 7/14/28 days, older than 28 days or never updated.
How it works ›A new picking stage: an order with goods to prepare waits blocked until someone prepares the lines and prints a label - then it goes back to regular picking by itself.
How it works ›A rule can run only for orders containing goods from selected ERP product groups - e.g. plants or cables that cannot be told apart by symbol alone.
How it works ›A Nexo kit has no stock of its own, so it reached the shop with zero and Allegro ended the offer. Kit stock is now calculated from its components, as in legacy, and ended kit offers resume by themselves.
How it works ›Product lists have a copy-to-clipboard icon next to the symbol and EAN, and a double click opens the card - a single click no longer throws you off the list.
How it works ›The administrator chooses which printers regular users see, and the batch picking list shows product photos - also from the shop when the ERP has none.
How it works ›The completion bar and the "Complete" filter are computed from stock on GT and WAPRO too, the "Goods in stock / out of stock" rules work when an order is added, and a new task re-checks open orders after deliveries and fires events for rules.
How it works ›The "Print document" rule action lists the ERP invoice and receipt (template from the shop's print template map), also behind a custom button. "Issue invoice" on an order already invoiced in the ERP shows the existing invoice number instead of an error.
How it works ›"New integration" offers the Pigu marketplace. With the address, login, password and Seller ID, emoms tests the connection and downloads orders from all PHH Group markets into staging and the ERP.
How it works ›"Connect to eBay" in the shop settings ends with a connection, the token refreshes itself, and eBay orders reach staging and the ERP with correct amounts, e-mail address and country.
How it works ›Pick a pickup point from carrier pills (Orlen Paczka, DPD, DHL and more), the shipment history shows route stages, and carrier status mapping can set a custom order status.
How it works ›The "Send a message to the buyer" action inserts the text of a message template, and a rule triggered by a buyer message tells the first contact from a follow-up. Message templates have a grid with drag-and-drop order.
How it works ›The list of orders that did not reach the ERP groups by error type, and an order line links straight to offer pairing. Bulk offer publishing has its own page with a live result per product.
How it works ›When a shop order cannot enter the ERP because a payment or VAT mapping is missing, the home page shows a tile with the number of blocked orders, and the payment and VAT maps offer a ready-made entry.
How it works ›The buyer ordered as a private person but wants a company invoice? Change the buyer straight from the order card. The orders list shows the Allegro buyer nickname and can search by it, and the red "did not reach the ERP" banner only shows the last week.
How it works ›Look up a product on the scanner: its location and stock in every warehouse. The code on the Warehouse list opens packing at once, a double tap on an order line shows the product photo, and scanning now recognises extra EAN codes from the ERP.
How it works ›Install new versions of the scanner and phone app from the emoms panel - no Google store and no sending files around. Test a version on one terminal first, then approve it for the whole company with one click.
How it works ›When an Allegro buyer files a return before you issue a sales document or a waybill, emoms can cancel the order in the ERP automatically. The option is off by default - turn it on in the returns sync task.
How it works ›The order number now shows how the parcel will be shipped: carrier, size, weight and dimensions. Change a locker size with one click and ship many orders at once.
How it works ›Custom thread labels, hiding system messages, thread type on the list and "Mark as unread". The auto-reply can answer only outside working hours.
How it works ›The error screen shows a Request ID that now really points to a log entry, and one button forwards the report to e-mo.pl.
How it works ›Search by fragment in filters, clearer order views, fixes for WAPRO and Allegro, and new task settings.
How it works ›When creating an order on Nexo you can set the Buyer, Recipient and Payer separately - e.g. a municipality and a kindergarten for public-sector invoices.
How it works ›The ERP order number, e.g. "ZK 171/2026", can be added to the remarks of receipts and invoices issued from an order.
How it works ›Task history has a third state "UWAGI" (warnings): an order refused by the ERP no longer switches off the whole task or holds back the other orders.
How it works ›In the ERP settings you can choose the fiscal printer brand (Posnet, Elzab, Novitus) separately for invoices and receipts.
How it works ›The warehouse list has a second layout: pieces summed per product across orders. The "Shipment number" filter now also sees shop-reported numbers and shipments made outside emoms.
How it works ›Claude, Gemini or Codex can knock on emoms, read how the system works and walk you through what to do, step by step.
How it works ›Allegro messages in the panel and on the order card. Reply templates and an auto-reply to the first message.
How it works ›An offer without stock ends by itself and comes back after delivery. Per-offer mode: automatic or manual.
How it works ›Scanned too many? Remove mode subtracts a piece, and error acknowledgement lets you close the parcel.
How it works ›Custom order views with a base filter, a permission and a menu icon. Filters with negation, separate invoice and receipt views.
How it works ›