Certified DIAN provider path
Contract, credentials, signing, transmission, contingency and authority conformance still require a selected authorized provider.
This board separates external proof required before a pilot, concrete work tracked in GitHub, and ideas that are only being explored. It is not a delivery calendar.
External evidence and operational rehearsals. No delivery date is promised.
Contract, credentials, signing, transmission, contingency and authority conformance still require a selected authorized provider.
Test the selected printer, drawer, scanner and payment terminal in a physical store-like environment.
Provision the shipped signed-HTTPS alert channel against a real receiver, verify its signatures and ownership, and observe it during a pilot. No 24/7 service is implied.
No unshipped local implementation issue remains in this delivery batch. New work enters here only when it has a concrete, feasible scope.
Possible directions only. They need field evidence and a narrower scope before becoming planned work.
Hosted deployment, backups and updates with a real operating and support model.
Evaluate safe direct transports beyond the current system-printing and TCP paths.
Tables, kitchen routing, tips and split bills only if a pilot validates this vertical.
A partner surface for integrations only after the public API and webhook contract are proven.
If something complicates your operation, open a GitHub issue. The proposal gets a public place for review and scoping; opening it does not promise a delivery date.