Sell everywhere with Commerce Layer Links.

Build with Commerce Layer and Nextjs.

Commerce Layer is built by developers and for developers. Our API and dev tools can integrate with any technology. Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.


Why Choose Nextjs?

The overview section briefly introduces the web framework (maximum of 1-3 paragraphs). It should include the following details:

  • A brief overview of the web framework.
  • A high-level overview of the benefits/results of the web framework (cover business and engineering benefits).
  • A brief overview of the web framework in relation to ecommerce.
  • A brief overview of the web framework in relation to use within the Commerce Layer ecosystem.
  • improved loading performance

  • markets launched within one year

  • increase in 2022 sales targets

  • availability since go‑live


Commerce Layer <> Nextjs

This section highlights the existing integration between Commerce Layer and the external service or third-party application. This can fall under any of the categories below:

  • Official integration application or plugin (e.g., Contentful app, Storyblok app, Zapier app, etc.)
  • Official template, starter, or public demo (e.g., Sanity template, Nextjs demo store, Slack bot, etc.)

This section should include the following details:

  • A summary of the integration(s).
  • Image or GIF previews of the integration.
  • A bullet or numbered list of features of the integration.
  • Links to the relevant tools mentioned and the integration itself.

Getting Started with Commerce Layer and Nextjs

This section should serve as a mini-version of the integrations getting started or installation guide (depending on the category it falls under). Here we will recommend a starting path for developers who want to start building with the partner product in view. Treat this as more of a summary of the steps/actions required and not as the actual documentation.

This section should include the following details:

  • A summary of the steps/actions required to get started with the recommended demo.
  • Link to relevant documentation of the integration (usually the README of the public GitHub repository or page on the integration partner’s website).

Commerce Layer + Nextjs + ____?

Learn more about integrating with other technologies you need to build a fully functional ecommerce product.

FAQs

Here are answers to what our customers have asked in the past, just in case you are thinking so.

  • An organization is a tenant that can be used to manage many companies, clients, or merchants within a single account. Users can be members of one or more organizations with different roles and permissions.

  • A user is a member of an organization that needs to gain access to the backend dashboard. Each user can be assigned an Admin or Read-only role. Custom roles and permissions are available for Enterprise plans.

  • A market is associated with a merchant, an inventory model, and a price list (plus an optional customer group, geocoder, and tax calculator). A market can refer to a location in a geographical region where merchants can sell items and customers can purchase or in general be used to define your selling strategy and specific business model. Commerce Layer is multi-market by design. Your organization may have one or more markets and most of the resources (price lists, inventory models, payment gateways, promotions, carrier accounts, and more) are market-specific and can be defined at a market level. Markets can be disabled. Your plan limits refer to active (i.e. enabled) markets only. If you've reached your plan's limit in terms of the number of markets, make sure to disable one of the active markets before enabling a new one.

  • SKU stands for Stock Keeping Unit and represents a distinct type of item for sale. To count the number of SKUs you need, consider all the product variants in your catalog. For example, all the size-color combinations of your t-shirts or shoes.

  • Stores enable you to map a market's physical shops (e.g. retail stores, pop-up stores, etc.) to effectively manage in-store sales and more. Stores are market-specific and can have their own stock location and payment methods. Stores can be put in scope when requesting an access token so that all the fetched resources (e.g. SKUs, prices) are automatically filtered by the related market, orders are associated with the store in scope, the stock availability is computed taking into consideration the store's stock location (if any) first, and the available payment methods are updated accordingly.

  • Commerce Layer's OMS helps you manage the entire lifecycle of your order, from creation in a cart to shipment from your warehouse. We provide several apps in the Commerce Layer Dashboard to manage the workflow. Our OMS suite of apps include the following:

    • Orders
    • Shipments
    • Returns
    • Stock transfers
    • Customers
    • Subscriptions

    Other apps related to order fulfillment that you can find in the Dashboard include

    • SKUs
    • SKU Lists
    • Price lists
    • Inventory
    • Bundles
    • Promotions
    • Gift cards
  • The Metrics API enables you to extract almost any kind of data information from your Commerce Layer's organization order, return, or cart history. By querying the Metrics API you'll be able to gather and aggregate useful data that you can leverage in different ways, such as:

    • creating your own organization reports
    • building custom metrics dashboards
    • set up metric-based alerts
    • send metric data to any open-source or in-house developed tool, library, or framework
  • The Provisioning API allows you to manage provisioning tasks automatically instead of manually. You can also use the Provisioning API to streamline user onboarding by creating accounts and permissions with simple API requests. You can pull API credentials for Commerce Layer web apps, integrations, and sales channels directly from the API, making it possible to programmatically dole out API access for key integrations and/or sales channels whenever required. Any of the administrative tasks that go with proper user and application access can be automated, saving time and helping scale your business.

  • We count the placed orders (i.e. the orders that have been confirmed by customers) in the billing cycle.

  • No. Commerce Layer integrates with many payment gateways and third-party tools. Their fees are not included in the cost per order and should be added up.

  • There's no trial period. Commerce Layer is free for developers, and it always will be. You can try our API without any time limits and switch to a paid plan when ready. Alternatively, you can speak with our sales team about trial options for the Enterprise plan.

  • Absolutely. You can manage as many organizations (i.e. brands) you want within the same account. You will pay for all of them with a single, centralized subscription.

  • No, we do not offer Commerce Layer on-premise.

  • We do. We have extended our support to nonprofit organizations. Tell us your story for consideration in this plan.