What Happens to Your Business Data When You Change Your Phone?

When an owner changes, resets or loses a phone, My Local Shops business records do not have to be recreated from memory, notebooks or old WhatsApp chats. Trades, products, stock, parties, invoices, payment records and reports belong to the authorised cloud account rather than only to one handset.

Install the correct app on the new Android phone and sign in with the same account. The app can then read that account's authorised records again. A few things that belong only to the physical device—such as downloaded files, the image cache, a paired label printer and the last selected billing location—must be downloaded or configured again.

What follows you and what stays on the old phone

Information or setting	Available after signing in on a new phone?	What to expect
Purchase trades, suppliers, payments, shipments and claims	Yes	Trade Manager reads them from the same owner account
Products, colour-size SKUs, prices, cost and stock by location	Yes	Inventory Manager reads the current cloud records
Parties, invoices, credit notes, outstanding and payments	Yes	Order Manager or authorised Staff Bill reads the relevant owner data
Owner and CA report source records	Yes	Reports can be prepared again from the recorded business data
Shop/godown and public digital-shop information	Yes	These belong to the seller account, not one device
Product and trade-proof image files	Yes, when still attached to cloud records	The new device downloads them again as they are viewed
Cached thumbnails and temporary image copies	No	They are rebuilt automatically; losing cache does not delete the original business record
Last selected billing location	No	Choose the billing/dispatch location again on the new device
Paired Bluetooth label printer	No	Pair the printer with the new phone and select it again
Label display preferences	No	Recheck whether the label should show shop name, phone and item code
PDFs or CSV files downloaded into the old phone's storage	No	Keep or transfer those files separately; supported records and reports can be generated again
Camera, notification, Bluetooth and file permissions	No	Android may ask for permission again on the new installation

This is the practical difference between cloud business data and device-local convenience data.

Cloud access is not the same as copying an app folder

With a phone-only ledger, the only complete copy may live inside the old device. If the handset is damaged or reset before export, the owner may lose years of records.

My Local Shops works differently. The four apps connect to the same authorised business account:

• Trade Manager keeps the purchase journey and landed-cost inputs;
• Inventory Manager keeps products, SKUs and location stock;
• Order Manager keeps owner billing, collections, outstanding, profit and reports; and
• Staff Bill lets an invited employee create bills under the owner's business without receiving owner-only screens.

Signing in on a new phone is therefore an account-access process, not a phone-to-phone database transfer. The old handset does not have to be available merely to make the cloud records appear.

This should not be misunderstood as an independent accounting archive or a replacement for every legally required export. Important PDFs and reports should still be retained according to the business's normal accounting practice. The key benefit is that day-to-day operational records are not tied to one physical phone.

Before changing a phone: the safest process

If the old phone still works, use this sequence:

1. Confirm that the app is using the intended My Local Shops account.
2. Make sure recent work has saved successfully and no form is still waiting to be submitted.
3. Download or share any PDF, CSV or other local file that must be kept outside the app.
4. Confirm that the same Google account can be used on the new phone, or that an MLS password has already been created for that email.
5. Install the official current app on the new Android phone.
6. Sign in with the same account and verify a few important records.
7. Re-select the billing location and reconnect local accessories where applicable.
8. Sign out on the old phone before selling, exchanging or giving it to another person.
9. Remove the old device from the relevant Google-account security page if it will no longer remain under the owner's control.

Do not create a second account merely because the phone is new. A different email represents a different identity and will not automatically become the owner of the first account's business records.

Signing in on the new phone

New My Local Shops owner accounts are created through Google sign-in. An owner who originally joined through Google can also create an MLS password for the same email from the supported account settings flow.

That provides two practical routes:

1. Continue with Google using the same Google account; or
2. Email and MLS password using the same email after that password has been created.

Creating an MLS password does not turn the Google account into a different seller. Both routes identify the same Firebase account when set up correctly.

If the MLS password is forgotten, use the signed-out Forgot password option and follow the reset email. If the owner never created an MLS password, Google sign-in remains the normal route.

The most important rule is simple: use the same authorised account, not merely the same name, phone number or shop name.

What happens inside each app after the move

Trade Manager

The owner can reopen active and completed domestic or international purchase trades, including suppliers, ordered items, recorded payments, consignments, charges, received quantities, claims and calculated actual cost.

Private proof images may download again when opened because the new phone has no existing cache. Trade Manager also protects its signed-in screens using the new phone's configured device security.

Local trade reminders or notification state from the old handset should not be treated as a cloud archive. Review the active trades and notification permission on the new device.

Inventory Manager

Products, item codes, colour-size SKUs, stock quantities, selling prices, cost, images and shop/godown allocation come from the business account.

A Bluetooth label printer's pairing is deliberately device-local because its address is useful only to the phone physically connected to that printer. Pair it again. The last choices for showing shop name, phone or item code on labels are also local preferences and should be reviewed.

The first catalogue visit may use more mobile data than a repeat visit because thumbnails are being downloaded into an empty cache. Later views can reuse those cached images.

Order Manager

The owner can see parties, recent invoices, outstanding balances, payments, credit notes, invoice profit and available report workflows again.

The default billing/dispatch location is a convenience stored on each device. If the business has two shops and a godown, select the correct location again before the first invoice. This prevents the new phone from silently assuming the wrong shop.

Staff Bill

The employee installs Staff Bill and signs in with the same invited Google account. If the invitation relationship is still active, the app can reconnect to the owner's authorised billing data.

The employee must choose the billing location again because that sticky selection belongs to the device. Staff should verify the shop name, address and available stock before creating the first bill from a replacement phone.

Why product images may load again

My Local Shops uses thumbnails in small catalogue rows and larger files when a person deliberately opens an image. Device caching avoids repeatedly downloading an unchanged product photo, which reduces Firebase delivery cost, page waiting time and the user's mobile-data consumption.

A new phone starts without the old phone's cache. It therefore downloads the relevant thumbnails and images as they are needed, then keeps reusable local copies according to the app's cache policy.

This does not mean the product photo was lost. The cache is only a performance copy. The cloud record continues to reference the stored image.

When an owner intentionally replaces a product photo in Inventory Manager, the new file receives a new image identity. Order Manager, Staff Bill and the public digital shop can discover the new reference during normal refresh instead of continuing to mistake an old year-long cached image for the current one.

What logout removes and what it does not

Signing out removes access to the signed-in account on that app. The apps also clear sensitive or session-related local image state, including private trade-proof cache where applicable.

Reusable product-photo cache may remain on the device because catalogue images are not treated like private trade proofs and retaining them reduces repeated data transfer. A cached image by itself does not grant access to the seller's cloud records, invoices, payments, cost or reports.

If a phone will be sold or transferred, do not rely only on application cleanup. Sign out, remove the Google account from the device where appropriate, and perform the phone manufacturer's secure reset process.

What if the phone is lost or stolen?

If the owner cannot access the old phone:

1. Secure the Google account immediately and use Google's device controls to lock or sign out the missing device where available.
2. Change any MLS password that may have been known or stored insecurely.
3. Install the required apps on a trusted phone and sign in using the same authorised account.
4. Check recent trades, inventory changes, invoices and payments for unfamiliar activity.
5. Contact My Local Shops support if account access or business activity looks suspicious.

Trade Manager, Inventory Manager and Order Manager also use Android's existing screen lock—fingerprint, face, PIN, pattern or device password—to protect an already signed-in owner app. My Local Shops does not receive or store the owner's fingerprint or phone PIN; Android performs that verification.

Device lock reduces casual access to a lost, unlocked session. It does not replace prompt action on the Google/MLS account when the physical phone is no longer under the owner's control.

Can old and new phones both remain signed in?

Yes, more than one authorised device can use an owner account. A replacement phone does not automatically corrupt data merely because the old phone still exists.

Critical stock-changing operations do not rely only on the quantity that was visible when a screen first opened. Invoice saving and important inventory writes recheck current records and use transaction-safe updates. If another device changes the same SKU first, Firestore detects the changed document and the operation is retried or rejected when the requested quantity is no longer valid.

For example, suppose both phones initially display 100 pieces. The old phone invoices 70, leaving 30. The new phone then tries to save an invoice for 50 based on its earlier screen. The final save must use the current state; it should not silently push stock to minus 20.

Ordinary descriptive edits are different. If two authorised people change the same product description at nearly the same time, the most recently accepted value may become visible. Owners should still assign clear responsibility for editing the same record.

Read how all four apps share data safely in the cloud for the detailed data-flow and concurrency explanation.

Real example: moving a two-shop clothing business

An owner has a Bhiwandi shop, a Mumbai shop and one godown. The business has 900 products, colour-size SKUs, unpaid retailer invoices and several active supplier trades.

The old phone stops charging. On a new Android phone, the owner installs Inventory Manager and Order Manager and signs in with the same account.

The result is:

• the products and SKU stock for all three locations become available again;
• parties, invoices, payments and outstanding totals remain attached to the business;
• owner reports continue to use the recorded invoice history;
• the digital wholesale shop remains connected to the inventory data;
• images begin downloading again when catalogue rows are opened;
• the owner selects Mumbai as the billing location before making a Mumbai invoice; and
• the label printer used at Bhiwandi must be paired separately with the phone that will print there.

No one re-enters 900 products. No one rebuilds the retailer ledger from screenshots. Only the device-specific setup is repeated.

Common mistakes to avoid

Creating a new Google account

A new account does not inherit another account's business merely because both accounts belong to the same person. Recover or use the original authorised identity.

Assuming downloaded files are cloud records

An invoice record in the app and a PDF saved in the Downloads folder are different things. Transfer locally saved files separately when they must be retained exactly as downloaded.

Billing before choosing the location

The new phone does not inherit the old phone's sticky billing-location choice. Confirm the shop or godown before the first invoice.

Expecting the old image cache

The first product list can download thumbnails again. That is expected after a fresh installation and does not mean every future visit will redownload them.

Sharing the owner's login with staff

Changing staff phones does not justify sharing the owner's Google or MLS password. Invite the employee's account and use Staff Bill so owner-only cost, profit and reports remain separated.

Leaving the old phone signed in before resale

Verify the new phone first, then sign out and securely reset the old device before it leaves the owner's control.

Frequently asked questions

Will changing my phone delete my inventory?

No. Inventory belongs to the authorised cloud account. Sign in with the same account to access the current product and stock records.

Will my invoices and outstanding balances appear on the new phone?

Yes. Order Manager reads those business records from the same owner account. Staff Bill sees the records allowed by its active staff relationship.

Do I need to buy another subscription for the new phone?

No. The subscription belongs to the seller account, not to one physical handset. Current plan limits and access rules still apply.

Must I copy the old app folder?

No. Install the official current app and sign in with the same account. Transfer only device-local downloads that you separately want to retain.

Why are product photos downloading again?

The new phone has an empty image cache. It downloads thumbnails and larger images as needed, then reuses cached copies for later views.

Will my paired label printer follow me automatically?

No. Bluetooth pairing and printer selection are specific to the device. Pair and select the printer again.

Can staff use a new phone?

Yes. They should install Staff Bill, sign in with the same invited Google account and select the correct billing location again.

What if I forgot my MLS password?

Use the signed-out Forgot password flow for the same email. If the account was created with Google and no MLS password was added, use Google sign-in.

Can I use the apps on two phones at once?

Yes. Critical stock and invoice writes use current cloud state and transaction-safe validation. Avoid simultaneous edits to the same ordinary descriptive field.

Does signing out delete my products from the cloud?

No. Signing out removes that app's account access on the device; it does not delete the seller's cloud business records.

Continue with the right setup

• See the complete connected-cloud explanation
• Choose the correct owner and staff apps
• Subscribe, download the apps and set up your first shop
• View all My Local Shops business apps
• Compare current plans and pricing

Cloud access removes the fear that one broken phone will erase the working history of a wholesale business. The correct account brings back the business records; the new phone only needs its own local setup.