Expanding the Integration to More Sophisticated Capabilities
The Value of Omnichannel Management and User Associations
Once an order is marked as complete, the status can change in the
eCommerce system and enable an extra self-service capability for the
end user that allows for requests regarding refunds, replacements,
questions, or support. However, it doesn’t stop here as the
integration between NetSuite and an eCommerce platform can further
incorporate the information below:
- Product catalog data with categories and products
- Accessories, associations to related items, and attributes
- Kitting information and variants
-
SKUs, product and manufacturer numbers, and detailed information
from the manufacturer or distributor
- Media, like pictures and video
-
Product information such as dimensional weight and detailed
descriptions
- Pricing data and facts about quotable-only items
- Inventory data
Whenever the items sync from NetSuite, they will likely need to be
enriched with marketing content so that they're more presentable from
an end user perspective. It's important that the integration
capabilities preserve this marketing information that might be unique
but still update other areas that are necessary. For example,
inventory and pricing data must be updated in real-time, or near
real-time, from NetSuite through an efficient and logical update
process that doesn't overwrite that rich marketing content. There
needs to be a high-fidelity level of integration between the systems
so that it's possible to preserve very useful data while also
updating a set of discrete fields, like pricing and inventory.
Other sets of information that commonly make sense to include are
location data, user data, and custom fields. User data could be pulled
from an eCommerce system into NetSuite, which would then associate
those users with contacts on a customer record. At the end user’s
discretion, their company may be set up so that new users on the
eCommerce website can make a request to associate their account with
the overall company where they work. The company might have a common
domain name or an account number that can be used to make that
association request. Then, based on your specific business logic,
there may be an approval process for their account administrator to
handle within the company. Once their user account is associated with
their customer or company record, they would be able to access past
order history, make payments on behalf of the company if they're in a
financial role, possibly use the purchase on account capability to
book items, or purchase items via an eCommerce website that would then
get synced back into NetSuite.
In respect to location data that was mentioned before, it's possible
to bring in detailed location information around multiple warehouses,
distribution centers, or stores and storefronts where applicable. This
allows for an omnichannel experience whenever end users are using an
eCommerce platform, as they receive rich data about item availability
within each of the stores or the most efficient warehouse to ship
from. The process may be dynamic, such that the eCommerce system will
dynamically select the most efficient shipping location, and potential
split shipments or split payments, while also accounting for possible
drop shipping or a need to transfer items. In conclusion, this
presents a rather extensive capability when integrating with NetSuite.