23 January 2019 (8.0.2)

New Features and Enhancements

The following features and enhancements have been implemented in this release:

Service/Admin Name Description
Catalog Admin Console In the Import and Feeds Rules pages, the left menu has been made always visible. When accessing the respective menus, the user must select a project that has the “Open” status and displays the import or Feeds Rules screen immediately. [SECOM-29608]
Ability to configure the product and SKU settings. [SECOM-7240]
The Swatch image section has been newly added displaying Swatch Image, Swatch Text, and Link columns. [SECOM-30824]
Inventory Service Enables a user to search a string with space. [SECOM-31046]
Merchandising Service For handling multiple templates, the fields, such as template ID and template URL have been newly added to the Milestone entity. [SECOM-30979]
Retrieves the start time and end time for the given time zone in the collection property. Previously, the start time and end time captured from the system time zone (UTC). [SECOM-30973]
Returns only the default locale properties along with the requestor locale properties. Previously, all the locale properties were returned. [SECOM-30102]
Merchandising Admin Console In the Site Navigation builder, the categories will be aligned to the left in the grid. Previously, the categories were aligned to the center. [SECOM-30877]
The “Search” button has been renamed as the “Apply” button in the Product tab of Category builder page. [SECOM-30976]
The presentation of Alert message has been improvised by changing the component, which displays Alert title and message. [SECOM-30978]
In the admin console, a temporary fix for the start date has been made where the milestone’s start date will be reduced by 2 days. [SECOM-31054]
Previously, a user had no options to choose a template for a category. Now, the user can choose one template among multiple templates. [SECOM-30975]
Order Service Enables the user to search a string with space. [SECOM-31043]
Previously, when SKU ID and/or Bin ID were null or empty, an error message was not displayed. Now, an appropriate error message will be displayed. [SECOM-31042]
Next possible status of the order will reflect appropriately once the order is shipped. [SECOM-31041]
The Audit field has been newly added for the audit log. [SECOM-31504]
Payment Service Enables a user to search a string with space. [SECOM-31045]
Pricing Service Previously, the Evergreen price was not returned in the Exact Price API when a schedule matches. Now, the Evergreen price is returned along with the other prices. [SECOM-30970]
Previously, the Tier price was not indexed. With this update, the Tier price has been removed from the seed data. [SECOM-31337]
Promotions Service The Audit log has been implemented for all the APIs. [SECOM-9399]
Reporting Service Enables a user to search a string with space. [SECOM-31044]
Search Service Able to retrieve response for multiple filters. [SECOM-31018]
Optimized the performance of reindexer, which reduces the time taken for reindexing the products. [SECOM-32017]
Storefront Orchestration Services Camel routes have been reorganized and regrouped for modularity. [SECOM-20596]
For the PLP calls, the Merchandizing template has been added in the response. [SECOM-30988]
Tax Service A new SKU type field has been added to the CalculateTax model in the Tax service, which is consumed by the storefront orchestration service. [SECOM-31462]

Bug Fixes

This section highlights important bugs fixed in this release:

Service/Admin Name Description
Catalog Admin Console When creating dynamic attributes through the admin console, the header validation field was not updated correctly. With this update, the header is validated appropriately. [SECOM-31315]
Catalog Admin Console honored microservice Load API changes. [SECOM-30105]
Previously, the product IDs and SKU IDs search were not working when those IDs are given in the integer. Now, this issue has been fixed. [SECOM-31023]
Clears the cache once the approval status returns success by the Feeds History call. [SECOM-30929]
The selection of attributes for the variant group is more appropriate with this update. [SECOM-30898]
Previously, a user was able to select only the date. Now, the user can select a date and time. [SECOM-30693]
Catalog Service Previously, when loading the product and SKU information, time-related fields were not converted into the required collection time zone. With this update, this issue has been fixed. [SECOM-30819]
The Load API has been updated to accept the locale parameter when loading all the products or SKUs and loading a product or SKU by ID. If the locale parameter is not given, then all the products or SKUs will be displayed. [SECOM-30103]
As per the Approval Workflow process, creating a product or SKU in the default project is not allowed. [SECOM-29831]
Feeds Service The time zone is retrieved from the collection properties in the Import or Export feed. [SECOM-31038]
When running the sales catalog rules feed, initially overwrite option was defaulted to false. With this update, this is set to true which resolves the Catalog admin issues. [SECOM-30953]
Previously, the Export feed exported only the default locale properties of products and SKUs. With this update, the given locale parameter is accepted and properties of the given locale will be exported. [SECOM-30908]
With this update, the special characters are not allowed in the product IDs. It accepts only characters and integers. [SECOM-30904]
Merchandising Admin Console While generating a Note, the project Reopened state is saved as the Denied state. With this update, the state Reopened is reflected correctly. [SECOM-30813]
An ID of the deleted category is reused while creating a new category. [SECOM-30806]
While creating a category milestone, a deleted category ID will not be used in this release. Previously, a deleted category was used while creating a category milestone. [SECOM-30804]
Previously ampersand symbol (&) and forward slash (/) were not allowed in the category name. With this update, these symbols are allowed in the category name. [SECOM-30762]
Localization has been newly implemented to filter collection properties based on the given locale in the request parameter. The response will include default locale collection properties along with the requested locale collection properties. [SECOM-30413]
The target completion date was not reflecting correctly after submitting the project. With this update, this issue has been rectified. [SECOM-31257]
Payment Service A restriction has been removed to update multiple transactions for the same payment ID. [SECOM-31048]
The transaction expiry time issue has been fixed. [SECOM-31047]
In the audit log, the PII data will not be captured. [SECOM-30949]
Promotions Service Upgraded Query DSL, which supports more operators with improvised filter format. [SECOM-31005]
Enabled pre-authentication for the promotion service calls. [SECOM-22414]
Search Service Previously, when a special character is present in the product name, the search was not retrieved properly. Now, this issue has been fixed. [SECOM-31050]
Previously, the newly added products in the Catalog were not retrieved when searching with product ID after reindexing. With this update, the newly added products are retrieved correctly when a search is made with the product ID. [SECOM-31030, SECOM-31559]
Ability to search a product by product ID. [SECOM-31031]
The default values have been rectified in the collection properties. [SECOM-31028]
The multiple filters issue has been rectified. [SECOM-31018]
Storefront Orchestration Services The X-Auth-Token has been removed from all the responses of Store Front orchestration calls. [SECOM-24566]
Ability to add more than 10 items (configurable) in the cart. [SECOM-31000]
The Tire price is now displayed appropriately in the storefront. [SECOM-30934]
Previously, the price and regular price were shown with null values in the add-to-bag response when providing both the values. With this update, the configured prices are displayed with appropriate price value for Tier Price and Scheduled Price. [SECOM-31591]

21 December 2018 (8.0.0)

Common Changes

The following changes have been implemented across all Skava Commerce microservices:

  • All Admin consoles have been completely revamped with a new look and feel. The layout is consistent across all Admin consoles.
  • Skava Commerce Framework has been introduced where each microservice uses the framework as its basic building block for development.
  • Implementation has been done using Spring Boot framework across all microservices for RESTful APIs.
  • The Product Information Management (PIM) microservice has been deprecated and instead Catalog, Pricing, and Merchandising microservices have been created separately and will be independent of each other.
  • The Cart microservice has been made as a separate microservice containing only cart and checkout features. Previously, Address Validation, Shipping and Tax features along with Cart and Checkout features were part of Cart microservice. Now, these have been created as separate microservices and act as utility microservices to the Cart microservice.
  • Storefront Orchestration and Admin Orchestration in Skava Commerce have been newly introduced in this release. For more information, see Storefront Orchestration and Admin Orchestration in this document.
  • The collection, collection properties, and collection attributes have been implemented for all microservices to manage multiple microservice instances.

Skava Commerce Framework

Skava Commerce Framework has been newly introduced in this release. It is an entry point, which provides all the required ready-made components for the microservices and Admin Orchestration:

Component Description Dependent Microservice(s)
AuditLogComponent This component provides audit-logging capabilities. All microservices
AuthorizationComponent This component enables role-based authorization for the APIs using the Spring security. All microservices
BPMNComponent This component handles business process modeling. Order
Camel This component maintains the dependency management of the Camel framework. Admin Orchestration
ContentRepositoryComponent This component stores contents (docs, images, etc.) into the repository like s3, fileserver, etc. Feeds, Foundation, and Admin Orchestration
CoreComponent This component includes exception handler and validator components. The validator component makes validations at the model level using custom annotations. The validators can be custom defined at the microservice level. All microservices
CryptoComponent This component handles encryption and decryption.
  • Address
  • Authorization
  • Cart
  • Shipping
  • Tax
  • Customers (User)
Event This component provides messaging capability using RabbitMQ. All microservices, except:

  • Shipping
  • Tax
  • Feeds
  • Search
HibernateComponent This component provides SQL database capability using MySQL. All microservices, except:

  • Promotions
  • Catalog
  • Lists
  • Merchandising
LocalizationComponent This component obtains localized messages based on the locale using the resource bundle. All microservices
LogComponent This component provides loggers to make application logging. All microservices
MongoComponent This component provides MySQL database capability using Mongo.
  • Catalog
  • Lists
  • Order
  • Promotions
  • Feeds
  • Merchandising
MavenPluginComponent This component provides a template, which converts source code Swagger documentation into the YAML file. All microservices
QueryDSL This component is used by either Mongo or Hibernate for searching/filtering in the JPA and Mongo repository.
  • Catalog
  • Address
  • Cart
  • Lists
  • Shipping
  • Tax
  • Pricing
  • Promotions
  • Search
  • Merchandising
RedisComponent This component provides caching capability using the Redis cache. All microservices, except Feeds
RestTemplateComponent This component makes HTTP remote calls to other services or third-party plugins.
  • Feeds
  • Notification
  • All Admin modules
RuleEngineComponent This component generates and executes business rules in a runtime production environment. Promotions
SolrComponent This component performs various search operations, such as full-text search, hit highlighting, faceted search, real-time indexing, dynamic clustering, database integration, etc. Search
  • Implementation has been done using Spring Boot framework across all microservices for RESTful APIs.
  • All Skava Commerce microservices are independent with each other and dependent on Skava Commerce Framework.

Admin Orchestration

The following new endpoints have been created as part of Admin Orchestration. The endpoints from the following microservices are used to integrate microservice APIs with Admin console. The request from Admin console is sent to the Admin Orchestration APIs and the appropriate resources from various applicable microservices are retrieved. The Admin Orchestration composes the response and sends it back to the Admin console.

  • Foundation (Business and Store) / Common Admin
  • Catalog
  • Order
  • Merchandising
  • Promotions
  • Feeds
  • Customers (User)
  • Collection
  • Pricing
  • Accounts
  • Authorization

Storefront Orchestration

In the 7.5 release, Skava Stream was used as a data management and orchestration layer that performed transformation and data capture for requests flowing through the Release 7.5 Skava Commerce. In the Skava Commerce 8 release, it has been replaced by Storefront Orchestration. It is an Apache Camel-based orchestration layer. This layer integrates various microservices together. It serves as a central place for customer-specific business logic and an integration point for the third party or client’s in-house microservices. The following are the features of this layer:

  • Accepts a request from the storefront and makes the request(s) to the concerned microservice(s) and aggregates the response.
  • Consists of configurable flows (sequence of actions).
  • Caches data to improve performance.
  • Uses eventing for asynchronous processes.

The following endpoints have been created as part of the Storefront Orchestration for Skava Commerce 8:

  • Customers (User)
  • Accounts
  • Catalog
  • Cart
  • Order
  • Lists
  • Notification
  • Pricing
  • Promotions
  • Merchandising

For more information, see API Endpoints of Storefront Orchestration.

Skava Commerce Microservices

Accounts

This microservice has been newly implemented in this release with the following functionalities:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.

Seller Organization can perform the following functions via Accounts APIs or Accounts Admin console:

  • Ability to create a buyer account, where the mandatory fields are DUNS number, tax ID, account type, account size, and buyer email address. The system considers the given email address as the buyer admin.
  • Ability to manage contracts between buyer and seller. The contract covers catalog, pricing, and payment method (credit and PO). If the payment method supports the PO, then the payment term is mandatory.
  • Ability to upload the contract document and the contract expiry date.
  • Ability to manage the buyer account of a client.
  • Ability to assign an account by an account admin to an account representative.
  • Ability to manage the account status (such as Pending, Active, Inactive, Suspended, and Close). Login cannot be performed if the account status is pending or close. If the status is inactive, the user can log in but cannot browse the products. If the status is suspended, the user can log in, and browse the products, but cannot add a product to the cart. The account goes to the suspended status automatically if the payment is not made as per the payment term.

Buyer Organization can perform the following functions via Accounts APIs or Storefront:

  • Support for self-on-board where buyers can onboard themselves.
  • Ability to create or manage the cost-center.
  • Ability to create or manage a team with the standard roles (such as buyer admin and buyer user).
  • Ability to invite users.
  • Ability to reset the password.
  • Ability to manage profiles.
  • Ability to view the contracts.
  • Ability to place an order.

Note: See Skava Store 8 Release Notes.

Address

In this release, the Address microservice has been newly introduced containing all the Address features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Address microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to support extension points to the third party address service providers.
  • OOTB support for Cybersource as an address validation service.
  • Ability to support Fallback for default validation (in case of third-party service being down).

Authorization

The authentication and authorization that were part of both Corporate Admin and Customers (User) microservices have been moved to a new service called the Authorization microservice. The following functions can be performed via the Authorization APIs or Authorization Admin console as part of this release:

  • Ability to create a collection and its properties (only API support is available).
  • Ability to manage the collection and its properties.
  • Ability to establish and manage a session for the users created with the Customers (User) microservice.
  • Ability to generate a JWT token, which contains session information and role/privilege information, which is used as a security token for all microservices.
  • Ability to log in to Skava Commerce admin.
  • Ability to manage roles available for each microservice (only API support is available).
  • Ability to add standard/custom roles with a set of new or existing privileges (only API support is available).
  • Ability to assign or modify a role to any user who already exists or who are currently being invited (only API support is available).

Foundation

The Business Onboarding and Store were separate microservices in the 7.5 release. Now, both have been combined under the Foundation microservice.

The following functions can be performed via Business and Store APIs or Foundation Admin console as part of this release:

Business Service:

  • Ability to view existing businesses.
  • Ability to create new business and enable one or more microservices.
  • Ability to update the existing business.
  • Ability to add users and set of roles to an instance.
  • Ability to edit the properties of an existing business.
  • Ability to view the list of stores within each business.

Store Service:

  • Ability to create an online store (B2C/B2B).
  • Ability to manage an online store (B2C/B2B).
  • Ability to associate microservice(s) to a store.
  • Ability to manage custom properties per store basis.
  • Ability to manage storefront orchestration properties.
  • Ability to schedule recurrence feed/on-demand feed.
  • Ability to preview a store.
  • Ability to clear the cache.

Cart

In this release, the Cart microservice has been made as a separate microservice containing only cart and checkout features. Previously, Address, Shipping, and Tax features along with Cart and Checkout features were part of Cart microservices.

The following functions can be performed via Cart APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to add, edit, or delete cart items.
  • Ability to add or delete promo codes.
  • Ability to add, edit, or delete custom properties to a cart or cart item.
  • Ability to add, edit, or delete communication preferences to a cart.
  • Ability to add, edit, or delete shipping details to a cart or cart item.
  • Ability to add payment details to a cart.
  • Ability to edit the existing payment details in a cart.
  • Ability to delete a particular payment detail from a cart.
  • Ability to capture delivery instructions and the latest delivery date.
  • Ability to use extension points for address validation, tax, and shipping services.
  • Ability to merge guest cart items when a customer logs in.

Catalog

In this release, the Catalog microservice has been newly introduced containing all the Catalog-related features that were part of PIM service in the 7.5 release. The PIM service has been deprecated in this release.

The following functions can be performed via Catalog APIs or Catalog Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Manage master and sales catalogs within the context of a project approval workflow.
  • Create, view, and update products and SKUs.
  • Create, view, update and delete Attribute and Attribute Group or Variant Group.
  • Maintain product versions.
  • Manage product types such as Bundle and Collections.
  • Manage assets digitally.
  • Manage semantic or SEO URLs.
  • Import products and SKUs with its attributes from the local computer in the .xls format file to the Catalog service.
  • Export products and SKUs with its attributes to the local computer in the .xls format file.
  • Sales catalogs can be generated from the master catalog by defining rules.

Customers (User)

The profile management was part of both Corporate Admin and Customers (User) microservices in the 7.5 release. Now, it has been combined and called as Customers (User) microservice. The following functions can be performed via Customers (User) microservice or Customers (User) Admin console:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create an instance collection, which holds all the admin user profile information.
  • The collections associated with stores/business holds customer profile information under the specific store/business.
  • Every valid user can log in, log out, view his profile and can update it with more information like shipping address, security questions, etc.
  • An admin with a valid role (for example, CSR) can additionally view the customers under each business/store.
  • Ability to search the existing customers based on the various attributes, such as first name, last name, email address, and/or status.
  • Ability to view, add, or edit one or more shipping addresses and set an address to default.
  • Ability to update password by resetting through email or security questions (only API support is available).
  • Ability to opt-in or opt-out to any consent, which is available under each collection.
  • Ability to track user consent history by tracking a user’s activity.
  • Ability to add, view notes for each user profile, which is stored against each profile (only API support is available).
  • Ability to freeze or delete a customer account as part of GDPR compliance.
  • Ability to view, add, or edit payment card details (via Customers (User) Admin console or Payment microservice).
  • Ability to view the order history (via Customers (User) Admin console or Order microservice).

Inventory

The following functions can be performed via Inventory APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create bins.
  • Ability to create bin items.
  • Ability to create transactions (Add, Remove, Transfer, and/or Reconcile) on bin items.
  • Ability to import bins, bin items, and/or transactions.
  • Ability to export bins, bin items, and/or transactions.

Lists

The following features have been added to the Lists microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create lists of different types (Wishlist, Favorites, etc.).
  • Ability to create lists for different item types (Product, SKU).
  • Ability to manage items within a list.
  • Access type support for lists (public, private) for sharing.

Merchandising

In this release, the Merchandising microservice has been newly introduced containing all the Merchandise and related features that were part of PIM service in the 7.5 release.

The following functions can be performed via Merchandising APIs or Merchandising Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to view, create, edit, and delete a category.
  • Ability to view, create, and edit a navigation (only API support is available).
  • Ability to view (only API support is available) or create a milestone for a category.
  • Ability to view (only API support is available), create, and edit a milestone for a navigation.
  • Ability to customize category product mapping for a category milestone.
  • Ability to customize category attribute mapping for a category milestone.
  • Ability to customize a template for a category milestone.
  • Ability to customize category hierarchy for a navigation milestone.
  • Ability to add new creative (assets) and edit the existing creative.
  • Ability to manage categories by admin users within the context of a project approval workflow.
  • Ability to publish a merchandising collection (only API support is available).

Notification

In this release, the Notification microservice has been newly introduced containing all the notification features.

The following functions can be performed via Notification APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to configure the events.
  • Ability to configure the third-party email provider and/or SMS provider.

Order

In this release, the Payment related features have been removed from Order microservice and made as a separate microservice.

The following functions can be performed via Order APIs or Order Admin console for Order microservice:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create orders (from the services, not from the admin console) with the flexibility of having alphanumeric or numeric order IDs
  • Ability to cancel order items (partial/full) (only API support is available).
  • Ability to return order items (partial/full) (only API support is available).
  • Ability to have customized order item status (via the BPM workflow) (only API support is available).
  • Ability to refund to the original payment method (store credits is not supported) (only API support is available).
  • Ability to add notes to an order (only API support is available).
  • GDPR compliance with user details anonymization on the deletion of a user account (only API support is available).
  • Ability to view the list of orders, search orders, and view order details (only API support is available).

Feeds

The following features have been added to the Feeds microservice as part of this release:

  • Ability to create a feed.
  • Ability to run a feed on-demand.
  • Ability to schedule a feed.
  • Ability to obtain feed status.
  • Ability to view feed history.

Payment

In this release, the Payment microservice has been newly introduced containing all the payment features. The payment features were part of Order service & Cart service in the 7.5 release.

The following features have been added to the Payment microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create provider master configurations (Cybersource, Braintree, Default payment processing, etc.).
  • Ability to add payments using multiple payment methods.
  • Ability to add payment items.
  • Ability to create transactions for payments based on cash/non-cash types.
  • OOTB support for Cybersource as a payment provider.

Pricing

In this release, the Pricing microservice has been newly introduced containing all the pricing features that were part of PIM service in the 7.5 release.

The following functions can be performed via Pricing APIs or Pricing Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to create and edit price facets (price types).
  • Ability to create and edit pricelists by associating the price types and a currency.
  • Ability to filter pricelists by its ID, name, currency, status, etc.
  • Ability to manage pricelists by admin users with different privileges within the context of a project approval workflow.
  • Ability to associate SKUs with a pricelist for different price values.
  • Ability to update the price of a SKU.
  • Ability to import multiple SKUs into a pricelist using .xlsx file.
  • Ability to filter SKUs using its ID, project, status, created by, created time, and its different price types.
  • Ability to configure a variable price.
  • Ability to export a price into the local computer.
  • Ability to publish a price (only API support is available)

Promotions

The following new features or enhancements have been made to the Promotions microservice or Promotions Admin console as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to launch Promotions.
  • Ability to search the approved promotion groups based on the name of a promotion group.
  • Ability to use filters within promotion group landing page such as Project, Priority, Status, Date Range, and Stop Further Processing.
  • Ability to search the approved promotions within a promotion group based on the promotion name, message, description, or promo codes.
  • Ability to use filters within the promotion landing page such as Priority, Status, Date Range, Offer On (previously Rule Type) and Offer Type (previously, Action Type).
  • Ability to create, edit, update and delete operations of the promotion group and promotions within the context of a project approval workflow.
  • Ability to approve, deny, or reopen projects that are submitted for approval.
  • Ability to view all live promotion groups and promotions that are approved.
  • Ability to manage promotion groups and promotions.
  • Ability to set up or schedule promotion group and promotion for a specific period of time.
  • Ability to configure business rules or conditions, set up promo codes and one or more actions around each promotion as required.
  • Ability to configure the promotion types, such as Item Price Offer, Item Shipping Offer, BOGO Offer (Buy X Get Y, Buy X & Y, Gift with Purchase), Cart Price Offer, and Cart Shipping Offer
  • Ability to configure the following promotion offers, such as Percentage Offer, Fixed Offer, Amount Offer (previously, Currency Offer), Formula.
  • Ability to create custom promo codes, generate random promo codes, or upload pre-defined promo codes in the CSV/TXT format file.
  • Ability to reuse promo codes across multiple promotions by using Promo Code List.

Search

This release introduces the same features of Search microservice that were part of the 7.5 release. However, all APIs covering the following functions have been completely revamped as part of this release.

The following functions can be performed via Search APIs as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to search and suggest based on the keyword.
  • Ability to spell check for search and suggestions.
  • Ability to configure weightage for search and suggestions.
  • Ability to configure default suggestions.
  • Ability to configure group suggestions.
  • Ability to redirect URLs for each synonym map, which is locale based.
  • Ability to configure synonym and curation.
  • Ability to configure sort order (product boost based on keyword).
  • Ability to configure for personalized search.
  • Ability to configure typeahead minimum characters.

Shipping

In this release, the Shipping microservice has been newly introduced containing all the Shipping-related features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Shipping microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Ability to add shipping classes.
  • Ability to configure shipping methods with shipping cost calculation (flat rate or percentage) based on the shipping class.
  • Ability to configure shipping zones with the ZIP code-based restrictions.
  • Ability to associate shipping methods to shipping zones.

Tax

In this release, the Tax microservice has been newly introduced containing all the Tax-related features that were part of Cart microservice in the 7.5 release.

The following features have been added to the Tax microservice as part of this release:

  • Ability to create a collection and its properties.
  • Ability to manage the collection and its properties.
  • Support for extension points to the third-party tax providers.
  • OOTB support for Cybersource as a tax provider.
  • Ability to support Fallback for default tax rate (in case of the third-party service being down).

 

Revision History

2019-01-23 | JP – Added Release 8.0.2 content.
2018-12-21 | JP – Added Release 8.0.0 content.