What iVendNext builds

Before you invest in an app, see what we give away free and what is yours to sell. This page lists what we build, what we give you a starter for, and what you build. Its lists come from our own work lists, and we refresh them as we close the work that changes them. It carries no dates: an item moves from next to being built to listed when it does.

Why the split works for your business, and what stays yours: Build your business on iVendNext's apps.

The build test

We build something only if it is one of three things:

1. The platform and its core: the till's money path, the stock ledger, the fiscal rules of each market, the integration layer every connector runs on, the payments layer every gateway plugs into, and the ways in: the extension points, this kit, the App library and the hosting.
2. The standard version of a need many retailers share: an app in the App library, or the standard version of a vertical such as Pharmacy or Hospitality. It is free, it starts as a sample in this kit, and you may copy it.
3. A connector that opens a channel for many partners at once: a major ERP, a major web store, a marketplace or delivery platform in our focus regions, a tax engine, or the main payment rails of a focus market. M-Pesa, Paystack and the delivery marketplaces are among these, so they are ours.

Everything else is yours to build, from our starters: each customer's own version, local and regional systems, niche solutions, and every service. A provider connects its own product through the published contract and its conformance kit.

Our two promises

• The services are always yours. Solution Partners do the implementation, customisation and support, and we never sell them to a customer a partner covers. CitiXsys works directly with a retailer only where no partner covers the country, or on an account named to partners in advance, on the partner pages you see once signed in. No account has been named, so today CitiXsys works directly only where no partner covers the country.
• Partner first in the App library. Where your listed app already answers a need, we build no free app against it, and we feature yours. You may also claim a need from our next list before we start it (Claim a need).

The honest limit. A free standard app does take the product sale of that exact need off the table: a software house that hoped to sell its own version of it to every retailer will find ours free. We accept that, because a free standard version brings more retailers to iVendNext for partners to implement, extend and support. What we keep to the letter: we never take the services from a customer a partner covers, we never build a customer's own version, we say here in advance what we will build, and we never build a free app against a partner's listed one.

What we build

Listed

In the App library now, 33 apps, free or with a key:

• AI: AI Gateway · CoPilot · Foresight
• Approvals: Price change approvals · Price change approvals across stores
• Compliance: UAE tax invoice receipt
• Customers: iVendNext Loyalty · WhatsApp messages · Gift card on spend · Customer-owned loyalty
• Integrations: SAP Business One · WooCommerce · Acumatica
• Payments: Card payments on Stripe Terminal · Partner payment gateways
• Reports: Price-deviation audit
• Selling: Warranty terms · Till field rules · iVendNext POS · Counter hardware · Price-checker kiosk · Members-only check before payment · Till guard rules · Coupon rules · Click and collect · Call-centre orders by district · Duty-free allowance and boarding pass · Age-restricted sale check · Expiry markdown
• Stock: Unit codes at the scan · Bin locations · iVendNext Handheld · Pick route

Being built

• Delivery marketplaces: Orders from delivery marketplaces arrive in iVendNext as sales orders against your store's stock, and your stock levels go back to the marketplace.
• M-Pesa payments: Customers pay with M-Pesa at the till: the payment request goes to their phone.
• Paystack payments: Customers pay through Paystack on their own phone at the till, where Paystack works.
• Deliveroo: Deliveroo orders arrive as sales in your store's stock, and your stock decides what Deliveroo shows as available.
• Talabat: Talabat orders arrive as sales in your store's stock, and your stock decides what Talabat shows as available.
• Careem: Careem orders arrive as sales in your store's stock, and your stock decides what Careem shows as available.
• Noon: Noon orders arrive as sales in your store's stock.
• Avalara sales tax: US and Canadian sales tax worked out by Avalara AvaTax, on the till and in Desk.
• Amazon: Amazon orders arrive in iVendNext as sales against your stores' stock, and your stock levels go back to Amazon.
• NetSuite: Connects iVendNext to NetSuite: items, prices and customers come from NetSuite, and your stores' sales, returns and payments go back to it.
• Sage X3: Connects iVendNext to Sage X3: items, prices and customers come from Sage X3, and your stores' sales, returns and payments go back to it.

Next

• Staff time clock
• Optical prescriptions and lab orders
• Pharmacy, the standard version: Pharmacy counter rules · Expiry and recall · Regulated stock register · Insurance co-payment
• Hospitality, the standard version: Kitchen display · Front of house · Guest ordering · Restaurant back office · Room charge

A need marked Claimed is held for a partner, with no name and no date: we do not start it while the claim holds.

What we give you a starter for

Systems that are local to a country or a region are yours to connect. For each, the kit gives you a starting point where it has one (Starters for local work):

• A local ERP or accounting system: a starting point to copy, the need it answers, and what changes per market
• A local payment gateway or wallet: a starting point to copy, the need it answers, and what changes per market
• A loyalty provider: a starting point to copy, the need it answers, and what changes per market
• A messaging gateway: what works today; no starter in the kit yet
• A local delivery app: a starting point to copy, the need it answers, and what changes per market

What you build

• Every customer's own version of an app: their fields, rules, screens and links to their other systems.
• Local and regional systems: a local ERP or accounting system, a local payment gateway or wallet, a loyalty provider, a messaging gateway, a local delivery app, a country's insurers or e-prescription service.
• Niche solutions beyond our standard versions, for the markets and formats you know.
• Every service: implementation, configuration, training, support, and hosting resale.

Our free apps that start as a kit sample are yours to copy: Make one of our apps your own.

Claim a need

If you will build something on our next list, claim it before we start it.

1. File the form. Open Claim a need: the need as this page names it, your company, what you will build and the market you will sell it in. The forms are for members only: the form is in a private repository on GitHub, so anyone not signed in as an onboarded member sees GitHub's "page not found" (who can file). Every member can read every form.
2. We answer in the issue. Once we accept your claim, the need shows here as Claimed.
3. It holds 90 days from the day you filed it, once we accept it. Within them, we do not start that need.
4. List your app, and it stays yours. Once your app is listed in the App library, partner first applies: we build no free app against it.

Only a need on the next list can be claimed. A need being built has started, a listed one is answered already (where it is one of our free kit apps, copy it and make it your customer's own), and a need on you build is yours already. The claim form in full: Claim a need.