Functional Overview of NextLevelObjects Shopping Cart System


NextLevelObjects is a feature rich, sophisticated shopping cart. Retailers are given a variety of options concerning what features are implemented, and how features are implemented. NextLevelObjects allows retailers to maintain multiple web sites with one database and one code base. Configuration options are set at the web site level. Additional features can be found by downloading the PDF.

Below is a summary of the functionality contained in the shopping cart. This is a partial list of important features:

Multi-Site / Multi-Store Shopping Cart
  • One database and one code base supports one or more web sites. Reports about orders, shipments, returns, etc. can be created for a particular web site, or across all web sites.
  • Each web site can operate independently from all other web sites, even when the web sites share the same database and the same code base.
  • A web site can contain multiple web stores. Each web store has its own look, feel, and brand. Web stores can share a single shopping cart.
  • A product id can be used across multiple web sites. Product details can be customized for each web site.
  • Products can be cloned and maintained between multiple web sites.
Multi-Vendor Shopping Cart

Note: NextLevelObjects uses the term 'vendor' to describe a vendor, supplier, or partner. A vendor can be an external supplier, a corporate division, a product manager, or a retail outlet.
  • Retailer can maintain all product data, or allow selected vendors to maintain their own product data.
  • Retailer controls which vendors have access to which web sites.
  • Using a single user id, a vendor can maintain and publish their products in multiple web sites. The same product id can have different product information in each web site.
  • A vendor can have multiple shipping locations.
  • A product can reside in multiple locations.
  • A vendor can maintain their own inventory levels.
  • A vendor can ship their own products to web sites customers.
  • A vendor can process returns.
Cross Web Site Administration
  • Add or delete a web site.
  • Add, change, or delete a vendor.
  • Assign vendors to web sites.
  • Manage products across web sites.
  • Various system administration utilities.
Product Catalog Information
  • Product customization (ie: name, description, price, etc.) by web site within the same database.
  • Product search by brand, manufacturer, product type, vendor, category and status.
  • Product search by customer entered text.
  • Products can reside in multiple categories. For instance, a baseball glove can reside in the categories 'baseball', 'sports', and 'summer sports'. Customers can search for a baseball glove using any one of these categories.
  • Products can reside in multiple statuses. For instance, a baseball glove can reside in a status called 'For quick sale' and in a status called 'Sale items'. Customers can search for a baseball glove using either of these statuses.
  • Product rank by category. Since the same product can reside in multiple categories, a product can rank high (and therefore show up on the first page of a product search) in one category and rank low in another category.
  • Products can have features. Shoppers can compare the features of one product against the features of many other products.
  • Products can be sold as a kit. For instance, a 'baseball kit' can include a glove, a bat, and a baseball.
  • Products can have selectable attributes. For instance, a baseball uniform might come in an attribute called 'size', and an attribute called 'team'. A customer could then select 'small', 'medium', and 'large' for size, and 'Yankees', 'Rangers', or 'Red Sox' for team.
  • Customer pricing can be applied to product attributes. This also can be used as a simple product configurator.
  • Products can have multiple suggested products. For instance, when a customer puts a baseball glove in their cart, the system will recommend that the customer also purchase baseball glove leather treatment and a baseball bat.
  • Product prices can be implemented in a future date.
  • Product prices can have a sale start and end date set into the future.
  • A video file can be run when a customer wants to learn more about a product.
  • An audio file can be run when a customer wants to learn more about a product.
  • Instructions or other informative material can be sent with a product when it is shipped to the customer.
  • Customers can 'bookmark' a product using their browser, or save a product in the database for later review. At any time the customer can put a saved or bookmarked product in their shopping cart.
Shopping Cart Capabilities
  • Customers can put products in layaway.
  • Customers can create a gift registry.
  • Customers can put products in a 'saved' status. The product can be converted to an active order at any later time.
  • Customers can put layaway, gift, saved, and regular order types all in the same order at the same time.
  • Customers can use gift cards, coupons, and other promotions to apply discounts to their order.
  • Customer credit card is charged when order is received or when product is shipped.
  • Multiple shipping calculators
  • Simple tax calculator, or AvaTax tax calculator
Additional Customer Services
  • Customers can make offers on a product.
  • Customers can buy gift cards.
  • Customers can use coupons.
  • Customers can have multiple ship-to locations.
  • Customers can have multiple bill-to locations.
  • One page checkout (Quick Check Out).
  • Retailers can offer free shipping based on order value.
  • Retailers can offer and charge for expedited shipping.
  • Retailer can offer and charge for gift wrapping services.
  • Customers who forget their passwords can change them without system administrator intervention.
Shipping
  • Products can be shipped from multiple locations on the same order.
  • Multiple methods for calculating shipping costs.
  • Free shipping based on order value, cost, or weight.
  • Partial shipping is supported. For instance, if a customer orders 3 units of Product A, and 4 units of Product B, the retailer can send 2 units of Product A today, 3 units of Product B tomorrow, 1 unit of Product A next week, and 1 unit of Product B next month.
  • The retailer can collect payment when the customer processes the order, or when the retailer processes the shipment. If the retailer makes a partial shipment, only the items shipped are billed to the customer.
  • Support for over-shipments (with warning message).
Returns
  • Support for RNA's.
  • Support for partial returns.
  • Multiple returns can be processed against a single RNA.
  • Support for over-returns (with warning message).
Inventory Control
  • Inventory balances are maintained by physical location.
  • Products can reside in multiple locations.
  • Automated inventory adjustments based on orders, shipments, and returns.
  • Inventory control can be turned off.
Payment Processing
  • The system supports an unlimited number of payment gateways.
  • Payment can occur when the order is processed, or during shipping. Partial shipping results in partial debit of the customer's credit card.
  • Supports multiple bank accounts. For instance, a retailer can specify that all orders that use a Visa credit card use Bank Account A, and all orders that use an American Express card use Bank Account B.
Internationalization
  • Multiple language support.
  • Multiple currency support.
  • Multiple date formats.
Custom Web Design
  • Web site design in completely segregated from the shopping cart engine.
  • Each web site can have its own look, feel, and behaviors / business rules.
  • Retailers have complete control over HTML, CSS, and (most) JavaScript files.
  • Each web site has its own configuration files. The configuration files control the behavior of the web site and the shopping cart engine.
Security
  • PCI / DSS Support.
  • Protection against SQL injection and other database attacks (protects the retailer from attacks that can illegally change the database).
  • Protection against cross site scripting attacks (protects the retailer from illegal information displaying in the web site).
  • Protection against various types of code injection.
  • Support for SSL certificates (authenticates that the user is using the intended web server and that sensitive information is protected as it passes between the customer and the retailer).
  • Hard or soft user passwords (hard passwords are harder to break than soft passwords).
  • Credit card information may or may not be stored in the database.
Search Engine Friendly
  • Product based landing pages use search engine friendly URLs.
  • All URLs are easy for humans to read.
  • much, much more ...