The counter in front of NetSuite.
A point of sale for iPad, iPhone and Android that runs on your Oracle NetSuite account. Items, customers, prices and pictures come down, and every sale goes back as the document your accountant expects.
One connection, and the counter has your whole catalog.
Items and prices.
The full item record, its price levels and stock. After the first pull only changes move, so an edit in NetSuite reaches the terminal on its own.
Customers, both ways.
Searchable at the counter by any detail they give. A customer added at the terminal goes back to NetSuite.
Product pictures.
Read from the image fields your items already use, optimized to a few kilobytes and versioned. An item without one still sells.
The right document every time, not a nightly CSV.
A sale.
An invoice with the payment applied, posted as the sale completes. The books never carry an invoice nobody paid.
A return.
A credit memo and a refund against the original sale, for what was actually charged.
A sales order.
An order taken at the counter lands as a sales order for your normal fulfillment. It isn’t invoiced at the terminal.
Line discounts post as a rate override, with the reason and the approver’s name. Anything usellit can’t post is refused loudly, so a sale is either in NetSuite or visibly waiting.
Not a demo account with forty items in it.
Connects the way your admin expects.
OAuth 2.0 in the browser, or a certificate that lasts two years. The Console walks the mapping and shows the fingerprint, so you confirm the right one.
Respects NetSuite’s limits.
Up to twelve parallel SuiteQL readers on every plan, starting at three. If NetSuite throttles, usellit backs off and tells you.
Keeps selling when NetSuite is out of reach.
The catalog is on the device and sales queue locally. When the connection returns, the queue drains in order, with no duplicates.
One real NetSuite account, loaded on September 1, 2026.
54,132 items.
With 37,577 product pictures, fetched, optimized and versioned.
94,554 customers.
Found at the counter by any detail they give.
21 minutes.
To cold load all of it, 661,482 lines of transaction history included.
Verified against NetSuite’s own counts, not rounded up. Every sync ends by comparing the two sides and reports any drift that day.
How to Set Up NetSuite POS Integration
Step 1: Prepare NetSuite
Ensure your NetSuite account is ready for integration by checking permissions and roles. Create an integration record and assign necessary roles.
Step 2: Configure usellit
Log into the usellit Console, open Settings and then Connections, and choose NetSuite. Authorize with your NetSuite account; the tokens are encrypted and held by the Console, never by a device.
Step 3: Sync Data
Initiate the first data sync to pull items, customers, and prices from NetSuite to usellit. Verify the data integrity and ensure all records are correctly imported.
Following these steps ensures a smooth integration process, allowing you to leverage the full capabilities of usellit with your NetSuite account.
What people ask before they connect.
Does usellit replace NetSuite?
No. NetSuite stays the source of truth for items, customers and finance; usellit is the counter in front of it.
Do we need SuiteCommerce or SuitePOS?
No. usellit connects through its own integration record, and reads the SuitePOS image fields where your items use them.
What gets installed in NetSuite?
An integration record and a role. No SuiteApp, no bundle, no changes to your item records.
How fast does a price change reach the terminal?
Daily on Standard, every 8 hours on Pro, every 5 minutes on Elite.
More than one subsidiary or store?
Yes. Each store takes its subsidiary from its NetSuite location and posts its sales there.
Can we try it on our own NetSuite?
Yes, by invite for now: fourteen days, no card, your real items and customers, and your books untouched.
Try it on your own NetSuite account.
Fourteen days, no card, your real items and customers.