Everything that matters, before we talk.

Dorian is an adaptable business management system that connects sales, cash register, inventory, expenses, customers, reports, and audit in a single operation. Configuration and modules adjust to each business's real workflow.

It's especially geared toward stores, corner shops, minimarkets, distributors, and operations with products sold by unit or by weight. Since every implementation is assessed individually, it can also adapt to companies with mixed workflows or particular processes.

No. Dorian starts from a modular architecture with configurable workflows. Only what the operation needs gets enabled, and rules, permissions, and flows are modeled so the business doesn't have to adapt to a generic package.

The current operational product is a Windows desktop application, with your database running on your own infrastructure — it doesn't depend on a cloud server to operate. It can connect with external services when a specific feature needs it, for example ARCA electronic invoicing, payment validation, or AI-based invoice analysis.

Not for the essentials. Sales, inventory, and the cash register work against your local database. An internet connection is only needed for specific features, like ARCA electronic invoicing, payment validation, or AI-based invoice analysis.

Depending on the license and scope: Home, Inventory, Purchase Orders, Sales, Treasury, Customers, Calendar, Reports, Audit, Human Resources, Suppliers, and ARCA tax integration, among other configurable capabilities. It also connects with external services like Mercado Pago or AI-based invoice analysis.

Yes. We can set up a conversation and a demo focused on your operation, showing you the workflows that actually matter instead of a generic presentation.

Pricing depends on the modules, users, and integrations your operation needs. There's no fixed off-the-shelf plan: it's defined during the initial assessment and presented as a clear proposal before moving forward.

We first assess how you currently work, the friction points, and what can't be interrupted. Then we design the solution, plan the rollout, and support the team's adoption.

Yes. Loading your initial products, customers, and inventory is part of the implementation, so you start operating in Dorian without losing your history. How complex the migration is depends on where the data is coming from, and it's assessed during the initial evaluation.

No. The goal is to respect what already works, fix what's causing errors, and automate repetitive steps. Any necessary changes are discussed and introduced with a clear path.

Yes. Each account can be tied to a role, and permissions determine which modules and actions it can use. Sensitive operations re-validate the permission when they execute, not just when the button is shown.

Yes. Appearance is a per-user preference, along with other personal options like language, row count, and notification channels.

Yes. The implementation can evolve in modules, users, permissions, alerts, and integrations. The specific scope depends on the license and the needs identified during the assessment.

Yes. Dorian's offering includes assessment, implementation, and ongoing support that continues after go-live to answer questions and fine-tune the workflow with real-world use.

Building the ticket and collecting payment are two separate steps. The ticket reserves inventory, and when the sale closes, stock is deducted, the payment is recorded, and Dorian attempts to generate the corresponding entry in the open cash register.

Cash, bank transfer, debit or credit card, QR, mixed payments, and Mercado Pago when that integration is configured. It calculates change for cash payments and splits the total between two methods for a mixed payment.

Yes. Sales with an outstanding balance are flagged and can later be settled from Treasury, selecting one or several tickets while always keeping a reference back to the original sale.

The sale closes and inventory is still deducted, but no automatic entry is generated in Treasury. That's why Dorian flags cash registers left open from previous shifts or days, and it's best to open the register before starting to sell.

Yes. Closing compares the calculated balance against the reported cash and transfers. If there's a difference, it's logged as an incident along with notes and the responsible user.

Yes. A sale can include collaborators and roles to split commissions according to the team's configuration.

Yes. Products can be sold by unit, by weight, or in mixed mode. You can also define price tiers per kilo, automatic unit-opening, and remainder management.

They're leftover amounts from products sold by weight. Dorian lets you discard them with a reason or set them aside for a remainder batch, keeping their history and stock traceability.

The batch increases inventory and can automatically generate the debt owed to the supplier. Once that debt is paid, the batch becomes protected against edits that would break accounting traceability.

If the Gemini integration is configured, Dorian can analyze a PDF, suggest matches against the catalog, and let you review quantity, cost, and expiration before creating the batch. Manual entry is always still available.

Yes. The analytics combine sales history, inventory, batches, and supplier data to estimate coverage, reorder point, criticality, and a suggested purchase, with global parameters and exceptions per supplier or product.

If the module is enabled, an order moves through the states Suggested, Sent, Confirmed, and Received. Receiving goods generates the actual batch and links it back to the order.

Yes. The home screen shows out-of-stock products, critical units, and upcoming expirations. Alert rules let you set thresholds and choose notifications inside the tool, by email, or both.

Yes. With the fiscal module enabled, Dorian integrates with ARCA's electronic invoicing services through WSAA and WSFEv1, validates the tax data, and requests the CAE when a sale closes.

Dorian issues Factura A, B, and C, along with their corresponding credit notes A, B, and C. For Factura A, the type is selected automatically when both issuer and recipient are registered VAT taxpayers and the customer is identified by CUIT.

It's the electronic authorization code issued by ARCA. Dorian requests it when the sale closes and stores the result, numbering, and tax status for lookup, audit, and reprinting.

The internal operation can still close, but the tax document is marked Rejected or Error and must not be delivered as a valid tax document. Dorian logs the attempt and allows automatic or manual retries with permission.

Yes. Final Consumer is the default option, and you can also select a customer with a DNI or CUIT and VAT status to include them as the recipient on the document.

Yes. A supplier's tax registration lets you validate the CUIT against the tax registry and store their legal name, VAT status, address, and contact details.

Yes. The Suppliers module can record the document, point of sale, number, amounts, attached file, and its link to the corresponding batch or debt.

Not necessarily. It depends on the contracted scope, whether the module is included in the license, and completing the configuration of the issuer, certificate, environment, and point of sale.

Yes. Audit logs creations, deletions, edits, and relevant events with user, date, module, action, and detail. Role changes and fiscal-authorization attempts are also traced.

Yes. Dorian supports manual or automatic backups, with configurable retention and encryption. They're stored in a local or network folder chosen by the client, never on a Dorian server.

Dorian runs as a desktop application with the database on your own infrastructure, not on a Dorian server or a third-party cloud. It only connects to external services for specific functions, like ARCA electronic invoicing. You decide where backups are stored.

Yes. The restore test uses an isolated temporary database, validates the schema, and deletes it when finished, without touching the production database. The result is logged for audit.

Yes. There's an Excel export for products, customers, suppliers, and sales. It's independent from the encrypted backup used for recovery.

Yes. It can be turned on per user and requires a six-digit code sent by email. In addition, five incorrect passwords temporarily lock the account for 15 minutes.

Fill out the contact form, write to us at administracion@dorianteam.com, or call us at +54 9 11 3012-9421. The first conversation is no-commitment.