Choosing ERP for an electronics or computer shop in Bangladesh
Choosing ERP for an electronics or computer shop in Bangladesh: serial numbers, warranty and RMA, bank EMI, PC Builder, POS, online store and Mushak 6.3.
By SORS Technology team 6 min read
Walk through Multiplan Center on Elephant Road, IDB Bhaban in Agargaon or the computer market in Agrabad and every shop has the same problems: a serial number that has to be traced back to a purchase, a customer waving a warranty card, a bank EMI form to fill in, and a Mushak challan to issue on the same sale. Generic accounting software was not built for this. This guide lists what an ERP has to do for an electronics or computer shop in Bangladesh, and how to test each point before you buy.
Why a generic package struggles here
A grocery item is a quantity. A laptop is an individual. The shop needs to know which unit, bought on which purchase bill, at what cost, with what warranty, went to which customer, and whether it came back. Add bank EMI, where the monthly figure differs by tenure and bank, and an online store where a customer builds a PC from compatible parts, and a spreadsheet plus an accounting package cannot keep up. See the electronics and computer shop industry page for the full picture.
Serial numbers: the heart of the system
Every requirement below depends on serial tracking. The ERP should:
- capture serial numbers at goods receipt, by scanning or by importing the supplier’s list;
- reserve and sell specific serials on the invoice, so the receipt shows the exact unit;
- show, for any serial, its purchase bill, cost, sale invoice, customer and warranty status;
- move serials between outlets and the godown on stock transfers;
- handle serials on sales returns, RMA and vendor claims.
Test it in the demo: receive three units of one item with serials, sell one at the POS, return it, and search for its serial. If the vendor has to leave the room, move on. See inventory management.
Warranty and RMA without a paper register
Most shops track warranty in a register or on the invoice copy. Problems start when the customer comes back a year later without paper. The ERP should record the warranty period per item or per serial at sale, look up any serial to show whether it is under warranty, open an RMA request with the fault description, track the unit through diagnosis, repair, replacement or refund, keep RMA stock separate from saleable stock, and raise a vendor claim to the distributor with the original purchase reference. Alerts for units sitting too long in RMA save arguments with both the customer and the distributor. See RMA and warranty.
Bank EMI at the counter
Card EMI through banks is how a large share of laptops, phones and appliances are sold in Bangladesh. The complication for the shop is that each bank offers different tenures, and the settlement from the bank may differ from the sticker price. The ERP should hold EMI templates per bank with the tenures each offers, apply the plan to the invoice so the customer’s monthly amount is printed, and record the bank as the paying party so your receivable is from the bank, not the customer. The sales module in SORS ERP carries EMI templates for exactly this.
PC Builder and your online store
Computer shops sell to a customer who often wants to configure: a processor, a compatible motherboard, RAM of the right type, a power supply of adequate wattage. On a website that means a configurator that knows compatibility rules and prices the build from live stock. If the online store is a separate system with its own product list, prices and stock drift within days.
The better pattern is the ERP as the back end: one item master with specifications, one stock, one price list, and the storefront reading from it. SORS ERP includes a PC Builder and a Keyboard Builder as part of its headless e-commerce module, with a storefront that reads live stock and EMI plans. Ask any vendor to show an online order arriving in the same order list as counter sales.
Online orders also have to be delivered. In SORS ERP’s courier and delivery module, Steadfast is booked from the order by API; Pathao, Paperfly and CarryBee are recorded with the consignment number your team enters, and their payout statements can be uploaded to reconcile cash on delivery. Parcel labels come from the courier’s own panel, because label file generation inside the ERP is still a placeholder. For a shop sending a few laptops a week that is a small thing; for high parcel volumes ask about the roadmap before you commit.
POS for a busy counter
The counter at a computer shop is slower than a grocery till and more detailed. Look for barcode and serial scanning, held bills while the customer checks with a relative, split payments across cash, card and bKash, a printed receipt that doubles as the warranty record, counter sessions with end of day Z-reports, and outlet-level access so a Dhanmondi salesperson cannot see Uttara’s margins. See POS software.
Mushak 6.3 on every sale
Electronics shops issue many invoices to registered buyers, corporate offices buying twenty laptops, for example, who need a proper Mushak 6.3 with their BIN to claim input credit. The ERP should generate the 6.3 at the point of sale with sequential numbering, keep the 6.1 purchase register up to date automatically, and lock periods after the 9.1 is filed. Our Mushak 6.3 guide covers the detail, including what must appear on the form.
Items, specifications and pricing
A specification template per category (screen size, processor, RAM, storage) makes the item master consistent and powers filters on the website. Price tiers let you give a corporate customer or a reseller a different price without editing every invoice, and pricing history tells you what a model sold for last Eid. Bulk price updates matter in a market where the dollar rate moves prices weekly. See items and pricing.
The checklist
| Requirement | Why it matters | How to test in the demo |
|---|---|---|
| Serial numbers on purchase, sale, transfer and return | Traceability, warranty, theft control | Receive, sell, return and search one serial |
| Warranty lookup by serial | Customer arrives without paper | Search a sold serial and show the warranty end date |
| RMA workflow with vendor claims | Units sitting at the distributor | Open an RMA and raise a vendor claim |
| EMI templates per bank | Correct monthly figure on the receipt | Sell one item on a 12-month plan |
| PC Builder or configurator | Online sales of custom builds | Build a PC on the storefront from live stock |
| POS with split payments and Z-report | Busy counter, mixed payments | Split one sale across cash and bKash and close the day |
| Mushak 6.3 with BIN | Corporate buyers need input credit | Print a 6.3 for a registered customer |
| Multi-outlet stock and transfers | Shops in two markets | Transfer a serial between outlets |
| Specification templates and price tiers | Consistent listings, reseller pricing | Create an item from a template and apply a tier |
Score each row yes, partial or no for each vendor, and weight serial numbers and RMA highest; they are the rows that cannot be fixed with a workaround later.
Where SORS ERP fits
SORS ERP was built with computer and electronics shops in mind: serial number tracking, RMA and warranty with vendor claims, bank EMI templates, POS with Z-reports, Mushak 6.3 and a headless online store with a PC Builder are all live modules. We are a young company, founded in 2024, and there is no native mobile app; the web app installs on Android phones as a PWA. We do not have a direct bKash merchant API yet, so bKash at the counter is recorded as a payment method and online bKash comes through SSLCommerz. On the courier side, Steadfast is API integrated while Pathao, Paperfly and CarryBee use manual consignment entry with statement upload, and label files from the ERP are on the roadmap.
Bring a supplier challan with real serial numbers and a bank EMI chart to a demo and we will run the whole flow on it; request a demo.
Written by the team that builds SORS ERP, the ERP described on this site. We implement it ourselves in Bangladesh, so the guidance here comes from setups we run rather than from general research. More about SORS Technology.
Frequently asked questions
Can an ERP track serial numbers from purchase to sale and return?
Yes, if serial tracking is built into inventory rather than added as a note field. Serials should be captured at goods receipt, selected on the invoice, moved on transfers and followed through returns and RMA. Test it in the demo by receiving, selling, returning and searching for one serial.
How does bank EMI work inside the ERP?
The ERP holds EMI templates per bank with the tenures each bank offers. On the invoice you choose the bank and tenure, the monthly amount is printed for the customer, and the bank is recorded as the paying party so the receivable is from the bank. The customer's card is processed on the bank's terminal as usual.
Can the same ERP run my online store?
In a headless setup, yes. The ERP holds the items, specifications, prices, stock and EMI plans, and a storefront reads from it, so online and counter sales share one stock. SORS ERP includes a PC Builder configurator for exactly this purpose.
What about warranty claims to the distributor?
An RMA module records the customer's claim, tracks the unit through diagnosis and repair or replacement, and raises a vendor claim to the distributor with the original purchase reference and serial. RMA stock is kept separate from saleable stock, and alerts flag units that have sat too long.
From the blog
- How to choose ERP software in Bangladesh: a 15-point checklist
A 15-point checklist for choosing ERP software in Bangladesh: Mushak VAT, bKash payments, Bangla, support, data export, offline resilience, cost and contract.
- From Facebook page to fulfilled order: F-commerce with Steadfast, Pathao and an ERP
Run a Facebook shop in Bangladesh properly: order intake, confirmation SMS, courier booking with Steadfast, tracking, returns and COD reconciliation in one ERP.
- Payroll in Bangladesh: attendance, overtime and income tax without spreadsheets
Payroll in Bangladesh without spreadsheets: ZKTeco attendance sync, shifts, overtime, advances, tax slabs set per NBR circular, payslips and final settlement.