A suspended store is closed by a platform admin: the storefront stops, owners, staff and apps are blocked, Ola stops working for the store, and the dashboard shows a full-page suspended screen. Reactivation restores access. Suspensions come down to policy violations or billing issues, and both are easier to avoid than to undo.

What does suspension do to the storefront?

Suspension closes the storefront. Customers cannot browse or buy while the store is suspended, and the store is no longer a live shop. This is the part that matters commercially: a suspension is not a private warning in a dashboard, it is a closed door.

The closure is deliberate. A platform admin suspends a store when something has to stop before it continues, and leaving the storefront open would defeat the purpose. Treat a suspension notice as urgent, not as a notification to read later.

If you have an active campaign pointing at the store, pause it. Sending paid traffic to a closed storefront wastes the spend and gives customers a bad first impression.

Tell your regular customers if the closure will last more than a day. A short message on the social channel they already use prevents the questions that arrive while the storefront is closed.

Who is blocked during a suspension?

Owners, staff and apps are all blocked. A team member cannot log in and keep processing orders, and a connected app cannot keep working on the store's behalf. The block is at the store level, not at the level of one user account.

Ola is blocked too. The assistant cannot answer customers or act on the store while it is suspended. If a customer messages during the suspension, do not expect Ola to handle it.

That combination is why suspension is more than a billing state. It stops the people, the automation and the integrations at the same time, so there is no side channel quietly keeping the store alive.

What does the owner see?

The dashboard shows a full-page suspended screen. It is not a small banner that can be dismissed while the rest of the dashboard keeps working. The screen is the signal that the store is not in a normal state.

A suspension can carry an optional reason. When a reason is present, read it before you contact support. The reason tells you which conversation to have: a policy question or a billing question.

If no reason is shown, ask. Do not guess at the cause and start changing settings at random. A support conversation with the store details is faster than a series of speculative fixes.

If the reason is unclear, take screenshots before you change anything. A record of the suspended screen and the dashboard state helps support understand what you saw.

Why can a store be suspended?

The two categories are policy violations and billing issues. A policy violation means the store has done something the platform does not allow. A billing issue means the commercial side of the account is not in order.

This article will not invent a longer list. If you are unsure whether something in your store crosses a line, ask support before you publish it, not after. The cost of a question is low.

Billing issues are the easier category to prevent. Keep a current payment method, watch for failed charges, and deal with a billing notice when it arrives rather than when the storefront closes.

How does reactivation work?

A platform admin reactivates the store, and access is restored. Owners can optionally be notified when the store is reactivated. Reactivation is an admin action, so you cannot do it yourself from the dashboard; ask support to review the store.

Before you ask for reactivation, fix the cause. If the suspension was about a product listing, remove or change it. If it was about billing, settle it. A reactivation request that arrives before the cause is fixed may produce another suspension.

After reactivation, check the store the way a customer would. Open the storefront, place a test order if you can, confirm that staff can log in and that apps and Ola are working again. Access being restored is not the same as every integration being healthy.

Ask what evidence support needs. A reactivation conversation goes faster when you can point to the listing or the payment that caused the suspension and show what you changed. Vague assurances take longer than a specific fix.

A suspension is a stop sign, not a verdict. Fix the reason, then ask for the door to be opened.

How do you avoid a suspension?

Read the platform policies before you list products, and keep the store within them. A seller who gets suspended may not have set out to break a rule. They listed something they had not checked, or they let a billing notice sit.

Keep billing current. A card that expires, a charge that fails or a plan that is not paid can all put the account in the billing category. Set a reminder to review the payment method before it expires.

Keep a record of what you sell and why. If a listing is questioned, a clear description and a legitimate source are easier to discuss than a vague product page. This is especially important for restricted or regulated categories.

Finally, do not ignore a warning. If the platform contacts you before a suspension, respond while the store is still open.

Do not open a second store to work around a suspension. A second store does not fix the first one, and it can create a worse problem if the same details are used. Fix the store you have.

Frequently asked questions

What happens to my storefront when the store is suspended?

It closes. Customers cannot browse or buy while the suspension is active.

Can staff still log in during a suspension?

No. Owners, staff and apps are blocked, and Ola is blocked as well.

How do I get my store reactivated?

A platform admin reactivates it. Contact support, fix the cause first, and ask for reactivation.

Will I be told why the store was suspended?

A suspension can carry an optional reason. If none is shown, ask support.

Can I avoid suspension by paying a fee?

No. Suspensions are about policy violations and billing issues, not a fee you can pay to reopen.

The safest position is boring: follow the policies, keep billing current, and answer platform messages while the store is still open. The pricing page explains plans and billing, features covers the dashboard, and integrations covers the apps that depend on it. For the account side of running a store, read referral links and the ambassador programme, and for payment setup, see Paystack vs Flutterwave vs Nomba.