nikki-erp

Package codify derives a machine code from a human label: "Nước ngọt có ga" → "nuoc_ngot_co_ga".

Package cronexpr parses and evaluates 5-field cron expressions in UTC.

Package json holds the JSON Schema describing a dynamic model definition, plus the validator used before a model JSON string is parsed into a builder.

Package advanced holds AdvancedPgQueryBuilder, the enhanced PostgreSQL graph query builder.

Package model provides robust and easy-to-use model mapper and utility methods for Go.

Package tabular reads the first sheet of an xlsx workbook or a csv document into a header row plus string rows.

Package accounting owns tax: master data, effective-dated configuration, determination rules and the calculation engine.

Package app holds the Accounting application services: the layer that authorizes a request and then delegates to a domain service.

Package services holds the Accounting business rules that reach for stored configuration.

Package tax implements determination, calculation, rounding and reversal, applied in that order.

Package settings declares what an organization may configure about its own tax handling.

Package dynamicengines declares the resource engines Accounting serves through the dynamic resource engine, and creates them during Init().

Package external binds Accounting's local ports to the services other modules publish.

Package currency publishes which currency an organization keeps its books in.

Package tax is the port other modules consume to have tax determined and calculated.

Package contacts holds the people and organizations the business deals with.

Package dynamicengines declares the resource engines the Contacts module serves through the dynamic resource engine, and creates them during the module's Init().

Package party declares the party capability that Contacts offers to other modules.

Package vendor declares the vendor capability that Contacts offers to other modules.

Package usagecheck asks the modules that reference a resource whether it is still in use, before the module owning it deletes it.

Package composable is the successor of package engine.

Package settings holds Essential's settings schemas.

Package dynamicengines declares the resource onions the Essential module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package external binds Essential's local ports to the services other modules publish.

Package currency declares the currency capability that Essential offers to other modules.

Package uom declares the UoM capability that Essential offers to other modules.

Package uomcat declares the UoM Category resource's layers.

Package settings holds iam's settings schemas.

Package dynamicengines declares the resource engines the IAM module serves through the dynamic resource engine, and creates them during the module's Init().

Package app holds the Inventory operations that span more than one domain service.

The only raw SQL in the Inventory module, a deliberate exception to the engine-first rule: reserving stock safely requires SELECT ...

Package dynamicengines declares the resource onions the Inventory module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package external binds Inventory's outbound ports to the services other modules and the core publish.

Package message speaks the broker's protocol for Inventory's integration event port.

Package external declares the ports Inventory consumes from other modules.

Package message is the port for Inventory's outbound integration events.

Package product is the Inventory module's cross-module port: the only Products capability other modules bind to.

Package stock is the port onto what Stock knows about a location.

Package warehouse is the contract for Warehouse operations spanning more than one resource: writes that touch a warehouse and its locations together, plus the flow reads the Stock movement engine plans against.

Package jobscheduler runs recurring jobs registered by other modules.

Package services holds the scheduling engine and the rules it applies.

This file contains the only raw SQL in the Job Scheduler, and it is a deliberate exception to the engine-first rule in docs/wiki/07 §6.7 rather than drift.

Package settings holds Notification's settings schemas.

Package dynamicengines declares the resource onions the Notification module serves through the composable resource engine, and registers them into the dependency container during the module's Init().

Package external binds Notification to the infrastructure and to other modules.

Package channels holds the distribution channels themselves.

Package delivery declares the contracts for raising and reading notifications.

Package cqrs receives the commands other modules dispatch into Notification.

Package paymentinvoice takes payments through the payment gateways the business has contracts with, and issues the invoices that account for them.

Package app holds the payment module's background work: notifying the ordering system that a payment settled, and the sweeps that recover orders no callback ever arrived for.

Package services holds the rules of the Payment & Invoice module: what may be paid, what may be refunded, and what state an order is left in when a gateway answers.

Package dynamicengines declares the resource engines the Payment & Invoice module serves through the dynamic resource engine, and creates them during the module's Init().

Package event publishes this module's announcements on the internal Watermill bus.

Package gateway builds the gateway registry this deployment will actually serve payments through, from configuration.

Package momo talks to MoMo, a Vietnamese e-wallet.

Package mpos talks to mPOS (NextPay), which drives a physical card terminal.

Package vietqr talks to VietQR, which settles bank transfers made by scanning a QR code.

Package event is what this module announces to the rest of the build when an order reaches a verdict.

Package gateway declares what a payment gateway must be able to do, and nothing about how any particular one does it.

Package invoice is the Payment & Invoice module's port for raising a fiscal document on behalf of another module.

Package order is the Payment & Invoice module's port for taking money and giving it back.

Package paymentmethod is the port through which another module reads this one's payment method master data.

Package v1 serves the gateway callbacks.

Package purchase covers the procurement cycle from request for quotation to confirmed purchase order.

Package services holds the rules of the Purchase module: the totals recomputation, the order and agreement lifecycles, and the audit trail that records them.

Package vendorpricing decides which vendor price applies to a purchase.

Package dynamicengines declares the resource engines the Purchase module serves, and creates them during Init().

Package external binds Purchase's local ports to the services other modules publish.

Package external declares Purchase's local ports onto the capabilities other modules offer, so that splitting a module into its own process changes only the binding in infra/external.

Package sales owns the commercial transaction: sales order and lines, pricing and promotion, billing, payment allocation, return and refund.

Package app holds the Sales application services.

Package services holds the Sales business rules.

Package pricing is the sales pricing engine: a pure function from a basket to a priced result.

Package settings holds Sales' settings schemas.

Package dynamicengines declares the resource engines the Sales module serves, and creates them during Init().

Package eventhandlers acts on the events Sales subscribes to.

Package external binds Sales' local ports to the services other modules publish.

Package invoicing binds Sales' fiscal-document port to whoever issues the documents.

Package message speaks the broker's protocol for Sales' integration event port.

Package repository holds the Sales repositories.

Package billing declares the commands the scheduler dispatches into Sales.

Package catalog declares the layers of the Sales catalogue resources: the fulfillment methods, channels and points a sale happens through, and the pricelists and combos it is priced by.

Package channel is Sales' outward-facing contract for sales channels and sales points.

Package event declares what Sales listens for on the internal event bus.

Package external declares Sales' local ports onto the capabilities other modules offer, so splitting a module into its own process changes only the binding in infra/external.

Package invoicing is Sales' port onto the issuing of legal fiscal documents.

Package fiscal declares the layers of the resources that turn a sale into a legal document: the request for an invoice, the instruction that says how to bill, and the record of each issuance attempt.

Package fulfillment declares the layers of the resources that carry out a sale: the fulfillment a confirmed order owes, the attempts made against it, and the record of a target being moved.

Package integration declares the layers of the two records Sales keeps about itself: the manual discounts granted on an order, and the outbox of integration events other systems consume.

Package message is the port for Sales' outbound integration events.

Package order is Sales' port for raising and settling an order from another module in-process.

Package promotion declares the layers of the promotion and voucher resources: the programs a discount is defined by, the conditions and rewards that shape it, and the voucher codes and redemption ledger that track its use.

Package quotation declares the layers of the quotation resources: the offer a customer is given before it becomes a sale, and the lines it quotes.

Package returns declares the layers of the return and refund resources: the customer's request to send goods back, the lines it covers, and the money paid back against it.

Package cqrs receives the commands the scheduler dispatches into Sales.

Package eventtransport subscribes Sales to the internal event bus and dispatches each event to the handler registered for its type.

Package v1 serves the Sales resources over HTTP.

Package settings gives every feature module one place to declare its configuration and have it stored, resolved and rendered, instead of each building its own settings table.

Package dynamicengines declares the resource engines the Settings module serves through the dynamic resource engine, and creates them during the module's Init().

Package settings declares the capabilities the Settings module exposes to the rest of the application: schema registration, and the per-level read and write of setting values.