How to weave retail outlets info into Magento site - magento

We are trying to do something interesting but challenging:
We have a couple thousand products listed on our B2C site (non-Magento), & are considering moving the site to Magento for a variety of reasons. The product pages provide detailed information about these products. Our user base would now like us to provide local information about retail stores where they can buy these products; the information required would be Retail outlet name, address, zip, phone, & a Google-map display (this last is optional).
In the front-end, each product detail page will display relevant retailers depending on the product AS WELL AS depending on the user's zip. Each user will see upto 5 nearby retailers.
My question is: how best can we set up this in Magento so that we can:
map products to retail_outlets, the way magento allows for mapping of products to categories. Products & outlets will have a many-to-many relationship, & we are looking for something that will be easy to maintain.
Map user's zips to the retailer info.
We are open to using magento 1.7, if that is a better fit.
Thanks in advance.
-TM

This is not the right place for this question as it is not related to programming and does not have code samples and is too general :( read the FAQ please
but in general you need:
add a product attribute (multiselect) with all your retail_outlets and add a possible retailers to a product
ask user to input a zip if he has not jet . you can get this from quote->getShippingAddress()->getPostcode(); if your user is
registered or something
on detail page query out your retailers by zip. This will need you to implement Geo/Spatial Search with MySQL.

Related

How to handle price dynamic

We have requirement to handle price dynamic (referring external system).
We would like to know, what is the best way to handle dynamic pricing among below :
Approach 1 :
Creating Price factory extension and overriding getBasePrice() method of customPricefactoryManager. Please confirm if it uses jalo layer.
Approach 2 :
In DefaultSLFindPriceStrategy we can customize getBasePrice() method.
If any other way too, please lets know.
We would like to know which approach can help to handle prices in addtocart operation, checkout and product page details pricing.
It is not good getting price in another system with integration online. ERP system used by few sales people but ecommerce site can be used by hundred customer in same time. ERP cannot be handle huge amount of connections. I prefer pushing price from ERP not pulling them from hybris side. On the other hand customer will be hate changing price while surfing between hybris pages. You need to plan correct time for updating price and re-calculating existing carts.
It is highly unlikely that you would need to override the above classes to get dynamic prices.
Hybris already provides OTB functionality to get prices for different-
Users
User groups
Currencies
Time range
If you are trying to get different prices based on above criterions then you can simply use the OTB price row model.Getting dynamic prices on different pages has many caveats-
The price on different pages i.e. Homepage, PDP, Cart, Checkout,
etc. might show different values confusing the customer.
It cannot
be indexed so the PLP page will almost always show a different price
value.

Can we map product category to Customer/Store in Magento

In Magento, We can able to map the customers to the website. Is it possible to map the customers to the product category or the particular store ?
Note: Each product category has to be mapped with certain group of customer. All the products should not be visible to all the customer.
How can we achieve this.
I have the same requirement on my current project ended up going with this
https://github.com/Vinai/groupscatalog2
It seems like the solution is pretty heavy but, this was the most no fuss solution and it does the trick

Schema.org microdata for marketplace

For a marketplace, schema data becomes more confusing. Not only will you want to represent your organization, but you also have the supplier's organization to worry about. Is it bad practice to have all of this data on one page? Should the product page only have product information in the metadata, and the local business only have local business details on it?
Marketplace Org
logo
name
description
LocalBusiness Org
logo
name
description
address
lat/long
product
description
rating
price
I can provide html for all of this, but I am not sure this needs it to explain. I read the schema docs pretty in-depth but it doesn't have great examples of what a marketplace site would do with multiple organizations or what Google will think of it. For instance, if there is a localbusiness with many products, is it proper to have an aggregate rating on the localbusiness page of all of their products combined into one rating?
Is it bad practice to have all of this data on one page?
No. The more the better! (Of course it may be the case that some consumers only like to work with a single item per page, but when it comes to this topic, anything might be possible. So when you are interested in a particular consumer, you should consult their documentation.)
Every itemscope creates a new item. Every item on a page is (… should be) about something different.
So don’t create several items for the same thing on the same page (unless you can use itemid so that it’s clear that the items are about the same thing).
If possible, use properties to relate the items.
For example, LocalBusiness has the property makesOffer to point "to products or services offered by the organization" (i.e., Offer), or the property owns for products "owned by the organization" (i.e., Product).
You can associate a Product via brand or manufacturer with an Organization (resp. LocalBusiness).

Using Magento Like Ebay

I want to use magento's multi store system like ebay.
I want to use stores on one domain and using the same root category but every store can have different price on every single product and I want every store to be multilingual.
Before I start I appreciate some direction, which way would be best practise to achieve this?
This cannot (reasonably) be done in Magento, mainly because pricing cannot be set at the store level AND each scope (website/store) comes with a not-insignificant performance hit. MANY have tried what you are proposing. None have succeeded. Sorry.
Actually there has many Magento extension can extend one Magento site into one Marketplace, which can let customer apply to be as one seller to sell their products as vendor on this common market.
Like:
https://www.magentocommerce.com/magento-connect/marketplace.html
https://www.magentocommerce.com/magento-connect/medma-marketplace.html
...

magento - Allow Countries - What does this mean?

ok... so I feel really stupid asking this question.. but just wondering about the Allow Countries drop down in the admin panel..
What exactly does this mean?
Does it mean that only certain countries are allowed to purchase from your site? if it does mean that how does it determine where you are shopping from? is it done using a IP Geo locator or is it determined when the user inputs their address on the checkout page?
or does it mean that only customers from certain countries have access to the site?
Regards,
Fiona
I believe it's a list of countries you are willing to ship to. Here's a reference that says this. The available list seems to be limited by locale, so no geolocating involved. No idea why this is done though.
The reason for this feature is so that you can use one Magento website to serve multiple countries with different prices or products. Say you have a German and an English store. You may have different prices and you don't want someone from Germany going to the English store and ordering a product which is not available for Germany or is at a reduced price.

Resources