We've got 2 magento stores configured, A and B:
Store B only shows categories and products below the catgory CAT2.
Now, when searching on store B's front-end, products from categories of store A come up. How can I avoid that? I'd like to cleanly separate products assigned to store A from those assigned to store B as store B is a specialized product segment presented with another company.
Any idea how to do this?
we finally set up the second store as a different website, this way we can assign products to either one or the other in the website section of the product, and search results adapt accordingly.
Related
I have a magento store. I want to operate in a city. When one customer visit the store he/she will asked to select his/her area from a dropdown list in a popup. Then the customer is allowed to see the products in the store and shop online.
Example: Suppose My city is Bhubaneswar
Areas: Acharya Vihar, Vani Vihar, Rasulgarh, Barmunda.
U can create different stores for different places and put this Mage::app()->setCurrentStore($store_id); to make your storeid your current one
For each store you can map several areas, this mapping could be represented in your city area table, by adding a store_id column.
The customer selects the desired store by selecting the city/area, you can then redirect to the desired url with the store scope here you should use
Mage::getUrl($path, array(
'_store'=>'your_store_id'
));
To restrict the store as you said, there are different approaches, one is having a default store that is not associated with any area, then you make the categories/products available/enabled only for the stores other than this default one.
I would like know
Suppose, A order consist of three product. When i submit this product to warehouse it ship the prodduct in different shipping method.
I would like to know how can i add these tracking number in magento either programmatic php or directly using mysql query
Thank you.
You can do this without having to run any code (i.e PHP or MySQL), simply partially invoice the order by navigating to the order itself, choosing the invoice tab & checking / unchecking the appropriate products. Then, when you choose to create a shipment, you can base it off of an invoice number and assign appropriate tracking information to it.
We have a magneto store and we sell decorations that are season based. So we need to have Magento possibly split into multi stores each housing the different seasons. But I need it to ONLY allow orders from 1 season to go through the system at a time not to have the customer able to mix their products up and then complete that order.
Does anyone know if it is possible to have settings changed to lock products/carts to a single store with in a multi store site?
Thanks,
Simon.
I have a situation:
I have products that are in a CodeIgniter Cart custom store.
Each product has an ID associated with it, but also has options for it (sizes).
These sizes all have different prices. (We're talking about photos being sold at different print sizes).
Because CI Cart updates, adds and deletes based on the product ID inserted, I am not able to insert one product with 2 different sizes.
As of now, the only solution I can think of is to pass the ID to the cart as IMAGEID_OPTIONID so that it contains both IDs.
However, I thought there might be an easier, more uniform way of doing this?
Or a better solution than an ID that isn't (on it's own) associated with anything specific unless i explode it..?
I recently built a site that had these constraints. In short, you'll want to create a distinction between "products" and "product groups". Think of it as managing the most discrete data units. In reality, shirt X sized medium is actually a different thing than shirt X sized large...doubly so if you have prices that are built on these qualities (this becomes more realistic when you consider cloth patterns or colors).
So anyway, if you have a "groups" table, a "product_groups" table, and a "products" table, you can keep all of these ideas distinct. On your products table, you can have columns for "size" and "color" (and any other distinguishing property you can think of) and a column for "price". Alternatively, you can go even more hardcore and make separate pricing tables that match up prices to unique products (this would be especially useful if you want to keep track of historical prices and discounts).
Then in your cart you can simply attach product_ids to cart_ids and perform a couple of joins to determine what "group" this product is a part of, what pictures are in that group (or exist for that product), and so on. It's not a simple problem, but following this line of thought should help get you on the right path.
One last point: keeping track of unique products like this also makes inventory accounting much, much more straightforward.
I have a customer who retails third party batteries, and some batteries can replace several OEM models.
For instance, 3rd party SKU 12345 may replace Toshiba N23 and HP 53214, thus my customer would like to create two products with the same SKU in front end (they are essentially the same product). However, Magento by default does not allow duplicated SKU.
My current solution is to set SKU to not required from the backend, and add another attribute called Model that allows duplicated values, and display the Model in front end.
Is there a better way to do this? Or is it possible to allow duplicated SKU?
Tian Bo
Noble Technologies
It sounds to me like you've found a good solution. I'm not so sure you should try to have duplicate values for SKU for two reasons.
First the whole point of SKU is that it is a unique identifier. That's its only reason for existing. If you're going to have duplicate values, then it's not a unique identifier; it's just another attribute. But of course Magento still needs a unique identifier to work, which means that this is an extra field, which takes us exactly where you are now.
That said we come to my second point which is this... I'm not exactly a Magento guru, but I've built my share of e-commerce sites and one thing I've learned is that they depend on certain unbreakable rules to work properly. One of them is that unique identifiers are unique, both on the database and application level. As such, a large part of the website depends on this to function correctly. Which I'm pretty sure goes for Magento too.
So trying to change such a basic premise in something so complicated will only lead to horrors and a slow descent into madness.
This sounds like a good solution that I extended a bit further, however what I did with multiple store was to create a visible attribute ITEM_SKU (Item SKU) - make it visible and searchable and then concatenate the store_id to Magneto SKU to make it unique.
So SKU becomes (Store_id "-" SKU).
It surprises me how often people are willing to break who-knows-what parts of Magento, just to get a specific piece working how they expect.
The proper way to allow for duplicate skus is NOT to (unless you'd like to re-write large parts of the framework). You CAN, however, add a custom attribute to products that shares all the same settings as "sku" minus the setting that requires values to be unique.
Changing product pages, emails, etc to show this value instead will require a little extra work but will save you headaches later.
Why don't you create 1 product (SKU 12345) and list this product in multiple categories. So your multiple categories will be Toshiba and HP. The same product (SKU 12345) will be listed in Toshiba and HP.