Point of Sale
About us
Let's grow. Together.Our Expert Team Dedicated to Your Success
At Point of Sale, our success is driven by a team of experienced professionals committed to ensuring seamless POS integrations with NetSuite. Each member brings specialized expertise to the table, ensuring that every project is executed smoothly and efficiently
As Chief Technology Officer, Kristjan leads our technical strategy and innovation, ensuring our platform remains cutting-edge and adaptable to client needs.
With extensive experience in enterprise-level solutions, Robert works closely with clients to align business goals with our POS system, ensuring optimal performance and scalability.
Each project is supported
by a dedicated team
Project Manager
Manages timelines, communication, and deliverables to ensure projects stay on track.
Business Systems Analyst
Analyzes client requirements and ensures the solution aligns with business needs
Systems Architect
Designs the technical structure of each integration to ensure a seamless, scalable solution.
NetSuite Integration Specialist
Expert in configuring and optimizing NetSuite integrations, ensuring flawless connectivity and data sync.
SUPPORT
Frequently Asked Questions
Get answers to common questions about our integrations, services, and how to make the most of our platform
General Integration Questions
Sync Frequency: Every 15 minutes. Intervals can be managed and set by the customer as per their requirements (5 min is max).
No.
Both. The integration is a microservice in Point of Sale that utilizes NetSuite RESTlet scripts.
RESTlets.
Yes, the integration can send daily error logs to predefined email addresses.
Yes, error logs are sent daily to predefined email addresses.
No, when a new store comes online, it will already have the product sync from HQ to store completed.
Data Mapping and Control
Done by Point of Sale
Yes, the mapping is defined during scoping, and changes to mapping require Point of Sale intervention after implementation.
Yes, the integration uses RESTlets whose usage is subject to NetSuite's concurrency limits based on the plan.
Point of Sale has API and rate limits, but they are high enough not to impact the sync rate for NetSuite integration. NetSuite's limits typically get hit first.
Development and Implementation
Yes, if a Sandbox NetSuite is available.
Yes, it's preferred to work with data as close to production as possible.
Yes.
Yes, the connection uses NetSuite's internal IDs. The production setup will use the same scripts and field mapping as Sandbox, but product mapping will be done for the production environment during the initial product sync.
No, running behind typically depends on NetSuite's API concurrency limits, not Point of Sale's processing. If limits are low but there are many transactions or item updates, it will sync entities sequentially.
No.
Saved searches and Suitescript are used and will be copied to production for go-live.
Yes, all required fields will be created in the production account for go-live.
Customers, Suppliers, Products (items), Price lists, Inventory documents (inventory adjustments), Purchase documents (purchase orders and inventory receipts), Sales documents (customer orders, cash sales, customer returns). Promotions, users, system settings, reporting, dashboards, and GoERP apps are not supported by the NetSuite-Point of Sale connector.
Point of Sale: Customers
To be analyzed. Custom fields can be implemented in Point of Sale if needed.
Yes.
Minutes, with sync typically every 15 minutes.
Point of Sale: Items
Yes.
NetSuite.
To be determined as part of the analysis. Point of Sale will review needed fields for item syncing.
Yes, or an exclusion table.
Sync frequency is to be determined as part of the analysis.
Sync frequency is to be determined as part of the analysis.
Yes, package UPCs are supported in Point of Sale, and a carton-level UPC in NetSuite can be mapped to a package UPC in Point of Sale.
Assembly items are required in Point of Sale to reflect finished product quantities in inventory. Currently, bundle products are used.
TBD, based on mapping analysis.