Answers

Ask the awkward questions. That is what this page is for.

Everything below describes what the platform actually does today. Where a number appears it is the real setting the platform runs on, not a range or an average.

Getting started

Opening a store, claiming an address, and getting to your first order.

  • An email address and a password. You claim your store address during sign-up, pick a template, and the store exists from that moment — there is no application, no approval queue and no setup fee. You will need a bank account before your first withdrawal, but not before your first sale.

  • A single sitting. Realistically: a few minutes to sign up and pick a template, and then however long your product photos and prices take you. The store is live at your address from the moment you create it — adding products is you stocking a shop that is already open.

  • Your own subdomain: yourname.traxease.com. You choose it when you sign up and it is reserved to you the moment you claim it. It is a real web address you can put on a flyer, a delivery bag or a bio, and it works exactly like any other website.

  • Yes, on the Premium plan. You point your domain at us, we verify you control it, and your store answers on it. Your traxease.com address keeps working alongside it, so nothing you have already shared breaks.

  • No. There is nothing to install, nothing to host and no code anywhere in the process. If you can post a product to a chat app you can add one to your store — the fields are the same information you already type out by hand every time somebody asks.

  • The Free plan is one store. Premium allows three on the same login, each with its own address, products, orders, wallet and brand. Business sets the number with you. Stores never share data with each other, even on one account.

Money & payouts

Where your money sits, when it moves, and what it costs.

  • Card sales land in your store wallet. Once an order is delivered the money becomes available, and you withdraw it to a bank account we have verified against your name. Transfers go out through Paystack; a failed transfer re-credits your wallet automatically rather than disappearing.

  • One percent, taken when you withdraw to your bank — after the money is already in your wallet and already yours. Nothing is taken at checkout, nothing is charged per listing, and there is no fee to open or keep a store.

  • A card sale lands as pending: it is yours and it is counted, but it is not spendable until the customer has what they paid for. Mark the order delivered and it moves to available immediately. If you forget, it releases itself seven days after the sale, so a forgotten order never sits on your cash.

  • ₦1,000. That threshold exists so a transfer is worth more than it costs to send, not to keep your balance on the platform. There is no maximum and no limit on how often you withdraw.

  • They never touch the wallet. The rider collects the money and it is yours directly — Traxease takes nothing and records nothing to withdraw, because there is nothing of yours being held. Your wallet balance therefore only ever means one thing: money the platform is actually holding for you.

  • Every movement of money writes one permanent ledger row showing what moved, why, and the balance that followed it — you can read the whole history in your dashboard. Separately, a scheduled job re-adds every row for every wallet on the platform each night and fails loudly if a single kobo disagrees.

  • Yes. Refunds are processed back to the customer through the same payment they used, and the movement is recorded in your ledger like any other — as a new row, never by editing the original. Pay-on-delivery orders are settled between you and the customer directly, since no money passed through the platform.

  • Not to open a store or to sell. You do need a bank account in a name we can verify before your first withdrawal, and larger volumes may require identity verification — the dashboard tells you exactly what is needed before it becomes urgent, never after your money is already stuck.

Selling & orders

Products, checkout, delivery, and the day-to-day of running the shop.

  • Card, and pay-on-delivery. Both are first-class: card payments are verified on our server against Paystack before an order is ever marked paid, and pay-on-delivery is a proper checkout with your own delivery zones rather than a "call us" fallback.

  • You define your own zones and what each one costs — by state, by city, by however you actually deliver. The customer picks their zone at checkout and the fee is added to the order total. Traxease does not deliver anything itself and never takes a share of your delivery fee.

  • Yes. Products carry variants with their own prices and stock counts, so a dress in four sizes is one product with four things to track rather than four products to keep in step. Stock decrements on sale, and a variant that runs out shows as unavailable rather than taking an order you cannot fill.

  • The order appears in your dashboard queue with its payment method, delivery zone and items, and you get an email and an in-app notification. You move it through fulfilment as you actually work it — and when you mark it delivered, the money releases.

  • No. Guests can buy without signing up and track their order from a link. Creating an account gets them saved addresses, order history, a wishlist and reviews — which is really about your second sale to them rather than your first.

  • Yes. Coupons are part of every plan, including Free, with the usual controls over what they apply to and how long they last.

Templates & media

How the store looks, and how images work.

  • At any time, as often as you like. Products, categories, content, customers, order history and your wallet are stored independently of the template, so switching changes the shop window and nothing behind it.

  • 500 MB on the Free plan and 5 GB on Premium. An image is counted once no matter how many products use it, so re-using one photo across a range costs you one photo. If you reach the limit your store keeps selling — only new uploads are refused, with a message naming exactly what you have used.

  • There is a stock photo search built into the media library, so you can find something usable without leaving the page. A stock image is not stored on your account and costs you no storage, though it does live on someone else’s server — the interface says so where it matters, and saving a copy to your own library is one click.

  • You are shown exactly what still uses it — which products, which categories, whether it is your logo or part of a page — before anything is deleted. Deleting is allowed, but it is never silent, because a broken image on a live product page is the kind of thing you find out about from a customer.

The AI assistant

What it can do, what it is allowed to see, and what it will not do.

  • Turn a photo into a finished product draft — title, description, category, a suggested price — for you to approve. Answer questions about your own sales in plain language. Suggest what to restock or bundle based on what your store actually did. And, on Premium, answer your customers’ product and delivery questions from your published catalogue.

  • No. Anything it creates arrives as a draft with Publish, Edit and Discard on it. Nothing reaches your storefront without you saying so — an assistant that can publish is an assistant that can embarrass you at 2am.

  • No. It is scoped to your store by the same database-level isolation the rest of the platform uses, so a request for another store’s data does not return the wrong thing — it returns nothing. That boundary is tested with deliberately hostile prompts, not assumed.

  • A monthly token allowance: 50,000 on Free and 1,000,000 on Premium. Your dashboard shows what you have used. Running out affects the assistant only — your store, checkout and payouts are entirely unaffected.

Security & trust

Who can see what, and what happens if things go wrong.

  • No, and not by accident either. Isolation is applied at the database layer to every query the application can make, rather than being a filter each developer has to remember to write — so a query that forgot to scope itself returns nothing at all instead of returning someone else’s data.

  • To Paystack, never to us. Card entry happens on their checkout and we are told the outcome, which we then verify server-side against Paystack before an order changes state. Traxease never sees, stores or transmits a card number.

  • They go to a separate private storage bucket with no public address at all, and are read only through short-lived links issued to you and to platform administrators. They are never served from the same place as your product images.

  • The ledger is the answer to that question. Every movement is a permanent row with a balance snapshot, nothing is ever edited or deleted, and a nightly job re-checks every wallet against its rows. A discrepancy is therefore visible, provable and correctable — by a new row, in the open, not by a quiet adjustment.

  • Yes. Withdraw your balance and close the store whenever you want — there is no notice period, no exit fee and no minimum term. Your customers, orders and catalogue are yours.

Still holding a question?

Send it over. If enough people ask the same thing, it ends up on this page — which is how most of it got here.

We answer from Enugu, in working hours, as people