RestaurantOS Pro runs a restaurant's floor, kitchen and register, and issues every ticket as a legally valid Dominican fiscal receipt. ITBIS is calculated per line item instead of estimated from the total, so the numbers still hold when a bill is split or discounted. It installs locally on Windows and keeps taking orders when the internet drops. Built for a market most SaaS ignores.
Hi Product Hunt 👋
I build software for restaurants in the Dominican Republic, and the hard part here was never taking orders. It's that every ticket has to be a valid fiscal document under Law 32-23.
Most POS systems treat tax as an afterthought: they estimate the 18% ITBIS from the invoice total. That works until a table splits the bill or someone applies a discount, and then the numbers quietly stop matching what the tax authority expects. I've seen the cleanup that causes at month end.
RestaurantOS Pro calculates it per line item instead. It issues NCF and e-CF sequences, applies the legally mandated 10% tip and attributes it per employee, and exports the 606/607 reports the DGII asks for.
It also installs locally on Windows and keeps working when the internet drops. Not a feature I wanted to build, just one this market requires.
Happy to answer anything, especially about building vertical software for a market of 11 million people that global SaaS mostly ignores.