Implementing ERP.net

The recurring work of an ERP.net implementation, and the shape Operator gives it.

Implementing ERP.net is not one big project — it is a stream of well-understood, repeating tasks: printing a document, adding a calculated field, building a report, scheduling a job, setting up a validation. Each company does a version of the same things. These tasks have a known good shape, so Operator does not improvise — it follows a recipe and produces the same reliable result each time.

Operator recognizes what you are asking for from your own words. Say what you want — "make me an invoice printout that follows Bulgarian law" is enough — and it asks only what it genuinely needs (which document type, which details to show), builds it, and offers to put it where people work.

Each page below explains what the end result looks like, what to say to get it, and what you need to have in place.

Topics

• Document Printouts — a print button beside an open document that produces a clean A4 printout or PDF.
• Calculated Attributes — a new calculated field created directly in your ERP.net instance, with the expression written against your real model.
• BI Dashboards — from a chart in the chat to a standing dashboard app over your live data, placed in the Web Client menu.
• Scheduled Jobs — recurring work that runs on its own: nightly snapshots, Monday morning PDF reports by email, month-end recalculations.
• Business Rules — a new business rule in your ERP.net instance, described in plain language: validations, automatic values, and reactions to changes.
• Online Store Sync — an app that connects to your online store on a schedule: refreshes products and availability, imports new orders as ERP.net sales orders.
• Product Configurator — a public page where customers configure a product themselves, see the live price, and send an order-ready enquiry.

More implementation topics will be added here over time.