Chrisanne Clover – finishing the store build on Magento 2
- Magento 2
- Implementation taken over
- B2B / B2C
- Dedicated server
- SLA
The project in brief
Magento 2
The platform the store's implementation was finished on.
B2B + B2C
Splitting access to categories separated selling to both sectors without building a second platform.
Dedicated server
The hosting in place was replaced with server infrastructure sized for the store.
SLA
After the store's production launch Aurora Creation stayed on as the client's technical support under a Service Level Agreement.
Project scope
Adapting the functionality to Magento, repairing technical bugs, changing the hosting in place, and building the split of access to categories.
Technologies
Magento 2
An unfinished implementation taken over from another agency
Chrisanne Clover asked Aurora Creation to continue the implementation of its online store on Magento 2. The project had been run by another agency before, and it reached the team as an unfinished store.
The platform we inherited took many hours of analysis, of checking its technical state and of drawing up a remedial plan. At the same time the work leading to the finished Magento 2 build had to keep moving.
Flexible communication was an important part of the engagement too: it made it possible to respond quickly to the client's new ideas and to the changes that came up as the work went on.
What had to be solved before the store could go live
- 01
Taking over a started implementation
What came in for the rest of the work was an unfinished store built earlier by another agency. The existing solution had to be analysed, its technical state checked and a remedial plan drawn up.
- 02
Bugs and surplus features
The platform in place needed corrections. Analysing and reviewing the features available identified the elements that were surplus and loading the store, and the technical bugs that needed repair.
- 03
The server infrastructure
The hosting in place had to be changed for server infrastructure sized for the Chrisanne Clover store.
- 04
Separating B2B and B2C selling
The project needed functionality giving chosen customers access to particular product categories that other buyers cannot reach.
From analysing the inherited store to the production launch
The work concentrated on putting the existing solution in order, removing the technical problems and finishing the features needed to launch the store on Magento 2.
See Magento 2 support- 01
Analysing the technical state
The unfinished store was analysed, its technical state checked and a remedial plan drawn up so the implementation could continue.
- 02
Reviewing the functionality
The features available were analysed and the elements that were surplus while loading the platform were removed.
- 03
Repairing the technical bugs
The technical bugs identified were repaired, which improved the store's performance and how smoothly it ran.
- 04
Changing the server infrastructure
The hosting in place was replaced with a dedicated server sized for the Chrisanne Clover store.
- 05
Building the split of category access
Functionality went live that lets chosen customers reach particular product categories. The mechanism was used to separate B2B from B2C selling.
- 06
The production launch and continued support
After the store's production launch the engagement continued as technical support under an SLA. The client was also offered e‑commerce SEO work.
Magento 2, a dedicated server and control over category access
The store's implementation was finished on Magento 2. The work also replaced the hosting in place with a dedicated server and built functionality that controls customers' access to particular product categories.
Who sees what
- B2B customers
- B2C customers
Split of category access
Magento 2
the store platform
Infrastructure
- Dedicated server
Beyond the platform, the server and the category-access mechanism the project involved no outside system — the material for this project names no integration with an ERP, a PIM, a WMS, a CRM or any other platform.
What is on the figure
- Split of category access
- The functionality gives chosen customers access to product categories that other buyers cannot reach.
- Dedicated server
- It replaced the hosting in place. The change helped the store run faster, brought the freedom to change settings and full administration, and opened wider possibilities for developing the platform further.
Splitting category access for B2B and B2C selling
The functionality built made it possible to separate B2B from B2C selling without creating a second platform.
The feature was built as one part of finishing the Chrisanne Clover store on Magento 2.
How the mechanism works
- 01
The customer account
A customer account is registered.
- 02
A number in the admin panel
A regular customer is given an individual number in the admin panel.
- 03
Access to categories
The number automatically opens up the product categories other buyers cannot see.
- 04
Two sectors, one platform
The mechanism makes it possible to sell differently to the B2B and the B2C sector from one platform.
We do not show the view of a category unlocked by the number: the material for this project does not show the mechanism at work, and a reconstructed screen would be a mock-up rather than evidence.
The main changes in the store we took over
Removing surplus features
Analysing the existing solution made it possible to find and remove features that were not needed while loading the platform.
Repairing technical bugs
The technical bugs picked up were repaired. The store's performance and how smoothly it ran both improved as a result.
A dedicated server
The hosting in place was replaced with proven server infrastructure sized for the store. The change helped it run faster and widened what could be built on the Magento 2 platform next.
Access to chosen categories
Regular customers are given an individual number that automatically opens up product categories other buyers cannot see. The feature supports separating B2B from B2C selling.
An unfinished project carried through to a production launch
The implementation taken over was finished and launched in production on Magento 2. Along the way the existing functionality was put in order, the technical bugs were repaired, the server infrastructure was changed and the split of category access for B2B and B2C selling was built.
- A production launch
- A store left unfinished was carried through to going live on Magento 2.
- Better performance
- Picking up and repairing the technical bugs improved the store's performance. Removing surplus features and correcting bugs also made the platform smoother to use.
- A dedicated server
- The infrastructure change helped the store run faster and opened wider possibilities for developing Magento 2.
- B2B + B2C
- The split of category access separated B2B from B2C selling without creating a second platform.
The results are described qualitatively. The material for this project holds no performance measurements from before and after the changes and no data on sales, conversion or order counts, so there are no percentages on this page — only the scope that can be confirmed.
What the client said
Aurora team has been very responsive and responsible to client requirements.See other references
Ronnie LiManaging Director, Chrisanne Clover LtdThis project is a reference point for three situations
- 01Talk to us about a Magento 2 build
Taking over an unfinished Magento 2 implementation
The Chrisanne Clover project covered analysing the existing solution, drawing up a remedial plan, removing the technical problems and carrying an implementation started earlier through to a production launch.
- 02Talk to us about growing Magento 2
B2B and B2C selling on one platform
The project built a mechanism that differentiates customers' access to product categories and used it to separate B2B from B2C selling without a second platform.
- 03See Magento 2 support
Continued support after the store went live
Going live did not end the engagement. Aurora Creation stayed on as the client's technical support under an SLA.
The key facts about the Chrisanne Clover project
What taking the implementation over covered, what work was done, and what went live on Magento 2.
Let's discuss the state of your projectThe project was finished on the Magento 2 platform.
No. Aurora Creation took over an unfinished store whose implementation had been started by another agency — see what finishing a Magento 2 store covers.
The store's technical state was analysed, a remedial plan was drawn up, the existing functionality was reviewed, the technical bugs were repaired, the server was changed and the split of category access was built.
Functionality was built giving chosen customers access to particular product categories. That separated B2B from B2C selling without creating a second platform.
Yes. The hosting in place was replaced with a dedicated server sized for the Chrisanne Clover store.
Yes. After the production launch Aurora Creation stayed on as the client's technical support under an SLA — see what AURORA CARE covers. The client was also offered e‑commerce SEO work.
See other projects
Two projects with the same threads: taking over a started Magento 2 implementation, and B2B and B2C selling run from one store.
ImplementationSklepBaterie: taking over and finishing a Magento 2 project
A started implementation taken over at the point where the technical state had to be assessed first and the store launched safely second.
See the case study
ImplementationHulajnogi Micro: a Magento 1 migration and B2B sales
The store of the Micro brand's distributor moved to Magento 2 together with accounts for trade partners and integrations with outside systems.
See the case study
Have a Magento 2 implementation that needs finishing?
Describe the stage the project is at, what has already been done, and which problems or pieces of work are still open. On that basis the Aurora Creation team can set the starting point for the rest of the build.
It also helps to know who has run the project so far and what was handed over — with that, a first call is about scope rather than generalities.
