App Security Basics for Sellers

An app concentrates your catalogue, your orders and your customer list behind a single login, and that is both the convenience and the exposure. Whoever holds that login can change prices, read addresses and follow the money through settlements. Security for a small store is less about stopping sophisticated attacks and more about controlling who can open which door, and noticing quickly when one opens without permission.

Start With Account Access

Every security decision begins with the account that owns the store. That account should hold a password used nowhere else, long enough that guessing is impractical and kept in a password manager rather than a notebook or a chat message.

Where the platform offers a second step at login, switch it on for the owner account first. A code from a phone or an authenticator app means a stolen password alone is not enough to get inside.

Shared logins deserve a hard rule: one person, one account. When three staff members use the same owner credentials, the activity log can no longer tell you who did what, and removing one person means changing the password for everyone.

Give Staff Only What the Job Needs

Access should match the task. Someone packing orders needs the order list and the dispatch screen, not the payment settings or the customer export. A catalogue editor needs products and categories, not settlements. Splitting access by role limits what a mistake or a grudge can reach.

• Order handling: view and update orders, print packing slips.
• Catalogue: add and edit products, manage stock and categories.
• Delivery: see addresses and routes, update delivery status.
• Finance: view settlements and refunds, restricted to the owner.
• Settings: domains, payment and staff permissions, owner only.

If the platform supports named roles, use them instead of building access by hand. Named roles are easier to audit and easier to correct when someone changes duties.

Turn Access Off When Someone Leaves

Offboarding is where small stores leak access most often. A departing staff member may keep a working login for months because nobody wrote down what they could open.

Keep a short list for every person: which account, which role, which device. On the last day, disable the account, remove the device from the trusted list and rotate any shared password they could have seen. Confirm the change took effect by trying to sign in yourself under the old details.

Watch for Messages That Ask for a Password

Most account takeovers at small stores start with a message rather than a technical attack. Someone writes as if from the platform, the courier or the bank, and asks the seller to confirm a password or open a link.

The safe habit is to treat every request for credentials as suspect, no matter how official it looks. Open the platform through your own bookmark instead of the link, and check whether the notification exists inside the account.

Support staff never need your password to help you, and a request for one is the clearest sign that something is wrong.

Devices, Sessions and Updates

Treat devices as part of the account. Set a screen lock on any phone or laptop used for the store, and sign out of sessions on machines that are lost, sold or left in a shared office.

Install app and browser updates when they arrive, and download the app only from the official source named by your platform. A copy installed from a random link is a copy you cannot trust with order data.

Most panels show a list of active sessions with the device and the last sign-in. Review it now and then, because an unfamiliar entry is worth investigating immediately.

Handle Customer Data With Care

Names, phone numbers and addresses are the most sensitive thing a store holds. Collect only what fulfilment and support genuinely need, and store it inside the platform rather than in loose spreadsheets passed around by chat.

When a file has to leave the platform, send it through a controlled channel and delete the copy once the task is done. Customer data kept in a personal download folder long after the job is finished is a risk with no upside.

What the Activity Log Tells You

Most platforms keep a record of changes and sign-ins. Reading it on a routine makes an unusual pattern stand out, because you know what normal looks like.

None of these signals proves a breach on its own. Together they show where to look first, and a quick check costs far less than a quiet problem running for weeks.

Write the Rules Down

A short written policy turns good habits into something the team can follow. It does not need legal language: a page covering who gets which role, how access is removed and what to do if a device goes missing is enough.

Review it when the team changes and when the platform adds new features. Access that was reasonable a year ago can be excessive today, and the rule is the only thing that keeps the gap from growing.

Security for a seller is a routine, not a product. Named accounts, least access, prompt offboarding and a glance at the activity log cover most of the ground, and they cost nothing but attention.