Search by

spryker-shop / b2b-demo-marketplace

spryker-bot

Spryker B2B Marketplace Demo Shop

Package info

github.com/spryker-shop/b2b-demo-marketplace

pkg:composer/spryker-shop/b2b-demo-marketplace

Security

Advisories: 0

Aikido package health analysis

Transparency log

Statistics

Installs: 2

Dependents: 0

Suggesters: 0

Stars: 8

Open Issues: 14

202608.0 2026-08-26 14:43 UTC

Requires

Requires (Dev)

Suggests

None

Provides

None

Conflicts

None

Replaces

None

proprietary 83a84dcdbe2611630777cde0e8b3faee9a0e9da9

Published on Packagist.org on 2026-08-26 14:47 UTC

This package is auto-updated.

Last update: 2026-10-23 19:54:43 UTC

README

Build Status Scrutinizer Code Quality Minimum PHP Version

Description

Spryker B2B Marketplace Demo Shop is a collection of Spryker Marketplace B2B-specific features. It suits most projects as a starting point of development and can be used to explore Spryker.

B2B Marketplace Demo Shop quick start

This section describes how to get started with the B2B Marketplace Demo Shop quickly.

For detailed installation instructions, see Install Spryker.

Prerequisites

Recommended system requirements for MacOS:

Macbook type vCPU RAM
15' 4 6GB
13' 2 4GB

Install the B2B Marketplace Demo Shop

  1. Create a project folder and navigate into it:
mkdir spryker-b2b-marketplace && cd spryker-b2b-marketplace
  1. Clone the B2B Marketplace Demo Shop:
git clone https://github.com/spryker-shop/b2b-demo-marketplace.git ./spryker-b2b-marketplace
  1. Clone the Docker SDK:
git clone git@github.com:spryker/docker-sdk.git docker
  1. Set up a desired environment:

Set up a development environment

  1. Bootstrap the docker setup:
docker/sdk boot deploy.dev.yml

  1. If the command you've run in the previous step returned instructions, follow them.

  2. Build and start the instance:

docker/sdk up
  1. Switch to your branch, re-build the application with assets and demo data from the new branch:
git checkout {your_branch}
docker/sdk boot -s deploy.dev.yml
docker/sdk up --build --assets --data

Depending on your requirements, you can select any combination of the following up command attributes. To fetch all the changes from the branch you switch to, we recommend running the command with all of them:

  • --build - update composer, generate transfer objects, etc.
  • --assets - build assets
  • --data - get new demo data

You've set up your Spryker B2B Marketplace Demo Shop and can access your applications.

Set up a production-like environment

  1. Bootstrap the docker setup:
docker/sdk boot -s

  1. If the command you've run in the previous step returned instructions, follow them.

  2. Build and start the instance:

docker/sdk up
  1. Switch to your branch in one of the following ways:
  • Switch to your brunch, re-build the application with assets and demo data from the new branch:
git checkout {your_branch}
docker/sdk boot -s
docker/sdk up --assets --data
  • Light git checkout:
git checkout {your_branch}
docker/sdk boot -s

docker/sdk up

Depending on your requirements, you can select any combination of the following up command attributes. To fetch all the changes from the branch you switch to, we recommend running the command with all of them:

  • --build - update composer, generate transfer objects, etc.
  • --assets - build assets
  • --data - get new demo data
  1. Reload all the data:
docker/sdk clean-data && docker/sdk up && docker/sdk console q:w:s -v -s

You've set up your Spryker B2B Marketplace Demo Shop and can access your applications.

Automated testing

There are several testing frameworks integrated into this repository:

  • Codeception tests that are part of this repository are located in tests folder and you can adjust them as needed throughout the development of your project.
  • Robot Framework tests and Cypress tests that are used for testing of Spryker core features are located in separate repositories.
    • They are integrated via composer.json. You should remove the mentions of spryker/cypress-tests and spryker/robotframework-suite-tests from composer.json ("repositories" and "require-dev" sections) unless you plan to re-use these tests on your project.
    • Spryker does not guarantee these tests would work on a customized project.
  • In addition, this project has its own project-owned end-to-end UI test as a part of this repository under tests/cypress-boilerplate/ — plain committed files, not a Composer dependency, so nothing is fetched at install or CI time.
    • Run tests locally with npm run cy:open / npm run cy:run from tests/cypress-boilerplate/ — see tests/cypress-boilerplate/README.md for setup and environment configuration.

Troubleshooting installation of the B2B Marketplace Demo Shop

This section describes the most common issues related to the installation of the B2B Marketplace Demo Shop.

For a complete troubleshooting, see Troubleshooting Spryker installation issues.

when

You get unexpected application behavior or errors.

then

  1. Check the state of the directory:
git status

  1. If there are untracked files (returned in red), and they are not necessary, remove them.

  2. Restart file synchronization and rebuild the codebase:

docker/sdk trouble
docker/sdk boot -s deploy.dev.yml
docker/sdk up --build --assets

when You do not see the expected demo data on the Storefront.

then

  1. Open the queue broker and wait until all the queues are empty.

  2. If the queues are empty, and the issue persists, reload the demo data:

docker/sdk trouble
docker/sdk boot -s deploy.dev.yml
docker/sdk up --build --assets --data

Contributing to the repository

For contribution guidelines, see Code contribution guide.