The problems fashion brands face
- "How much? Do you have it in size 12?" The same questions arrive in DMs and on WhatsApp all evening, and a slow reply loses the sale.
- The last piece sells twice. One dress goes to a WhatsApp buyer and a website buyer on the same afternoon, because stock lives in someone's head.
- Proof of payment by screenshot. Staff check transfer alerts by hand before releasing an order, and a fake alert can slip through.
- Checkout that misbehaves. A customer taps Pay twice and gets two orders, or cancels on the payment page and lands on a "thank you" page.
- The catalogue lives in three places. The website, a spreadsheet and the WhatsApp price list never match.
- Discounts promised in chat. A discount agreed in a DM never makes it to the invoice.
How NETICS solves them
One catalogue for everything
In Products, each item has up to 12 photos, a price, a was-price shown struck through, a stock count, "Choices customers make" for sizes and colours, and labels such as New, On sale or Limited. Fill the catalogue by hand, from a CSV file, from a Shopify product list, or with a nightly catalogue feed from your site. When an order is paid, the quantity comes off the stock count, and an item that reaches zero is marked out of stock, so nobody keeps selling it.
Answers and orders in chat
Your NETICS agent on your website chat answers from your catalogue and published policies on delivery, returns and sizing. When it names a product, the customer sees a card with the photo, price and stock. It takes orders only for items in stock, totals them from your prices, and creates the order after the customer replies "Yes, place the order", then sends a secure payment link. On WhatsApp, NETICS answers questions; when a customer is ready to buy, your team presses Send payment link in the Omnichannel Inbox and the order is taken at catalogue prices.
Checkout for your own website
If you run your own store, the developer platform makes NETICS its catalogue and checkout. Your site reads products from the API, and a catalogue.updated webhook tells it when anything changes. At checkout it creates an order with an Idempotency-Key, one key per bag: the same key returns the same order, and two taps racing each other still make one order. It then asks for a payment link with a return_url and a cancel_url.
The NETICS payment page names your business. If the customer cancels, it says "Payment cancelled, you have not been charged" and takes them back to your shop's cancel page, never to the order-received page. An order counts as paid only when the payment company confirms it, and only then does your team get a "New order ORD-..., paid" notice. A fashion retailer already runs its live catalogue and checkout on NETICS this way.
Getting paid
Under Integrations, "Get paid to your bank" verifies your account number and turns on payments. Payment confirmation comes from the payment company, not from a screenshot. NETICS takes nothing from your sales; the payment company's fee applies. See orders and payments.
Repeat buyers
Every buyer is a record in NETICS CRM. Send new-collection news by email or SMS to contacts marked subscribed, with an unsubscribe link in every email.
On Enterprise, the Website Builder has an "Online shop" layout: a home page with Shop now and featured products, a Shop page with the whole catalogue, and a Help page for delivery, returns and payment.
An example day
- 9pm. A buyer asks the website chat of an Abuja boutique whether a wrap dress comes in size 14. NETICS answers from the catalogue and shows the product card.
- 9:05pm. She orders and pays through the secure link. The stock count drops by one.
- 9:30pm. A second buyer taps Pay twice on the brand's own website. The shop sent the same Idempotency-Key both times, so there is one order.
- Next morning. The team packs the paid orders on the Products and parcels board and marks them Shipped.
Which plan fits
- Pay as you go (no monthly fee): Starter's features with 1 agent and 1 seat, paid from credits as you use them, 3 credits (NGN 45) for each AI answer.
- Starter (NGN 50,000 a month): Products, Orders, the website chat agent with 1,500 AI answers a month, WhatsApp, NETICS CRM and the public API with webhooks, which is enough to run your own store's catalogue and checkout. 3 seats.
- Growth (NGN 200,000 a month): up to 5 AI agents, 10,000 AI answers a month, 15 seats, Inventory across branches, email campaigns with no per-email charge (SMS is NGN 10 a message from credits on every plan), Creative AI Studio for images and videos, the Analytics page and Ads Center.
- Enterprise: the Website Builder with the Online shop layout, your own domain and business email.
See pricing. The 3-day trial is free and needs no card.
Frequently asked questions
Can each size have its own stock count?
Not yet. A product has one price and one stock count, and its sizes and colours are choices listed on it. If a size needs its own price or stock, list it as its own product; Duplicate makes that quick.
Does NETICS reply to Instagram DMs?
No. Instagram is not a NETICS channel. Point your bio link to your website or WhatsApp, where NETICS answers, and on Growth customers can also call a NETICS phone line.
What if a customer closes the payment page?
Nothing is charged and nothing is marked paid. The order waits unpaid, and the customer goes back to your shop. If they pay later, the verified payment wins.
Can our website give its own discount codes?
Discounts are set by your team in the console, on an order, quotation or invoice. A website or the public API cannot set one, so a total cannot be changed from outside.
What does a payment link need?
Payments turned on under Integrations, the customer's email address on the order, and, for your own store, a return address on a website listed on your NETICS agent.