Orbis Nexa brings the product tree, catalog, bill of materials, change, quality, supply, dealer and marketplace channels, campaigns and customer management into a single platform that runs on your own infrastructure. Your suppliers, dealers and sellers connect to the same system through their own portals.
Every feature on this page works in the current release. Anything not yet available is listed separately under “Known limits”.
Sample record; field names and lifecycle stages are the real structure in the product.
Every component, AI included, runs inside your infrastructure. Data leaves the organisation only through integrations you set up.
From idea to recall and from order to settlement every record is linked; who changed what, and when, is always on file.
Separate portals for suppliers, dealers / franchisees and marketplace sellers; orders, shipments, appointments, scorecards and settlements in one record.
Each country works with its own data, currency and language. The interface comes in 9 languages, Cyrillic and Arabic included.
Three example processes show how Orbis Nexa is used in daily work. The screens are illustrative; field names, states and numbering are the real structure in the product.
A proposal voted up in the idea pool becomes a product record with one click. Choosing a category builds the product form by inheritance; missing mandatory fields block publication. Review and approval steps come from the workflow; the approved product is sent to the storefront and the connected sales channels automatically.
A change request (ECR) is opened with the affected products and gets an automatic number. The approval step records an electronic signature; at implementation the new BOM revision is frozen and its difference from the previous one (added, removed, quantity changed) is shown on one screen.
The purchase order appears in the supplier's portal; the supplier confirms the lines, creates a shipping notice and books a dock appointment based on capacity. At receiving the warehouse counts the quantity; any discrepancy opens a non-conformance record automatically and is reflected in the supplier scorecard.
The nine groups below are the real menu structure of the admin panel. Every item is a screen you can open and use today; visibility follows the user's permission package and the licence.
Product structure, change, document and quality records are linked to each other. Every transition passes through a state machine; invalid transitions are rejected and history is kept.
The language model and the search index run on your infrastructure; catalog data is never sent to a cloud AI service. The application itself opens outward as far as you decide: the storefront, the portals and agent connections work under your authorisation.
Finds synonyms and related concepts and understands fact filters such as “with a 3D model”. The vector explorer shows what the index actually found.
Answers natural-language questions over the matching products, in whatever language the question was asked. Source products are shown with the answer.
Bottom right on every screen. It knows the user manual, takes the open screen into account and explains the menu › screen › button path in its own words.
Turns a question such as “certificates expiring in the last 90 days” into the right report and parameters, and summarises the result briefly.
Demand velocity, stock-out risk, reorder point and a reasoned supplier risk score, with a “what to do” hint per row. When data is insufficient it produces no forecast and says why.
When a new country is prepared, product, category and attribute names are translated into the tenant's language, with script checks for Cyrillic and Arabic. The result is submitted for user approval.
The portals are not separate applications; they are areas of the same platform opened only to external users. Every partner sees only its own records, and prices and margins never leave the organisation.
Orbis Nexa is not a consumer cart or payment system. Orders arrive from the connected sales channels; campaign calculation, customer records, shipment tracking and reports live here.
The screens answer “what do we send, what comes in” in plain words. The building blocks (connectors, flows, field mappings) sit in a separate advanced menu; most users only use the platform centre.
Shipped with the product: API reference, Postman collection and an illustrated user manual.
Every request is authorised first at the entry layer and then inside the application itself. Permissions are granted through ready-made packages; the menu shows only the screens the user is allowed to open.
These matter for a purchase decision too. The items below are the limits of the current release; some are on the roadmap.
We load a sample of your data through an import profile and walk through the engineering, supply, dealer and campaign flows end to end. The environment can run on your servers or in our demo environment.
E-mail: info@extreamsoft.com