The specifications and functional specifications

an exemplary B2B E-Commerce strategy
phased ...

Part I - descriptive words

A viable offer requires the compilation of a specification sheet. It is the IT service provider's task to deliver these documents. To this end, workshops are held to discuss and structure requirements and to embed them in an overall context. The result of this project phase is a specification consisting of a requirement specification ("What is needed?") and a requirement specification ("How is it implemented?"). The latter is also called the technical specification. This is demanding in terms of content and usually complex - even if no one wants to hear it.

 

To clarify a widespread misunderstanding in advance: The technical specification is not intended for the client, but for those who will build it. This protects you from bad investments and reduces the risk, both in terms of time planning and budget.

 

The result is a PDF document that typically contains between 60 and 120 pages. For particularly large and/or complex projects, a specification can consist of several hundred pages.

 

A requirement specification for a B2B E-Commerce solution can have the following structure:

Cover page

Title with a short summary of what it's about.

Version history

Entry of date, version number, description of the last changes.

1. Introduction

1.1 Initial situation

Which digital processes are already mapped today?

1.2 Strategic objectives

  • Customer loyalty
  • Customer acquisition
  • Sales shift (offline to online)
  • Increase in turnover
  • Expansion through internationalisation
  • Expansion by multipliers (Multi-Store)
  • Relief for the office staff
  • Automation through process control
  • ...

1.3 Digitisation strategy in phases

Strategic goals are long-term, with a moving target. Here is an exemplatic example of a phase model.

  • Phase I in the year 20xx
    • Introduction of a B2B platform

  • Phase II in the year 20xx
    • Expansion as B2X Multi-Store Solution

  • Phase III in the year 20xx
    • internationalisation

  • Phase IV in the year 20xx
    • Introduction of a sales force solution for sales via B2B Sales APP

1.4 Objective

  • Comprehensive information about the assortment with clear and easy to use navigation
  • Complete connection to ERP
  • Connection to PIM
  • Availability of warehouse stocks and customer-specific conditions 
  • Encouraging customers or interested parties to interact with each other 
  • Added value in information procurement and order processing
  • ...

1.5 Scheduling

  • Workshops and elaboration of a specification approx. 2-3 months
  • Designs - see part II - approx. 2-3 months
  • E-Mail HTML-Designs - see part II - ca. 1 month
  • Tailor-made implementation - approx. 5 - 6 months
  • Migration of all data or initial load of all data - approx. 1 month
  • Test operation on a STAGING environment - requires that the ERP as well as all other systems are
  • Set up in the relevant IT landscape of a STAGING system - 1 - 2 months
  • Maintenance of content via the CMS - approx. 1 month

GO LIVE!

1.6 Project management

By means of a ticketing system.

 

Read more ...

2. Processes and functionalities

2.1. FRONT- and BACKEND

2.1.1. Browser compatibility

  • On which browsers with which versions does the platform have to run?

  • What happens if the user's browser does not meet these minimum requirements?

    • Layer with a hint as fallback

    • Alternative design

    • ...


Read more ...

2.1.2. SSL

Secure Sockets Layer (SSL), is a hybrid encryption protocol for secure data transmission on the Internet. Selection of a certificate.

2.1.3. Data security

The platform must be audited by means of penetration tests.

These audits are carried out by an independent company X.

2.2. The FRONTEND

2.2.1. Data protection

Which DSVGO measures should be implemented in FRONTEND?

2.2.2. Session Methodology and Visitor Recognition

As an essential prerequisite for the personalization of content and for the limitation of
Access rights are used to create and manage so-called session contexts on the server side. In this way, successive accesses of a certain visitor can be assigned to a user session - and thus to an authorization profile. The following session states can be distinguished:

  • Guest
    • unknown visitor
    • Prerequisite: Input of the general web address

  • Identified visitor
    • recognized visitor
    • Prerequisite: Access to a cookie

  • Authenticated visitor
    • registered visitor
    • Prerequisite: Login and password must be entered (if guest before) or the
      Password (if previously identified visitor)

2.2.3. Persistent shopping baskets & watch lists

Should order items be placed in the shopping cart and watch lists? 

  • stored in the cookie for guests
  • stored in the database for customers


and thus remain active beyond a session?

2.2.4. Use of cookies

Cookies are data that are stored on your computer by a website you visit.

What should the cookie contain?

  • IP address
  • Validity
  • Language settings?
  • Shopping baskets for guests?
  • Shopping lists for guests?

2.2.5. MultiChannel

Declaration on which end devices the FRONTEND must be optimally displayed

  • Desktop
  • Tablets
  • Smartphones

Read more ...

2.2.6. Tracking

Read more ...

2.2.7. Multilanguage

Read more ...

2.2.8. Multicurrency

Read more ...

2.2.9. Quality seals

  • Trusted shops
  • Internet privacy standards
  • EHI Certified Online Shop
  • S@fer Shopping - TÜV Süd

2.2.10. Page scenarios

Description of each page in words. The more detailed they are, the smaller the scope for interpretation, the smaller the surprises in terms of results and price.

  • What should happen what, when and where?
  • Which fields are mandatory, which optional?
  • Which cross effects and dependencies have to be considered?
  • Which effects are there with MouseOver, with clicks, with jumping of fields and in which order?

Typical page scenarios and comprehensive elements in FRONTEND

  • Home page
  • Product group pages
  • Search via AutoSuggest
  • Hit lists with filter: tile/lists, scrollable or with Infinity Scroll
  • Product pages for differently structured product types and parts lists
  • Zoom function for images as layers
  • Print view with specifically designed PDF page variants
  • Cross and up-selling
  • Recently viewed products
  • Emotional Shopping
  • Offerings
  • Enquiries
  • Sales
  • Residual item
  • Brand sites
  • Editorial pages as documents (min. 10 template templates)
  • Editorial pages with articles (min. 20 snippet templates)
  • Shopping Cart Layer; Shopping Cart Detail Page
  • Free orders via direct input or Excel upload
  • Watchlist layer; Watchlist detail page
  • Product comparison layer; product comparison as detailed view with sorting functions
  • Checkout process page: Overview
  • Checkout process page: Check
  • Checkout process page: Transfer Order
  • Print catalogue order & PDF downloads
  • Contact form
  • Login; Registration
  • Order history: Search
  • Order History: Order View with Quick & Fill Feature
  • Suggestion lists
  • My personal data & company data, depending on authorization (new / change / delete)
  • My addresses (new / change / delete)
  • Password forgotten; Change password
  • Subscribe / unsubscribe newsletter
  • Returns overview
  • Returns detail of an RMA
  • Rights management for shopping cart configurations

2.2.10. Base modules

Choose from these basic modules.

Detailed descriptions per module including necessary adjustments.

2.2.11. Modules

Choose from more than 90 modules.

Detailed descriptions per module including necessary adjustments.

2.3.1. Customizing

Detailed descriptions for each selected module including necessary adaptations for the BACKEND.

Additional description of ...

 

The number in brackets is the number of engines IconParc has already implemented in the framework (as of November 2017).

  • Roles (55)

    • Administrator

    • Chief editor

    • Editor

    • Catalog manager

    • Product manager

    • Order manager

    • ...

 

  • Schedulers (45)
    • CreateSitemapXML
    • UpdateSiteCoordinates
    • ExportProductFeeds
    • DetectAllStaleSessions
    • GenerateShortURLs
    • ...

  • Views (21)
    • Customer overview
    • Customer employees
    • Product groups
    • Products
    • Shipping costs
    • User
    • ...

  • Search (30)
    • Commissions
    • User
    • Dealer
    • Clients
    • Customer employees
    • Products
    • Editorial contents
    • ...

  • Reports (30)
    • Orders
    • Order processing
    • Exit pages
    • Bestseller
    • Registrations
    • Search
    • ...
  • Wizards (311)
    • Addresses
    • Users
    • Clients
    • Customer employees
    • Catalogue
    • Product groups
    • Products
    • Shop pages
    • ...

  • Tools (31) => only for developers
    • BackgroundProgressViewer
    • CheckDBAgainstMeta
    • GenerateClusterContext
    • CompareEngineInstances
    • SchedulerStatusPage
    • ...

2.3.2. Process controls

  • Automated e-mail notification processes for e.g.
    • Registrations
    • Changes of address
    • Password changes
    • Password Forgotten

  • Order
    • Orders
    • Order status
    • Shipment tracking
    • Ratings

  • Returns (RMA)
    • Return
    • Return status
    • Request a quote

  • General
    • Contact
    • Enquiries
    • Catalogue enquiries
    • Polls
    • Vouchers

Read more ...

  • Product data consolidation
  • Automated updates in the catalog area

3. Marketing

  • Budget for platform application
  • Discontinuation of advertising activities
  • Internal communication on the project
  • Sensitization of the sales department with regard to the introduction of the project

 

Read more ...

3.1. SEO

Read more ...

3.2. Google PageSpeed Insights

Read more ...

3.3. SEM

  • Strategy

  • Budget

  • Contact for

  • Introduction of LandingPages.

     

     

 

Read more ...

4. Interfaces

4.1. Catalogue data

What about catalogues, product groups and article data?

Ideally, you already have this data in a structured form, very probably distributed across ERP, PIM and possibly other systems. Before the catalog data can be used online, various consolidation steps usually have to be carried out. In particular, customer-specific prices, discounts, delivery times and availability must be dynamically supplemented. Without this real-time information, hardly any B2B customer will order from you.

 

Images

4.2. Customer master data

You maintain all customer bases in your ERP system

Customers, customer employees, invoice and delivery addresses, authorizations, payment terms, delivery options, prices & conditions etc. must somehow be linked to a new platform, and not only that: When customers change their data online, they must be automatically mirrored back into the ERP system.

4.3. Invoices & delivery notes

What about orders, delivery notes and invoices?

Would you like to transfer them manually, by e-mail or even fully automatically?

 

Read more ...

4.4. PaymentGateways

What payment options are available to your customers?

 

Read more ...

4.5. InDesign

Read more ...

5. Safety requirements

  • Password Crypting

  • Data protection and data security

  • Attack security measures

  • Fail-safety of the line

  • Fail-safe due to redundancies or clusters

  • Backup


    Read more ...

6. Infrastructure

  • System Architecture Overview
  • Specifications for dimensioning
  • Dimensioning of the hardware
  • Software
  • Operating system environment
  • Web server (Apache)
  • Application server
  • Email server
  • LUCENE Server
  • DBMS

7. Attachments

  • Contact for
  • Data structures (XML, Excel, ...)
  • Data modeling (relevant entity relationship diagrams)
  • Diagrams
  • ...

Part II - Design study

8. FRONTEND-Designs

8.1. Desktop version

Presentation of all above mentioned page scenarios - between 30 and 50 - as JPGs

8.2. Tablet version

Presentation of all above mentioned page scenarios - between 30 and 50 - as JPGs

8.3. Smartphone version

Presentation of all above mentioned page scenarios - between 30 and 50 - as JPGs

9. E-mail designs as HTML

  • Automated e-mail notification processes for e.g.
    • Registrations
    • Changes of address
    • Password changes
    • Password Forgotten

  • Order
    • Orders
    • Order status
    • Shipment tracking
    • Ratings

  • Returns (RMA)
    • Return
    • Return status
    • Request a quote

  • General
    • Contact
    • Enquiries
    • Catalogue enquiries
    • Polls
    • Vouchers
Our References
Current brochures
The Elevator Pitch:
IconParc explained in two and a half minutes


- or -

12 REASONS
Design and build your digital solution
by IconParc
What ever your digitalization project is

Talk to us.
[text.sitemap_layer in ml_comp 'content' undefined]