Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter selvberging

    (@selvberging)

    S/

    You got it spot on. Yes, a marker and insert the information to the marker description.

    Ideally the user should enter all their info in a form, including the location (street address, complete with postal code, street number, etc). It should not use the GetCurrentLocation.

    There may be different category of markers. For instance Public or Private entries. By private is a person entering their own location. Ideally it should be required to have an account, and even more ideally the map should not show description to users who are not logged in – only the marker. Public is an entery where anyone can post the location of any business and should be visible to guests as well as those that are logged in. Ofcourse ideal is not the same as a “must have”.

    Here are som examples of different types of locations (categories)
    -Community member (private)
    -Local business (public):
    –Farm that offer “pick your own”
    –Farm open for visits and with livestock
    –Organisation (i.e. the local beekeeper organization)
    –Other POI

    There is much else to be desired in my scope. What I am hoping for is that there is some out of the box plugin, or combination of plugins, that could be used, without too much coding – hopefully nothing but configuration.

    One of the other things that is desired is to present all the input in a web page (table), complete with filters and sorting features. For instance being able to filter by region and/or municipality, location type, services offerred, types of animals on the farm, types of vegetables/fruit/berries, and so on. The query would return a list of locations, complete with all contact details, descriptions, uploaded image, list of vegetables/and or animals (complete with icons), etc. This would ofcourse require an even more extensive form and a much more complex solution. If the community only gets a simple map in the first version, it will make a big difference.

    I have more time than money, but I am not broke…

    Thread Starter selvberging

    (@selvberging)

    Thanks for the input.

    As for product information to the pickers (i.e. use extra bubble wrap, etc) is something we can solve by posting the information directly on the shelf itself. The main issue that I want to find a solution for is aiding the pickers in finding the correct shelf in the first place. Even if the only thing I could get was the opportunity to add a field on the order line with the shelf number, and even if the order lines were not sorted by stock location, and even if customers could see it on their order confirmation e-mail, then this would make picking more efficient and accurate. This field could for instance be located underneath the sku directly on the order page. I could allways add the location info as a suffix to the SKU, but that will lead to a whole set of other problems (i.e. affecting bookkeeping, integrations, purchases, etc, every time we decided to change product location).

    Our SKUs are based on a number sequence, not some cryptic ID-regime. As such, I could allways provide pickers with a reference sheet of all the product locations sorted by SKU number. It won’t be very elegant and effective, but could help the novices in a pinch. But I think that my problem must be so far from unique that there must be some sort of plugin that could add info to each order line or that could solve my problem by other means. I have a plugin that can add purchasing notes to the product, but this only shows up on the customer’s order confirmation mail, not in the backend.

    @riaan The print invoices packing lists does really not solve the problem of identifying the product’s location. As customers tend to complete purchases in one category before moving onto the next, the added benefit of category sorting ads little benefit. Further more, it is dependant on products in the same category also being stocked together (which they often are, but not allways).

    @eddietate It seems that you might be onto something. I ight very well get back to you unless I find a more elegant solution.

Viewing 2 replies - 1 through 2 (of 2 total)