How All Four My Local Shops Apps Share Data Safely in the Cloud

My Local Shops is cloud inventory and billing software for clothing and footwear wholesalers. Trade Manager, Inventory Manager, Order Manager and Staff Bill use one connected business account, so a purchase received into inventory can later become a stock-safe invoice without the owner copying the same information between notebooks, WhatsApp chats and separate apps.

Cloud based does not mean every person sees everything. The owner apps keep sensitive purchase cost, landed cost, profit and reports within the owner's authorised business access, while Staff Bill receives only the operational access needed to create bills. The public My Local Shops website receives a separate customer-facing product view rather than the owner's private inventory record.

Connected cloud apps at a glance

Question	My Local Shops behaviour
Where is the business record kept?	In the owner's connected cloud account rather than only on one phone
Can the owner change phones?	Yes. Sign in with the same account to reach the cloud records again
Can the owner use more than one device?	Yes. Important stock-changing operations check current cloud data before saving
Does every app show every field?	No. Each app presents the part of the workflow its user needs
Can staff use the owner's billing data?	Only after the owner invites and authorises that staff account
Can staff see landed cost and profit?	Staff Bill does not show the owner-only cost, profit or reporting screens
Can website visitors read private product cost?	No. The public shop uses a buyer-safe catalogue view, not the private inventory document
What happens when a product photo changes?	A new image reference is saved so connected apps and the website can load the new photo without confusing it with the cached old one
What if two people sell the same SKU?	Final invoice save rereads current stock and commits the invoice and deduction together
Are owner apps protected when left signed in?	Trade Manager, Inventory Manager and Order Manager ask for the phone's existing screen security when the app is opened or resumed after the protection period

One business flow, four focused apps

The apps are separate because purchasing, inventory control, owner billing and counter billing are different jobs. Their records remain connected because the same wholesaler should not have to build four unrelated databases.

1. Trade Manager records the purchase journey

Trade Manager is the owner's purchase-tracking app. It follows a domestic or international trade from placement through shipment, charges, payments, delivery, claims and completion.

It helps answer questions such as:

• what was ordered from the supplier;
• what has been paid;
• which consignment is moving;
• what was actually received;
• whether goods were missing or damaged; and
• what applicable cost should be recovered through the received pieces.

The trade remains the purchase history. Completing it does not require the owner to retype every received item into an unrelated inventory system.

2. Inventory Manager turns received goods into sellable stock

Inventory Manager can receive eligible trade items and create or restock products. The owner reviews the goods, maps colours and sizes, confirms quantities, assigns shops or godowns, adds images, and maintains selling details such as item code, SKU, HSN and GST rate.

The private inventory record can include operational information that a customer must never see, including exact stock quantities and landed-cost information. Inventory Manager uses that private record for owner work while maintaining a smaller buyer-facing catalogue projection for the website.

3. Order Manager uses the same inventory for owner billing

Order Manager lets the owner find parties, select grouped products, add several colour-size SKUs, create GST or non-GST invoices, record collections, follow outstanding balances and review invoice profit.

The owner does not upload a second product catalogue into the billing app. Product names, item codes, SKU images, prices, HSN/GST details and current availability come from the connected inventory.

When an invoice saves, each inventory-linked line reduces the relevant location's stock. The invoice also retains the business snapshot required for historical billing and owner reporting even if the product is edited later.

4. Staff Bill gives authorised staff a narrower billing view

Staff Bill uses the owner's parties, products and billing locations after the staff member accepts an invitation from that owner. It is designed for the person at the billing counter, not as another owner dashboard.

The staff member can create and share invoices, record payment status, use the selected location's stock and open the bills needed for their work. Staff Bill does not provide the owner's landed-cost, profit, owner-report or CA-report screens.

The invoice still belongs to the owner's business. The owner can see the staff-created bill in Order Manager together with the recorded staff identity and the private business summary available to the owner.

What “shared data” actually means

Connected apps do not merely display identical copies of every document. They share business entities while preserving the responsibility of each app.

Business information	Created or mainly maintained in	Used by
Purchase trade and consignments	Trade Manager	Trade Manager and the approved inventory-receiving flow
Product, SKU and stock by location	Inventory Manager	Inventory Manager, Order Manager and Staff Bill
Buyer-safe catalogue details	Derived from Inventory Manager data	My Local Shops digital shop and product pages
Parties and delivery addresses	Order Manager or authorised Staff Bill user	Order Manager and Staff Bill
Sales invoice and payment state	Order Manager or Staff Bill	Both billing apps within the same owner business
Invoice cost and profit view	Calculated for the owner from stored invoice information	Order Manager only
Owner, CA and GST month-end reports	Generated from the owner's recorded billing data	Order Manager owner experience

This structure avoids two common problems:

1. Repeated entry — the same SKU does not need to be recreated separately for inventory, owner billing, staff billing and the digital shop.
2. Excess access — sharing a product for billing or public display does not require sharing the owner's complete private product record.

A realistic two-shop garment example

Suppose an owner runs wholesale garment shops in Bhiwandi and Mumbai.

A supplier sends one printed shirt design with four SKUs:

SKU type	Bhiwandi received	Mumbai received
Red / M	60	30
Red / L	55	25
Blue / M	50	20
Blue / L	45	15

The connected workflow is:

1. The owner tracks the supplier order, payments, transport and receipt in Trade Manager.
2. Inventory Manager receives the trade and creates the design with four SKU records.
3. The owner adds the product images, selling prices, HSN and GST rate once.
4. The buyer-facing digital shop can show the product and available types without showing exact quantities or landed cost.
5. The Mumbai counter staff opens Staff Bill and selects the Mumbai billing location.
6. The employee sells 10 Red / M and 5 Blue / L pieces.
7. Final save checks the latest Mumbai stock, creates the invoice and reduces only the selected Mumbai SKU quantities.
8. The owner opens Order Manager on another phone and sees the staff-created invoice, payment state and owner-only profit view.
9. Inventory Manager reflects the updated Mumbai availability without changing Bhiwandi stock.

The employee did not need the owner's password. The owner did not copy the staff invoice into a second ledger. The website did not receive the private quantity or cost record.

How changing a phone works

Business records should not disappear because a phone is damaged, replaced or reset.

The owner signs into the new installation using the same My Local Shops account. The app then reads the authorised cloud records for that business. A previously configured password can also provide an email-and-password sign-in route for an account originally created with Google, while normal password recovery is available from the signed-out flow.

There are still practical distinctions between cloud data and local device state:

• business records such as trades, products, invoices and payments belong to the cloud account;
• downloaded thumbnails and other temporary performance caches can be rebuilt on the new device;
• a newly installed app may need to download images again as they are viewed; and
• the person must use the correct account and complete the required device authentication.

Changing devices therefore does not require copying an application folder from the old phone. It does require access to the owner's authorised sign-in account.

Image updates without repeated heavy downloads

Garment and footwear catalogues depend heavily on images. Loading the full original photo every time a small product row appears would waste the user's mobile data and increase image-delivery cost.

The apps use small thumbnails in compact lists and reserve the larger image for places where the user deliberately opens or zooms the product. Long-lived device caching is useful because product photos usually do not change.

When an owner replaces a product image, the updated file receives a new identity rather than pretending to be the old cached file. The product and its buyer-facing catalogue record point to the new image. Other connected apps and the website can then discover the changed reference during their normal refresh and cache the new image independently.

This gives three benefits:

• repeat list views reuse downloaded thumbnails;
• customers and staff do not repeatedly download large originals; and
• an intentionally changed photo is not hidden behind a year-long cache of the previous file.

Multiple devices without silently corrupting stock

Cloud access allows more than one authorised device, but multi-device writing needs more than a simple last-write-wins update for important quantities.

Consider this case:

• Red / M has 98 pieces available;
• an owner starts an invoice for 60 pieces;
• a staff member on another phone starts an invoice for 50 pieces; and
• both screens initially saw 98.

Saving both deductions from their old screen values would incorrectly sell 110 pieces.

For an inventory-linked invoice, the system checks the current product record again during final save. Firestore transactions detect when a document read by the operation has changed. The operation is retried against the newer state; if the requested quantity no longer fits, that invoice is rejected for correction instead of producing negative stock.

The invoice and its stock deduction are treated as one operation. The system does not deliberately save three valid lines, fail a fourth line and leave a half-created invoice.

The same principle is used for critical inventory movements and received-trade commits: read the current state, validate it, and commit related changes together. This is what makes more than one owner or staff device practical without restricting the business to one phone.

What happens when two people edit ordinary information

Not every field is a stock counter. If two authorised users change an ordinary descriptive field at nearly the same time, the most recently accepted edit may become the visible value.

For example, one owner device may correct a product description while another changes it again. The system protects critical quantity and transaction flows more strongly because an incorrect stock deduction or partial invoice would damage business truth. Owners should still avoid asking two people to edit the same descriptive field simultaneously without coordination.

Cloud synchronization reduces stale copies; it does not remove the need for sensible operating responsibility.

Owner and staff access stay separate

An owner should not solve staff billing by sharing the main business password.

Staff Bill uses a deliberate relationship:

1. The owner sends an invitation to the employee's Google-account email.
2. The employee signs in using that exact account.
3. The employee accepts the invitation.
4. The staff account becomes connected to that owner.
5. The owner's active subscription and the live staff relationship are checked for staff business access.

A staff member cannot search across unrelated subscribers' parties or products. Party and product operations remain scoped to the connected owner.

Either the owner or staff member can end the relationship. Historical invoices retain the recorded creator identity even after that staff access is removed.

Owner-app protection on the phone

Owners do not normally sign out after every stock check or invoice. That makes application-level protection important when the phone is handed to another person.

Trade Manager, Inventory Manager and Order Manager use the phone's existing authentication capability. Depending on the device setup, this can include fingerprint, face authentication, PIN, pattern or device password.

The apps do not create another business PIN for the owner to remember. They ask Android to verify the person using the security already configured on the phone.

There is a short grace period around backgrounding so an accidental app switch does not create constant prompts. After the protected resume condition is reached, the owner must authenticate before the sensitive screen becomes usable again.

This protection is for casual physical access to an already signed-in device. It works together with account authentication and cloud access rules; it is not a replacement for them.

What the public website can and cannot read

The public digital shop needs enough information to help a buyer understand and inquire about a product. It does not need the owner's operational record.

The buyer-facing product view can contain information such as:

• product name and description;
• item code and SKU;
• colour and size;
• thumbnail and product image;
• selling price when the owner allows price display;
• HSN/GST catalogue details where applicable; and
• whether a type is currently available at a public shop.

The private inventory record remains restricted to the owner and authorised business staff. It can contain exact location quantities, cost information and operational provenance that should not be published.

This separation also helps performance: a product detail page can load its grouped buyer-safe listing without fetching every private SKU document.

What information is stored versus calculated

The platform keeps source records and derives summaries for particular jobs.

Stored business records

• purchase trades, consignments, payments and claims;
• products and SKU-level inventory by location;
• product images and thumbnails;
• parties and their saved addresses;
• invoices, invoice lines, payments and credit notes;
• staff invitation and authorisation relationships; and
• shop and godown records belonging to the subscriber.

Stored historical snapshots

An invoice keeps the relevant product, party, tax, price, cost and creator details required to understand that sale later. A later catalogue edit should not rewrite what the historical bill meant when it was created.

Calculated or maintained views

• dashboard stock worth, unit and SKU summaries;
• stock availability used by product pickers and the digital shop;
• invoice profit and margin for the owner;
• party outstanding totals;
• owner, CA and GST report totals; and
• landed cost per received unit after applicable purchase costs and receipt results.

These derived views exist to avoid repeatedly downloading and recalculating an entire business history for every screen.

Common misunderstandings and safe operating practices

“Cloud based means anyone with the app can see my data”

No. Installing an app does not grant access to another subscriber's business. Reads and writes are scoped through the signed-in owner or a live authorised staff relationship.

“Staff Bill is another owner login”

No. It is a deliberately narrower staff experience. Owners should use Order Manager for private profit and reporting controls.

“The quantity shown while selecting a product guarantees the save”

The visible number is a useful snapshot. Final invoice save checks current stock again because another authorised device may have changed it.

“A cached image means other apps will never see my replacement”

No. Intentional replacements receive a new image identity. Connected records point to that new reference, allowing each device to download it when needed.

“Changing my phone means transferring all app files manually”

No. Sign in with the same authorised account. Temporary local caches may rebuild, but the business records are associated with the cloud account.

“Cloud synchronization replaces every backup or export need”

Cloud storage protects the business from depending on one handset, but owners should still keep legally or operationally important exports such as shared invoices and monthly reports according to their own record-retention practice.

Frequently asked questions

Do all four apps need to be installed on one phone?

No. The owner can install the owner apps needed for their work, and authorised staff install Staff Bill on their own device. The cloud account connects the business records.

Can the same owner sign in on a second phone?

Yes. Multiple owner devices can read the same authorised business data. Critical stock-changing operations validate the current cloud state when saving.

Will changing phones delete trades, products or invoices?

No. Those records are connected to the owner's cloud account, not kept only inside the old phone. The owner must sign into the correct account on the new device.

If Inventory Manager changes a product image, will Order Manager update?

Yes. The product receives a new image reference. Order Manager, Staff Bill and the website can see that reference when their product data refreshes and then cache the new image.

Can Staff Bill see exact product cost or invoice profit?

Staff Bill does not show landed-cost, profit, margin or owner-report screens. Those remain part of the owner's Order Manager experience.

Can a customer visiting MLS see the exact stock quantity?

The public product projection communicates customer-facing availability. The private exact quantity and cost record is not the public product page.

What happens if two invoices try to sell the last pieces?

The first valid transaction can commit. The other operation then checks the changed stock and must retry against the current value; if insufficient, it fails for correction rather than forcing negative stock.

Does app lock upload my fingerprint or phone PIN?

No. The app asks the phone's operating system to authenticate the user with the device security already configured. The app does not need to receive the fingerprint or PIN itself.

Continue with the connected platform

• See how the complete purchase-to-report workflow works
• Read the Trade Manager complete guide
• Read the Inventory Manager complete guide
• Read the Order Manager complete guide
• Understand Staff Bill access and invoicing
• View and download all four business apps
• Compare current subscription plans
• Set up your business

My Local Shops connects the wholesaler's purchase, stock, billing and staff workflow without making one phone or one shared password the centre of the business. The cloud is useful because the right information follows the authorised user—and because private owner information stays separate from staff and public catalogue views.