[UPDATE GUIDE] Updating RetailMan ERP System

Use this guide when updating RetailMan ERP System to a newer release.

Important: Always take a full backup before replacing files or running an update.

Before You Update

Back up the following and keep the backup in a safe location:

Database backup: export the database used by RetailMan ERP System.
public/uploads folder.
.env file.
Translation files, if you added or customized languages:
- resources/lang/
- public/js/lang/

Do not continue until these backups are complete.

Update Steps

Download or prepare the new release files.
Extract the new release package.
Replace the old application code in your project directory with the new code.
Make sure your existing .env file is still present. If it is missing, restore it from your backup.
Open the update URL in your browser:

https://yourdomain.com/install/update/
Wait for the update process to finish. Do not close, refresh, or go back while the update is running.
After the update completes, the application should redirect to the login page or dashboard.
Check the footer or About page to confirm the latest application version is showing.
If required, restore or verify the public/uploads folder from your backup.
Test the main workflows before allowing users to continue daily work.

If The Update Fails

If there is a problem during the update:

Do not keep retrying without checking the error.
Review the latest log file in storage/logs.
Confirm file permissions, PHP version, and database access.
If needed, restore the backed-up database and files.
Run the update again after fixing the cause.

After A Successful Update

After a successful update, this URL should no longer run the updater:

https://yourdomain.com/install/update/

It may show a 404 page or no longer be available. This is expected after the update has completed.

Additional Steps For API Or Connector Module

If your installation uses an API, Connector, or integration module, review that module after updating:

Confirm the module is still enabled.
Confirm API credentials and tokens are still present.
Test one API request or integration sync.
Check module-specific settings for new required fields.

FAQ

Q: Will skipping one or two updates cause errors?

A: Usually, no. The updater is designed to update from older versions to newer versions. Still, always read the release notes and take a complete backup before updating.