B2B2C Application

Project Proposal
24th February 2018

Address: Suite # 13, Asghar Chambers, Jail Road, Hirabad, Hyderabad

Telephone: +92-22-2611042
Website: www.zaylabs.com
Email: cs@zaylabs.com

Zay Labs is a business owned by Adil Raza Shaikh

Table of Contents
B2B2C Application.................................................................................................................................2
General Flow.........................................................................................................................................2
Key Considerations................................................................................................................................2
Backend Services...................................................................................................................................2
Zay Labs Recommendation:...............................................................................................................3
Front End:..............................................................................................................................................3
Zaylabs Recommendation.................................................................................................................4
Warehousing or Routing........................................................................................................................4
ZayLabs Recommendation.................................................................................................................4
Terms.....................................................................................................................................................4

1|Page
B2B2C Application
Business to Business to Consumer (B2B2C) is an emerging e-commerce model that combines
Business to Business (B2B) and Business to Consumer (B2C) for a complete product or service
transaction. B2B2C is a collaboration process that, in theory, creates mutually beneficial service and
product delivery channels.

As per initial understanding client requires complete separate chains for his suppliers and
consumers. It would not be a typical B2B2C model but separate B2B and B2C models in one
application. Here in after the first B of B2B will be “Supplier” and second B “We” where as in B2C
first B would be “We” and C would be “End Consumer”.

General Flow
A single entry point domain will be created. Both End Consumer and Suppliers will register on
separate registration flows.

End Consumer UI:

End Consumer UI will be similar to that of many e commerce websites will products placed by
categories, deals and complete online shopping lifecycle.

Supplier UI

Supplier will log into a completely different environment. Here supplier can add his products, add
description, single unit asking price, bulk unit asking price and current available inventory. The
inventory management of supplier would need further discussion as to what mechanism will be
used. This would be dependent of if “We” would be buying from supplier first or simply rerouting
requests.

Key Considerations
1. Backend Services (Cloud Based or In-House)
2. Front End
3. Rerouting or Warehousing

Backend Services
This is by far the most important decision that is required for this project.

In-House Backend:

Following are the Pro and Cons of In-House Backend Services.

Pros
 Gives you physical control over your
server.
 Keeps critical data in-house; no third
party has access to your information.
 No need to rely on an Internet connection
Cons
 Requires a capital investment in
hardware and infrastructure.
 Requires space in your office for
rack space or a server room/closet,
as well as dedicated IT support.
 May be more susceptible to data

2|Page
 Pros Cons
loss during disaster situations due to
in-house location. How often you
for access to data. take the data offsite will reflect how
much data you’ll lose in an
emergency.
 Can be more cost-effective for
companies that are not as concerned  No uptime guarantees.
about uptime.
Cloud base:

Following are the Pro and Cons of In-House Backend Services.

Pros Cons
 No need for onsite hardware or capital
expenses. Well suited to rapidly growing  The user experience is limited by
companies that may outgrow their the speed of the Internet connection.
infrastructure too quickly.
 Easily scalable; can be added to as
needed. Solutions are often on-demand,  Third party cloud services could
so you only pay for the options you have direct access to your data.
want.
 If the Internet goes down on your
 Even though your internet have issues if
side or on your cloud provider’s
your backend service is up your site will
side, you won’t have access to any
be running.
of your information.
 Data can be backed up in the cloud as
 The costs can outweigh the benefits
regularly as 15-minute intervals,
for companies not as dependent on
minimizing data losses in disaster
uptime.
situations.
Zay Labs Recommendation:
We would highly recommend going for the cloud based backend like Amazon Web Services (AWS)
(https://aws.amazon.com/). AWS is a great service that do most of the bulk heavy lifting for you.
They help you grow with the scalable pay as you go packages so you only pay for what you will be
using.

Front End:
Front end is the main UI or the face of your website.

Custom Development:

A php based application can be created. The biggest con of this would be us reinventing the wheel
and spending countless hours on code that is freely available in the market place.

Installed Instance

Installed instances are the websites like wordpress, Joomla, magento, shopify, opencart and others.
These are very useful tools as they have provide solid framework for you to build upon. Most of
these are highly customizable and very reliable.

3|Page
Clone Scripts

Internet is filled with cloned scripts that replicate the functionality of a popular site or app. Similarly
there are countless Ali Baba like scripts available online. These are usually quite unreliable with bare
minimum documentation for customization.

Zaylabs Recommendation
Installed instances may require more time to develop as compared to clone scripts but it will give a
solid foundation for the application. The web-application can be launched in modules to get things
going as soon as possible. Joomla is the most popular and scalable of all the installed instances but
requires a lot of work as it allows a lot of customization. Wordpress is the easiest of the lot and we
would recommend using it to start off while work on the Joomla site is done at back.

Warehousing or Routing
There are two ways of going about the ecommerce business one is have your own warehouse and
get stock in from the supplier and then getting that delivered; the second would be routing i.e.
telling the supplier to send to the customer directly on your behalf. Most modern ecommerce
websites mix both of these run their business efficiently.

ZayLabs Recommendation
We would highly recommend going for the routing mechanism to start off and then gradually mixing
it with warehousing.

Terms
Zaylabs due to their other commitments won’t be able do the development work for this site but we
would like to get involved in a consultancy role should your wish. The payment and other terms can
be discusses if and when we crossed the bridge.

4|Page