Your business makes sales. Is everything connected?

The work the cash register doesn't show

The problem isn't always a lack of sales. Sometimes each sale brings invisible work: noting what left the store, updating quantities, checking the payment, and entering the same details again to issue an invoice. Each step looks small on its own. Repeated all week, they add up to a second shift.

Imagine a sale recorded at the register but missing from the stock spreadsheet. The next day, someone promises a customer an item that's already gone. The team put in the effort; two parts of the same business simply weren't connected.

Before adding another tool, look for the gaps in that journey. That's often where the first opportunity for improvement lies.

A sale should update everything it needs to

Dorian Desktop is a Windows application that connects sales, stock, cash, purchasing, and other business workflows. The idea is for one transaction to feed the related areas, according to your business configuration.

In a counter sale, for example, the record connects the products sold, the inventory movement, and the payment method. When an electronic invoice is required and the integration is enabled, the workflow also includes a request to ARCA, Argentina's tax agency.

You can then review what happened without piecing it together by hand: reports show your operations, and traceability helps you follow movements and user actions. Scope is defined for each implementation: a store selling goods by weight and a distributor managing customer accounts need different workflows.

This diagram summarizes the workflow: movements depend on the operation and its configuration. The request to ARCA only applies when an electronic invoice is required and the integration is enabled; tax authorization depends on ARCA's response and is tracked with its own status.

ARCA as part of everyday operations

Separate invoicing often means re-entering information you already have: the customer, amounts, and tax status. Dorian integrates A, B, and C invoices and linked credit notes into the sales workflow, within the scope enabled for each installation.

ARCA provides web services for requesting authorization of electronic invoices. Dorian uses that connection to request the CAE authorization code and keep the tax information associated with the transaction. Invoice status matters as much as the PDF: recording a sale does not, by itself, mean ARCA has authorized it.

That's why a demo should cover the whole journey: which details are checked, how a pending response or error appears, and how you retrieve the invoice later. ARCA's official documentation is linked at the end.

Integrations and AI: less typing, more judgment

An integration is useful when it removes a repeated step or connects information you need to make decisions. In Dorian, external connections can include payment validation with Mercado Pago and AI analysis of supplier invoices, depending on your license and configuration.

Consider a purchase invoice with many line items. AI can help interpret its contents and speed up data entry. Its value lies in reducing transcription; products, quantities, and amounts still need to be reviewed before the information is accepted as correct.

To evaluate these tools, bring an invoice that reflects your everyday work. Ask what the system recognizes, what a person needs to review, and how differences are corrected. A concrete example tells you much more than a promise to automate everything.

Automation also helps with less eye-catching tasks: restocking notices, due dates, and outstanding items. Together with reports, these automatic alerts help you focus on exceptions without checking everything from scratch.

Your data on your infrastructure, with specific connections

Dorian Desktop runs with the database on your own infrastructure: it is an on-premise system. Essential sales, stock, and cash functions use that local database. Internet access is used for external functions such as ARCA, payment validation, and AI analysis.

Keeping data close gives you control over where your operations are hosted. That control goes hand in hand with user permissions, audit history, and a backup routine with verified restores. Local hosting alone does not replace those practices.

It also helps to distinguish the database from the information each integration needs: an external service must receive the data required for its function. The scope of those connections should be clear when setting up the installation.

A ten-minute exercise to get started

Pick a recent sale and follow it from the order to the daily close. Before changing anything, answer these questions:

• In how many places were the same details entered?
• Did stock update with the sale, or did someone have to correct it later?
• Can you connect the payment, the invoice, and the cash movement?
• If something doesn't match, can you find out what happened and who was involved?
• Which alert would have helped you spot the problem sooner?

Bring your answers to your first conversation with Dorian. Your actual way of working is the starting point: keep what works, connect what was separate, and reduce the tasks you repeat today.