Project Description

Case Study: Organic Grocery Delivery with Multi Vendor Back-End

The customer wanted their own on demand food delivery service for organic and natural products from partner supermarkets. By only offering certified organic products they created their own niche supermarket delivery service rather than stocking all products carried.

Shuup multi vendor backend connected the multiple supermarkets with stock availability, ordering, customer data, and sales. This complex backend is shown to customers as a simple location-based ordering service, with hidden settings to allow only products form a single location once the order has started.

Supermarkets gain extra revenue through increased sales of premium products. Shoppers enjoy certified organic and natural products with the convenience of delivery to their doorstep. Through automation of the system, the customer can focus on increasing sales through marketing and press.

Challenges

Create a stunning e-commerce site that attracts and converts sales.

Sync inventory stock amounts between all supermarkets and use complex logic to create single location orders.

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

Privacy Preference Center

Consent Management

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience.

Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

Performance

These are being used to track user performance.

Cookies Used

Required

_ga, _gid, _gat,_gat_gtag

Marketing

__hs_opt_out This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies. (Expires: 2 years)

__hs_do_not_track This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot. (Expires: 2 years)

__hs_testcookie This cookie is used to test whether the visitor has support for cookies enabled. (Expires: Session cookie)

hs_ab_test This cookie is used to consistently serve visitors the same version of an A/B test page that they’ve seen before. (Expires: Session cookie)

_key When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login. The cookie name is unique for each password-protected page.

hs-messages-is-open (TTL 30 minutes) This cookie is used on the visitor UI side so HubSpot can determine/save whether the chat widget is open for future visits. It resets after 30 minutes to re-close the widget after 30 minutes of inactivity

hs-messages-hide-welcome-message (TTL 1 day)

When you dismiss the welcome message in your messages tool, a cookie is set to prevent it from appearing again for one day. Consent banner cookies

hubspotutk This cookie is used for to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts. (Expires: 10 years)

__hssc This cookie keeps track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. (Expires: 30 min)

__hssrc Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. (Expires: None. Session cookie)

messagesUtk This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor.

If you are logged in to HubSpot, HubSpot will set additional authentication cookies. You can see a complete list of cookies set by HubSpot's app here.