Version 2.2.0
We’re excited to introduce Version 2.2.0, which brings 50+ Reports to RestroPro SaaS.
v2.2.0 (Release Date)
- ✅ 50+ Reports Added
- Export reports to PDF
- Export reports to Excel
- New Dashboard Design added
Update Guide
Step 1: Update Database
ALTER TABLE orders
ADD COLUMN created_by varchar(255) DEFAULT NULL AFTER tenant_id,
ADD KEY orders_created_by_idx (created_by),
ADD CONSTRAINT orders_created_by_fk
FOREIGN KEY (created_by) REFERENCES users (username)
ON DELETE SET NULL
ON UPDATE CASCADE;
ALTER TABLE invoices
ADD COLUMN created_by varchar(255) DEFAULT NULL AFTER service_charge_total,
ADD KEY invoices_created_by_idx (created_by),
ADD CONSTRAINT invoices_created_by_fk
FOREIGN KEY (created_by) REFERENCES users (username)
ON DELETE SET NULL
ON UPDATE CASCADE;
CREATE TABLE IF NOT EXISTS printer_configs (
id INT AUTO_INCREMENT PRIMARY KEY,
tenant_id INT NOT NULL,
name VARCHAR(100) NOT NULL,
transport ENUM('bluetooth', 'tcp', 'usb') NOT NULL DEFAULT 'bluetooth',
address VARCHAR(255) NOT NULL COMMENT 'BLE MAC, TCP host:port, or USB vendorId:productId',
paper_size SMALLINT NOT NULL DEFAULT 80 COMMENT '58 or 80 mm',
is_default TINYINT(1) NOT NULL DEFAULT 0 COMMENT 'Default receipt printer',
is_kot_printer TINYINT(1) NOT NULL DEFAULT 0 COMMENT 'Designated KOT/kitchen printer',
auto_cut TINYINT(1) NOT NULL DEFAULT 1 COMMENT 'Auto-cut after print',
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
INDEX idx_tenant (tenant_id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;If any of these tables are missing, please refer to the v2.0.0 migration guide and complete those migrations first.
Step 2: Update Backend Code
- Replace the existing backend files with the latest version from the v2.1.0 release.
- Ensure all dependencies are installed by running:
npm install # or yarn install - Verify that Paystack SDK or API integration libraries are properly installed.
- Check your
.envfile for any new environment variables (if required by your backend implementation).
Step 3: Update Frontend Code
- Replace existing frontend code with the updated files from the v2_1_0 branch.
- Clear local storage/cache and rebuild the frontend for the changes to reflect.
- Verify that the Payment Gateways section in the superadmin panel now shows Paystack as an available option.