Repairer - Repair Shop Management System 3.7 icon

Repairer - Repair Shop Management System 3.7

Repairer - Repair Shop Management System 3.7

Description

Repairer – Repair/Workshop Management System is carefully developed for easy management of any type of repairshop/workshop. It’s actually an innovative, simple and powerful management tool, designed and developed for you. It’s just your trusty employee. It’s a web based system where you can manage reparations, clients, inventory, purchases etc.

Demo

URL: preview.otsglobal.org/rms Email: admin@admin.com Password: password

Quick Installation Guide

Download .zip package Upload it to your server Extract the package Run the uploaded url via browser (EXAMPLE.COM/RMS/INSTALL). Here you have to provide the settings for RMS:
  • Hostname : database host name / IP
  • Database Name : create a mysql database for RMS on your host and write that name here
  • Database username : username of the created database (if applicable)
  • Database password : password of the created database

Backend – Admin:

  1. Dashboard (graphical report)
  2. General settings (system customization)
  3. Client management
  4. Reparation management
  5. Inventory Management
  6. Purchases Managment
  7. Taxes, Models, Categories etc.
  8. Graphical Reports ( Stock & Finance )

Frontend:

  • Reparation Status
  • Login

Notification/ Alert System

Notify clients with their reparation status via E-Mail or SMS

Documentation

Want to know more about Repairer? Please read our Documentation

How to Update

Change Log 3.5 to 3.6

  1. Download v3.6
  2. Take Database & Files Backup.
  3. Extract 3.6 files in place of 3.5
  4. Copy application/config/database.php from 3.5 backup to 3.6
  5. Copy application/config/config.php from 3.5 backup to 3.6
  6. Copy assets/uploads from 3.5 to 3.6
  7. Run following in PhpMyAdmin.
ALTER TABLE `settings` ADD `open_report_on_repair_add` BOOLEAN NOT NULL;
ALTER TABLE `settings` ADD `hide_repair_fields` LONGTEXT NULL AFTER `open_report_on_repair_add`;
ALTER TABLE `purchases` ADD `return_id` INT NULL AFTER `attachment`, ADD `surcharge` DECIMAL(24,2) NULL AFTER `return_id`, ADD `return_purchase_ref` VARCHAR(255) NULL AFTER `surcharge`, ADD `purchase_id` INT NULL AFTER `return_purchase_ref`, ADD `return_purchase_total` DECIMAL(24,2) NULL AFTER `purchase_id`;
ALTER TABLE `purchases` ADD `rma_number` VARCHAR(255) NULL AFTER `return_purchase_total`, ADD `return_status` VARCHAR(255) NULL AFTER `rma_number`, ADD `provider` VARCHAR(255) NULL AFTER `return_status`;
ALTER TABLE `purchases` ADD `track_code` VARCHAR(255) NULL;
ALTER TABLE `order_ref` ADD `rep` INT NOT NULL DEFAULT '1' AFTER `re`;
ALTER TABLE `purchase_items` ADD `purchase_item_id` INT NULL AFTER `unit_cost`;
UPDATE `settings` SET `version` = '3.6';
UPDATE `settings` SET `hide_repair_fields` = '{"expected_close_date":"1","error_code":"1","date_of_purchase":"1","has_warranty":"1","warranty":"1","warranty_card_number":"1","repair_type":"1","client_date":"1"}' WHERE `settings`.`id` = 1;
UPDATE `date_format` SET `js` = UPPER(`js`)

Change Log 3.0 to 3.5

  1. Download v3.5
  2. Take Database & Files Backup.
  3. Extract 3.5 files in place of 3.0
  4. Copy application/config/database.php from 3.0 backup to 3.5
  5. Copy application/config/config.php from 3.0 backup to 3.5
  6. Copy assets/uploads from 3.0 to 3.5
  7. Run the Update35.sql in PhpMyAdmin. Download here: otsglobal.org/cc_updates/rms/Update35.sql

Change Log 2.2 to 3.0

- Add Image in Inventory Table
- Fix Barcode Problem in Print Barcodes Inventory
- Update Repair Statuses (Completed checkbox thing)
- Fix any calculation issue for repairs with tax
- Settings -> order & reparation -> categories: can add category but disappears after saving
- Purchases -> download pdf : rounds up numbers, 2 decimals would be needed
- editing purchases: When it was set up as ordered and I go back editing to mark it as arrived or trying to do any modifications to it its not possible
- POS Open/Close Drawer different coins in settings
- Add SMSInfo.API android Gateway
- Add Original Nexmo API
- Add Pattern/Pin Lock System
- Warranty System
- Document Sign
- Calendar Widget show repairs too
- Add Reparation ITEMS change quantity and price
- Add Reparation Payments
- Add Sales Payments.
- Remove Advance Scene
- Add Paid System
- Import/Export Systems Customers
- Forgot password email system
- Activity Log
- Add Table State Save based on users
- custom sms api function. 
- Permission Lang
- And the tax is not appearing in POS invoice. 
- Change status directly from table
- And Much More
  1. Download v3.0
  2. Take Database & Files Backup.
  3. Extract 3.0 files in place of 2.2
  4. Copy application/config/database.php from 2.2 backup to 3.0
  5. Copy application/config/config.php from 2.2 backup to 3.0
  6. Copy assets/uploads from 2.2 to 3.0
  7. Create a folder named “signs” in assets/uploads
  8. Run the Update30.sql in PhpMyAdmin. Download here: otsglobal.org/cc_updates/rms/Update30.sql

Change Log 2.2 to 2.3

- Fixed some bugs
  1. Download v2.3
  2. Take Database & Files Backup.
  3. Extract 2.3 files in place of 2.2
  4. Copy application/config/database.php from 2.2 backup to 2.3
  5. Copy application/config/config.php from 2.2 backup to 2.3
  6. Copy assets/uploads from 2.2 to 2.3
  7. open application/config/config.php and replace
    $config['composer_autoload'] = TRUE;
    with
    $config['composer_autoload'] = FCPATH.'vendor/autoload.php';
    on line 140
  8. Run the following SQL in PhpMyAdmin:
UPDATE `settings` SET `version` = '2.3' WHERE `settings`.`id` = 1;

Change Log 2.1 to 2.2

- Added composer
- Replaced phpexcel with phpSpreadsheet
- Added Reparation in Client view modal
- Added Links on Client Name And Reparation code. 
- Remove Tax Rate Required Attribute
- Add Assigned To field
- Added Manufacturer field
- Added 3 Reports And Invoice Templates
- Add Barcode Generator for reparations
- Added different views for completed & pending repairs
- Add autocompletion to defect & category
- Add expected close date
- Add Imei to autofill repair details
- Add numeric codes for repairs
- And Much More
  1. Download v2.2
  2. Take Database & Files Backup.
  3. Extract 2.2 files in place of 2.1
  4. Copy application/config/database.php from 2.1 backup to 2.2
  5. Copy application/config/config.php from 2.1 backup to 2.2
  6. Copy assets/uploads from 2.1 to 2.2
  7. Create a folder named “backgrounds” in assets/uploads
  8. Run the Update.sql in PhpMyAdmin. Download here: otsglobal.org/cc_updates/rms/Update 2.2.sql

Change Log 2.0 to 2.1

- Fix jQuery in templates
- Tax on Total + Service Charge in Repair
- Add Theme Module
- And Bug Fixes
  1. Download v2.1
  2. Take Database & Files Backup.
  3. Extract 2.1 files in place of 2.0
  4. Copy application/config/database.php from 2.0 backup to 2.1
  5. Copy application/config/config.php from 2.0 backup to 2.1
  6. Copy assets/uploads from 2.0 to 2.1
  7. open index.php change $view_folder = ''; change it to $view_folder = 'themes';
  8. Run SQLs in PhpMyAdmin
ALTER TABLE `settings` ADD `theme` VARCHAR(100) NOT NULL AFTER `use_topbar`; UPDATE `settings` SET `theme` = 'adminlte'; UPDATE `settings` SET `version` = ‘2.1’;

Change Log 1.71 to 2.0

- Add Dark Theme
- Add Image for client
- ADD Google GEOLOCATE
- Add Google RECAPTCHA
- MPDF PDF CREATION FIX for PHP 7
- Add Actions Button other than simple buttons
- Reparation Log
- Add Calendar 
- Add Diagnostics Field
- Add Excel, PDF Export And Column VISIBILITY
- Add Logo in Invoice, Report
- CSS FIXES and Body Font - Appearance Tab — like JR
- Add Search Reparation in Side Menu
- CHANGE SMS/EMAIL SEND BTN Location 
- Add Gallery for Repair - Like JR
- Add Assigned To field in repairer
- Add Date Adder for comments
- ADD SETTINGS LINKS IN TOP NAVIGATION - Like JR
- ADD QUICK ADD ETC in top nav
- Fix Barcode - print Label
  1. Download v2.0
  2. Take Database & Files Backup.
  3. Extract 2.0 files in place of 1.71
  4. Copy application/config/database.php from 1.71 backup to 2.0
  5. Copy application/config/config.php from 1.71 backup to 2.0
  6. now open application/config/config.php and change line 140 from
  7.  
      $config['composer_autoload'] = FALSE;
      
    TO
     
      $config['composer_autoload'] = TRUE;
      
  8. Copy assets/uploads from 1.71 to 2.0
  9. Create folder named “images” in /assets/uploads
  10. Run the Update.sql in PhpMyAdmin. Download here: otsglobal.org/cc_updates/rms/Update 2.0.sql

Change Log 1.7 to 1.71

— Added Translations
  1. Download v1.71
  2. Replace downloaded 1.71 application/languages folder in your server rms_folder (1.7)
  3. Replace downloaded 1.71 application/views/_base/foot.php in your server rms_folder (1.7)

Change Log 1.6 to 1.71

— Added Inventory Images
  1. Download v1.7
  2. Backup your current rms_application files (v1.6) and export current database as sql (as pre-caution).
  3. Delete v1.6 rms_application files and extract v1.7 as replacement
  4. Restore rms_application/assets/uploads/logos & rms_application/assets/uploads/members folder from v1.6
  5. Restore rms_application/application/config/config.php, rms_application/application/config/database.php files from v1.6
  6. Go to phpMyAdmin , select your database and run the following SQL:
ALTER TABLE `inventory` ADD `image` TEXT NOT NULL AFTER `isDeleted`; UPDATE `inventory` SET `image`="no_image.png" WHERE 1; UPDATE `settings` SET `version` = '1.7' WHERE `settings`.`id` = 1;

Change Log 1.6

— Bugs Removed
— Fixed Translations
— Home Page Permissions
— Added Postal Code Field for clients
— Added Parsley.JS Form Validation
— Updated Codeigniter and AdminLTE
  1. Download v1.6
  2. Backup your current rms_application files (v1.5) and export current database as sql (as pre-caution).
  3. Delete v1.5 rms_application files and extract v1.6 as replacement
  4. Restore rms_application/assets/uploads/logos & rms_application/assets/uploads/members folder from v1.5
  5. Restore rms_application/application/config/config.php, rms_application/application/config/database.php files from v1.5
  6. Go to phpMyAdmin , select your database and run the following SQL:
ALTER TABLE `permissions` ADD `dashboard-qemail` BOOLEAN NOT NULL AFTER `categories-delete`, ADD `dashboard-qsms` BOOLEAN NOT NULL AFTER `dashboard-qemail`; ALTER TABLE `clients` ADD `postal_code` VARCHAR(50) NOT NULL AFTER `city`; UPDATE `settings` SET `version` = '1.60' WHERE `settings`.`id` = 1;

Update – v1.3 to v1.4

Change Log 1.40

— Added USER Permissions 
— Added email notifications  - add for every status;
— Added field - by from supplier - Inventory product
— Updated SMS Library
— fixed dataTables search
— Added categories
And Much More. 
  1. Download v1.4
  2. Backup your current rms_application files (v1.3) and export current database as sql (as pre-caution).
  3. Delete v1.3 rms_application files and extract v1.4 as replacement
  4. Restore rms_application/assets/uploads/logos & rms_application/assets/uploads/members folder from v1.3
  5. Restore rms_application/application/config/config.php, rms_application/application/config/database.php files from v1.3
  6. Go to phpMyAdmin , select your database and run the following SQL:
CREATE TABLE `categories` ( `id` int(11) NOT NULL, `code` varchar(55) NOT NULL, `name` varchar(55) NOT NULL, `image` varchar(55) DEFAULT NULL, `parent_id` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; ALTER TABLE `inventory` DROP `category`; ALTER TABLE `inventory` ADD `category_id` INT NOT NULL AFTER `model_name`, ADD `category` VARCHAR(250) NOT NULL AFTER `category_id`, ADD `subcategory_id` INT NULL AFTER `category`, ADD `subcategory` VARCHAR(250) NULL AFTER `subcategory_id`; ALTER TABLE `inventory` ADD `supplier` VARCHAR(250) NOT NULL AFTER `subcategory`, ADD `supplier_id` INT NOT NULL AFTER `supplier`; CREATE TABLE `permissions` ( `id` int(11) NOT NULL, `group_id` int(11) NOT NULL, `repair-index` tinyint(1) NOT NULL, `repair-add` tinyint(1) NOT NULL, `repair-edit` tinyint(1) NOT NULL, `repair-delete` tinyint(1) NOT NULL, `repair-view_repair` tinyint(1) NOT NULL, `customers-delete` tinyint(1) NOT NULL, `customers-view_customer` tinyint(1) NOT NULL, `customers-index` tinyint(1) NOT NULL, `customers-add` tinyint(1) NOT NULL, `customers-edit` tinyint(1) NOT NULL, `inventory-index` tinyint(1) NOT NULL, `inventory-add` tinyint(1) NOT NULL, `inventory-edit` tinyint(1) NOT NULL, `inventory-delete` tinyint(1) NOT NULL, `inventory-print_barcodes` tinyint(1) NOT NULL, `inventory-product_actions` tinyint(1) NOT NULL, `inventory-suppliers` tinyint(1) NOT NULL, `inventory-add_supplier` tinyint(1) NOT NULL, `inventory-edit_supplier` tinyint(1) NOT NULL, `inventory-delete_supplier` tinyint(1) NOT NULL, `inventory-models` tinyint(1) NOT NULL, `inventory-add_model` tinyint(1) NOT NULL, `inventory-edit_model` tinyint(1) NOT NULL, `inventory-delete_model` tinyint(1) NOT NULL, `purchases-index` tinyint(1) NOT NULL, `purchases-add` tinyint(1) NOT NULL, `purchases-edit` tinyint(1) NOT NULL, `purchases-delete` tinyint(1) NOT NULL, `auth-index` tinyint(1) NOT NULL, `auth-create_user` tinyint(1) NOT NULL, `auth-edit_user` tinyint(1) NOT NULL, `auth-delete_user` tinyint(1) NOT NULL, `reports-stock` tinyint(1) NOT NULL, `reports-finance` tinyint(1) NOT NULL, `reports-quantity_alerts` tinyint(1) NOT NULL, `auth-user_groups` tinyint(1) NOT NULL, `auth-delete_group` tinyint(1) NOT NULL, `auth-create_group` tinyint(1) NOT NULL, `auth-edit_group` tinyint(1) NOT NULL, `auth-permissions` tinyint(1) NOT NULL, `utilities-index` tinyint(1) NOT NULL, `utilities-backup_db` tinyint(1) NOT NULL, `utilities-restore_db` tinyint(1) NOT NULL, `utilities-remove_db` tinyint(1) NOT NULL, `tax_rates-index` tinyint(1) NOT NULL, `tax_rates-add` tinyint(1) NOT NULL, `tax_rates-edit` tinyint(1) NOT NULL, `tax_rates-delete` tinyint(1) NOT NULL, `categories-index` tinyint(1) NOT NULL, `categories-add` tinyint(1) NOT NULL, `categories-edit` tinyint(1) NOT NULL, `categories-delete` tinyint(1) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; INSERT INTO `permissions` (`id`, `group_id`, `repair-index`, `repair-add`, `repair-edit`, `repair-delete`, `repair-view_repair`, `customers-delete`, `customers-view_customer`, `customers-index`, `customers-add`, `customers-edit`, `inventory-index`, `inventory-add`, `inventory-edit`, `inventory-delete`, `inventory-print_barcodes`, `inventory-product_actions`, `inventory-suppliers`, `inventory-add_supplier`, `inventory-edit_supplier`, `inventory-delete_supplier`, `inventory-models`, `inventory-add_model`, `inventory-edit_model`, `inventory-delete_model`, `purchases-index`, `purchases-add`, `purchases-edit`, `purchases-delete`, `auth-index`, `auth-create_user`, `auth-edit_user`, `auth-delete_user`, `reports-stock`, `reports-finance`, `reports-quantity_alerts`, `auth-user_groups`, `auth-delete_group`, `auth-create_group`, `auth-edit_group`, `auth-permissions`, `utilities-index`, `utilities-backup_db`, `utilities-restore_db`, `utilities-remove_db`, `tax_rates-index`, `tax_rates-add`, `tax_rates-edit`, `tax_rates-delete`, `categories-index`, `categories-add`, `categories-edit`, `categories-delete`) VALUES (2, 4, 1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 0, 0, 1, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1); ALTER TABLE settings ADD `r_inprogress` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE settings ADD `r_approved` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE settings ADD `r_tobedeliver` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE settings ADD `r_delivered` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE settings ADD `r_cancelled` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE settings ADD `r_tobeapproved` longtext COLLATE utf8_unicode_ci NOT NULL; ALTER TABLE `settings` ADD `rows_per_page` INT NOT NULL AFTER `model_based_search`; UPDATE `settings` SET `rows_per_page` = '10' WHERE `settings`.`id` = 1; ALTER TABLE `settings` ADD `iwidth` INT NOT NULL AFTER `rows_per_page`, ADD `iheight` INT NOT NULL AFTER `iwidth`, ADD `twidth` INT NOT NULL AFTER `iheight`, ADD `theight` INT NOT NULL AFTER `twidth`, ADD `watermark` BOOLEAN NOT NULL AFTER `theight`; UPDATE `settings` SET `iwidth` = '800', `iheight` = '800', `twidth` = '150', `theight` = '150' WHERE `settings`.`id` = 1; ALTER TABLE `categories` ADD PRIMARY KEY (`id`), ADD KEY `id` (`id`); ALTER TABLE `permissions` ADD PRIMARY KEY (`id`), ADD KEY `id` (`id`); ALTER TABLE `categories` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `permissions` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT; UPDATE `settings` SET `r_inprogress` = 'Hello %customer%, your order/repair for %model% was opened by %businessname%. Check the state of repair anytime on %site_url%.' WHERE `settings`.`id` =1; UPDATE `settings` SET `r_approved` = 'Hello %customer%, your order/repair for %model% was approved. ' WHERE `settings`.`id` =1; UPDATE `settings` SET `r_tobedeliver` = 'Hello %customer%, your order/repair for %model% was opened by %businessname%. Check the state of repair anytime on %site_url%.' WHERE `settings`.`id` =1; UPDATE `settings` SET `r_delivered` = 'Hello %customer%, your order/repair for %model% was delivered by %businessname%. ' WHERE `settings`.`id` =1; UPDATE `settings` SET `r_cancelled` = 'Hello %customer%, your order/repair for %model% was cancelled. ' WHERE `settings`.`id` =1; UPDATE `settings` SET `r_tobeapproved` = 'Hello %customer%, your order/repair for %model% need to be approved ' WHERE `settings`.`id` =1;

Update – v1.3 to v1.4

Change Log 1.40

— Added Unlimited Repair Statuses
  1. Download v1.41
  2. Backup your current rms_application files (v1.4) and export current database as sql (as pre-caution).
  3. Delete v1.4 rms_application files and extract v1.41 as replacement
  4. Restore rms_application/assets/uploads/logos & rms_application/assets/uploads/members folder from v1.4
  5. Restore rms_application/application/config/config.php, rms_application/application/config/database.php files from v1.4
  6. Go to phpMyAdmin , select your database and run the following SQL:
UPDATE reparation SET status = 10 WHERE status = 3; UPDATE reparation SET status = 11 WHERE status = 2; UPDATE reparation SET status = 12 WHERE status = 0; UPDATE reparation SET status = 13 WHERE status = 5; UPDATE reparation SET status = 2 WHERE status = 10; UPDATE reparation SET status = 3 WHERE status = 11; UPDATE reparation SET status = 4 WHERE status = 12; UPDATE reparation SET status = 0 WHERE status = 13; CREATE TABLE IF NOT EXISTS `status` ( `id` int(11) NOT NULL AUTO_INCREMENT, `label` varchar(150) NOT NULL, `bg_color` varchar(50) NOT NULL, `fg_color` varchar(50) NOT NULL, `position` int(11) NOT NULL, `send_sms` tinyint(1) NOT NULL, `send_email` tinyint(1) NOT NULL, `sms_text` text, `email_text` text, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=5 ; INSERT INTO `status` (`id`, `label`, `bg_color`, `fg_color`, `position`, `send_sms`, `send_email`, `sms_text`, `email_text`) VALUES (1, 'In Progress', '#000000', '#ffffff', 1, 0, 1, NULL, 'Hello %customer%, your order/repair for %model% was opened by %businessname%. Check the state of repair anytime on %site_url%.'), (2, 'To Be Approved', '#ff0000', '#ffffff', 2, 0, 1, NULL, 'Hello %customer%, your order/repair for %model% need to be approved '), (3, 'Job done! ready to deliver', '#692121', '#ffffff', 3, 0, 1, NULL, 'Hello %customer%, your order/repair for %model% was opened by %businessname%. Check the state of repair anytime on %site_url%.'), (4, 'Delivered', '#1be323', '#000000', 4, 0, 1, NULL, 'Hello %customer%, your order/repair for %model% was delivered by %businessname%. '); Update – v1.2 to v1.3
  1. Download v1.3
  2. Backup your current rms_application files (v1.2) and export current database as sql (as pre-caution).
  3. Delete v1.2 rms_application files and extract v1.3 as replacement
  4. Restore rms_application/assets/uploads folder from v1.2 (Delete current rms_application/assets/uploads folder and paste v1.2’s rms_application/assets/uploads as replacement from backup.)
  5. Restore rms_application/application/config/config.php, rms_application/application/config/database.php files from v1.2
  6. Go to phpMyAdmin , select your database and run the following SQL:
ALTER TABLE `reparation` ADD `imei` TEXT NOT NULL AFTER `date_closing`; ALTER TABLE `settings` ADD `model_based_search` BOOLEAN NOT NULL AFTER `version`; UPDATE `settings` SET `version` = '1.30' WHERE `settings`.`id` = 1;

Change Log 1.30

Quantity Increase Bug Fixed
delete confirmation added
added IMEI field
fixed Responsive Tables 
Front Page Translation added
Russian Translation added
Menu Translation added
Import/Export Feature added
Repair create without adding defective items 
Alert Quantity added
And Much More. 

Counter

External listing. code.market does not sell this product and does not process payment for it. Pricing, payment, delivery, licensing, refunds, and support are handled by the third-party merchant on its own website. We may earn an affiliate commission from a referral. Details.

Products of the Week.

Submit
codester.com

codester.com

SocialDesk+: Omnichannel Social Commerce & Business Management Platform This is stronger than simply “Social Commerce and Messaging” because it tells buyers this is a complete business platform, not just a messaging script. Turn Social Conversations Into Sales SocialDesk+ is a complete omnichannel social commerce and business management platform built for businesses that sell and communicate with customers through social media. Instead of switching between WhatsApp, Facebook, Instagram and TikTok, businesses can manage customer conversations, comments, products, leads, follow-ups, automation, teams and business reports from one professional workspace. And because the full source code is included, developers, agencies and entrepreneurs can customize, rebrand and launch SocialDesk+ as their own business solution or SaaS platform. 🚀 Build Your Own Social Commerce Business SocialDesk+ gives you the foundation to launch: - Your own SaaS platform - A white-label social CRM - A social-commerce management system - A customer communication platform - A business messaging solution - A custom solution for clients - A multi-business subscription platform 💬 Connect Your Customers Supported social channels include: WhatsApp • Facebook • Instagram • TikTok Bring supported conversations into one centralized workspace and help businesses respond faster without constantly switching between platforms. 🛍️ More Than a Messaging Platform SocialDesk+ combines communication with the tools businesses need to manage customer opportunities: Inbox Manage customer conversations from connected channels. Comments Monitor and respond to social-media comments. Customers & Leads Organize customer information and potential buyers. Products & Catalog Manage products and give your team quick access to product information. Follow-Ups Make sure potential customers don't get forgotten. Automation Automate repetitive customer questions and responses. AI Assistant Provide AI-assisted communication when configured. Team Management Give managers and staff access to the business workspace. Reports & Analytics Track activity using business reports and analytics. The current product listing already includes these capabilities. 🔥 Why Buyers Will Want It Launch Faster Start with an already-built business platform instead of developing the entire system from zero. Customize Everything The full source code is included, allowing developers to change branding, features, workflows and integrations. Build a SaaS Create multiple business workspaces and offer SocialDesk+ as a subscription-based service. Sell to Businesses Offer it to retailers, restaurants, service businesses, online sellers, agencies and other businesses that communicate with customers through social media. Mobile + Web + Backend This isn't just a mobile UI template. It includes: - Flutter mobile application - Python / FastAPI backend - Web interface - Administration tools - Database infrastructure - API-based architecture - SQLite / PostgreSQL support - Android and iOS project structure 💼 One Platform. Multiple Business Opportunities. For SaaS Entrepreneurs Launch your own subscription platform and allow multiple businesses to operate inside separate workspaces. For Software Agencies Customize and rebrand the platform for clients instead of building an omnichannel business system from scratch. For Developers Use the complete source code as a foundation for your own social-commerce or customer-management product. For Businesses Deploy a dedicated version for your own customer-service and social-commerce operations. 🧩 What's Included Mobile - Flutter / Dart - Android - iOS project Backend - Python - FastAPI - SQLAlchemy - Alembic Database - SQLite - PostgreSQL Web - HTML5 - CSS3 - JavaScript Deployment - Docker - Docker Compose - Production configuration Business Platform - Multi-workspace architecture - Authentication - Teams - Customers - Products - Messaging - Comments - Automation - Reports - Subscriptions - Administration The current listing also documents third-party integrations such as Meta, TikTok, Stripe, Firebase, SMTP and optional OpenAI configuration. ⚡ What Makes SocialDesk+ Different? You're not buying a simple: ❌ Chat UI ❌ WhatsApp clone ❌ Flutter template ❌ Admin dashboard ❌ Basic CRM You're getting a complete business platform foundation that can be customized, branded and commercialized. Connect. Automate. Manage. Grow. SocialDesk+ Omnichannel Social Commerce & Business Management Platform One important change I'd make to the current listing The current page starts with: “A simple guide to managing your social conversations, customers, products and business activity.”

Other · 3,667 views · 31 clicks

$2

Repairer - Repair Shop Management System 3.7 | Code Market