Propuesta de mejora – Gestión de la distancia de entrega

Actualmente, el sistema calcula la tarifa de entrega según un precio por kilómetro, con cargos mínimos y máximos de entrega configurados por zona. Además, cada categoría de vehículo tiene un área de cobertura inicial y un área de cobertura máxima definidas.

Cuando un pedido excede la cobertura inicial del vehículo, el sistema continúa tramitándolo aplicando el cargo máximo de entrega, incluso si la distancia sigue aumentando. Esto implica viajes más largos para el socio repartidor sin compensación proporcional, lo que genera rechazos de pedidos, quejas y retrasos operativos.

Para evitarlo, se suelen crear microzonas para limitar la distancia de entrega. Sin embargo, este enfoque reduce la visibilidad del comercio y bloquea los pedidos válidos de clientes que desean realizar pedidos desde mayores distancias.

Solución propuesta (sin microzonas)

Proponemos añadir un campo de “Cargo adicional por kilómetro excedido” que aplica únicamente cuando la distancia del pedido excede el área de cobertura inicial del vehículo, y antes de alcanzar el área de cobertura máxima.

Ubicación de campo sugerida:

Dentro de la configuración de la Categoría de Vehículo, junto a:

Área de cobertura inicial (km)

Área máxima de cobertura (km)

Ejemplo de configuración:

Precio estándar por km: US$5

Cargo adicional por km excedido: US$7

Lógica esperada:

Hasta el área de cobertura inicial → se aplica el cargo de envío estándar.

Distancia excedida → se aplica el cargo adicional por kilómetro por cada kilómetro extra.

El coste máximo de envío actual se mantiene como límite base, mientras que la distancia excedida se calcula por separado.

Además, cuando se activa la lógica de distancia excedida:

El tiempo de entrega estimado debe aumentar según la distancia adicional.

Se debe mostrar un mensaje obligatorio de confirmación del cliente, informando sobre el mayor costo y el tiempo de entrega más largo antes de permitir que se proceda con el pedido.

Esta mejora elimina la necesidad de microzonas, mantiene la compatibilidad con el sistema actual y aborda una necesidad operativa real al equilibrar la experiencia entre el cliente, el socio de entrega y la plataforma.

order is not cancelling from admin panel, cancellation reason also not visible bug in order view blade

For 2 years your buyers have been asking for multi-currency and zone specific payment method but you still won’t listen, that’s not customer service at all. Do better guys!

It’s strange that you don’t allow different currency for different zones.. it’s such simple thing for you to create

related products are also missing, reviewed by customers are also missing. please add these option because customers cannot return and go to again and again to order same category or same module’s items. regards

do you have any demo grocery shop frontend?

Hello 6amMart Team,

We found a bug related to scheduled orders.

When a store is configured to accept scheduled orders, and the customer places a scheduled order that is paid online or via wallet, the order is created with status = Confirmed.

The issue is that neither the customer nor the admin can cancel this order, even before the scheduled time. The cancel action does nothing.

We noticed that the same order can be canceled normally only when its initial status is Pending.

So the problem seems to be related to the Confirmed status on scheduled + prepaid orders, where the cancel logic is not working.

This affects wallet refunds and admin order management.

Please check the cancel flow for scheduled orders with online/wallet payment.

Thank you.

Regarding OTP, the biggest companies with money use WhatsApp because it’s almost free, but you want those who don’t have a thousandth of those resources to pay thousands of dollars a year for SMS?

Please add multi-currency and zone specific payment method

Hello , Happy new year

When multicurrency will be available Depending on the customer’s area

Improvement Proposal – Delivery Distance Management

Currently, the system calculates the delivery fee based on a per-kilometer price, with configured minimum and maximum delivery charges at the zone level. In addition, each vehicle category has a defined starting coverage area and a maximum coverage area.

When an order exceeds the vehicle’s starting coverage area, the system continues processing the order by applying the maximum delivery charge, even if the delivery distance keeps increasing. This results in longer trips for the delivery partner without proportional compensation, leading to order rejections, complaints, and operational delays.

To prevent this, micro-zones are often created to limit delivery distance. However, this approach reduces merchant visibility and blocks valid orders from customers who are willing to order from farther distances.

Proposed solution (without micro-zones)

We propose adding an “Additional charge per exceeded kilometer” field that applies only when the order distance exceeds the vehicle’s starting coverage area, and before reaching the maximum coverage area.

Suggested field location:

Inside the Vehicle Category configuration, alongside:

Starting coverage area (km)

Maximum coverage area (km)

Example configuration:

Standard price per km: US$5

Additional charge per exceeded km: US$7

Expected logic:

Up to the starting coverage area → standard delivery charge applies.

Exceeded distance → the additional per-km charge is applied for each extra kilometer.

The existing maximum delivery charge remains as a base limit, while the exceeded distance is calculated separately.

Additionally, when the exceeded distance logic is triggered:

The estimated delivery time should increase according to the extra distance.

A mandatory customer confirmation message should be displayed, informing about the higher cost and longer delivery time before allowing the order to proceed.

This improvement removes the need for micro-zones, maintains compatibility with the current system, and addresses a real operational need by balancing the experience between customer, delivery partner, and platform.

Please Add rapido as module

Dear in 3.6 unable to cancel orders even you can check in your demo.

Great improvement. But what most have been waiting for is the Restaurant ability to list their menu titles themselves than try to fall under admin set categories. It is making it hard for merchants like McDonald’s and other top brands to enroll on the system. I hope we see this in the next update

when opening a product/category or anything, when the page loads, there is a weird flickering animation/glitch happening. fonts too small everywhere. Add to card icon next to products ”+” is too small and there is a delay after the add to cart button is clicked. please fix

3.6 update is not ok, not showing updated contents, and also have many bugs . Please check it and correct , In Admin installation. I I have installed Admin so far and revert it back, Thanks

Please add shipping method ….. Pin code wise shipping charges…

Hello sir i see this feature is available on 6valey but i didn’t see on 6ammart

Is that available?

- Optimized image uploads by compressing files and converting them to WebP format.

Thanks

Please Convert uploaded files to WebP format before saving to the database.Its already implemented stackfood its helpfull to load website more faster.

Can I directly update from version 3.3 to 3.6?