Will you create a taxi module? A taxi service?

Hi 6amTech Team,

I’m writing this because many 6amMart users need a feature that is standard in top delivery apps but missing here: Independent Custom Menus for each Store.

Currently, stores are forced to use the global category structure. We need each business to be able to build its own personalized menu structure from their vendor panel, creating their own navigation tabs.

Detailed Feature Breakdown:

Vendor Autonomy: Each store owner should have a “Menu Manager” to create custom headers (Tabs).

Logical Mapping: Vendors should be able to group specific products under these custom headers, regardless of which global category the product belongs to.

Dynamic UX: In the Customer App, instead of seeing the global categories, the user should see the specific custom menu created by that store.

Technical Path to Implementation:

1. Database (The “Heart” of the change): A new table to store unique menu structures per business.

PHP

Schema::create(‘vendor_custom_menus’, function (Blueprint $table) { $table->id(); $table->foreignId(‘store_id’)->constrained(); $table->string(‘menu_name’); // e.g., “Our Signature Dishes” $table->integer(‘serial_number’); // For Tab ordering $table->timestamps(); });

2. Backend Logic (Mapping products to Custom Menus): Modify the products table or create a pivot table to link products to these vendor_custom_menus. In StoreController.php, the API must prioritize these custom menus over global categories when loading a store’s profile.

3. Flutter App (Dynamic Rendering): The StoreScreen needs to be refactored to render tabs based on the vendor_custom_menus list.

Dart

// The UI should dynamically build tabs based on the vendor’s unique setup TabBar( isScrollable: true, tabs: vendorProvider.customMenuList.map((menu) => Tab(text: menu.name)).toList(), )

Conclusion: This is not just a UI tweak; it is a fundamental shift to a Business-Centric Menu System. It allows a Pharmacy to have different tabs than a Restaurant or a Fashion Store. This flexibility is what will make 6amMart the most powerful script on the market.

Please, consider this for your next update. Many of us are waiting for this specific functionality!

Best regards.

I was toggling ON send email email templates. But after I am saving the template it turn OFF back again.

Whats the difference for food ordering modules between this solution vs your stackfood solution?

I really like the rental module, but I noticed a critical missing feature regarding pricing logic for Distance Wise Trip Type. Currently, it seems we can only set a “Price per KM,” but there is no option to set a “Base Price” or “Fixed Starting Charge.”

Relying only on “Price per KM” makes short trips commercially unviable for drivers (e.g., a 2km trip yields almost no profit to cover the pickup effort).

This causes logic issues for short-distance rides where the total fare becomes too low for a driver to accept.

Without this, the module (distance wise trip type) cannot be used for real-world taxi services. Please prioritize this!

2. ​also Fuel Responsibility (Day Wise): Currently, there is no option to define who pays for fuel. In a “Day-wise” rental, we need a toggle to specify if the User bears the fuel cost or if the Provider bears it. Without this, disputes will arise.

3. ​Mileage Caps (Fair Usage Policy): For “Day-wise” rentals, vendors should be able to set a daily limit (e.g., 200km/day). If the user exceeds this, an automatic “Extra km” charge should apply.

Last day of sale ?

Team, we’ve been waiting over two years for this update. Don’t you see the error caused by having 10,000 categories to identify the right products? Please, you already said you were working on it and would release it in future updates. How much longer will we have to wait for it, as well as for the update path?

1. Sir the Ui UX of the Application is outdated now. please work on that, make it more simple detailed informative and attractive with animations and more also we have some app freezing complaints from customers please work on that.

2. The inventory management for the Stores is very difficult for store partners make it easy and Realtime based the store could schedule item availability dynamically.

3. Why there’s two notifications arriving in Vendor and delivery app also its keep ringing even we have seen order it frustrating for vendors they need to click on notifications to stop sound (The Big Busy Vendors don’t want to use our platform) . the sound should be stopped if anyhow vendor acknowledges the order or if they have opened the app.

4. Show coupons on customer checkout page with stating (You can save ….... with Coupon code …...) so customer can see and use it during checkout some customers finds it difficult to use coupons

5. Restrict Vendor Delivery radius inside zone so if my zone is 20km long we can restrict store radius to 10km for particular vendor to avoid long distance order and so on customer can choose nearest vendor.

6.In the Vehicle Category there should be both distance and weight criteria also if Cycle is set within 1Km to 5Km the bike should be able to accept 1Km to 20km orders not 5.1Km to 20Km.

7. Also i can see the delivery partner live location do not updates when the partner turn of screen or exit app. the app already have background permission it only updates when app is opened.

8.Give Free Delivery over …. order amount option with maximum distance capping option so we can restrict free delivery to short distance only long distance free delivery led to very much losses

9. Make all apps more smooths and responsive.

10. Give one more payment gateway option names as Razorpay Mobile it should support razorpay android sdk so UPI payments work seamlessly using razorpay.

Any sale or discount on extended license ?

When will we have categories by product type? This is very important. They reported that they were already working on it and that it would be available in the next update.

Hello 6amMart Team,

​Thank you for the continuous updates on this amazing script. I have been using it for a while, and I have a few suggestions that I believe would make this system perfect for a wider range of business models:

​1. PRODUCT RETURN SYSTEM Please introduce a toggle when adding an item to mark it as “Returnable” or “Non-returnable.” If returnable, allow us to set a “Return Window” (e.g., 7 days). This status should be clearly visible on the Customer App’s item detail page so users know the policy before buying.

​ 2. VENDOR-MANAGED DELIVERY TRACKING For vendors who manage their own delivery, please add an option for them to input external tracking details (Tracking URL/ID). This should sync with the User App’s order tracking page.

​ 3. BARCODE SYSTEM (POS FOCUS) It would be great to have a Barcode Generator for products and scanning capability in the POS module. This is essential for retail-heavy implementations.

​ 4. MULTI-ZONE SUPPORT Please allow vendors to select or be assigned to multiple zones, rather than being restricted to just one area.

​ These features would add massive value to the script. Looking forward to seeing them in future updates!

These are the necessary answers that you should always give because this way we know what we really need to do, whether to customize immediately or what strategy to take for the moment. It also gives us an idea of ​​the difficulty it represents for you to implement complex ideas like these and helps us understand you better:

comment by (sixamtech) Thank you for sharing your feedback with us.

We truly appreciate the continued requests for multi-currency and zone-specific payment methods. After careful internal evaluation, we currently do not have plans to introduce multi-currency as it requires re-architecting core system logic, including reporting, calculations, wallet flows, and third-party payment reconciliations. This would involve a significant development scope and time that we are not able to allocate right now.

That said, we fully understand that some businesses may require this capability. For users with immediate needs, our team is happy to assist through a custom development request. Please feel free to submit a ticket here:

https://support.6amtech.com/ We appreciate your understanding and thank you again for helping us improve the product.

Not the copy-and-paste approach from this author (6amtechstaff), which ultimately resolves nothing and doesn’t answer our question:

(6amtechstaff)’s comment: Thank you for sharing your valuable suggestion with us. We sincerely appreciate the time and effort you took to provide this feedback. We have forwarded your idea to our product team for review and consideration. Although we cannot assure implementation at this time, insights like yours play an important role in shaping future enhancements to our system. Thank you for your understanding and support.

The more details you provide about the problem, solution, or an alternative idea we can use with what we have in the current system, the more helpful it is than a vague comment that defines nothing.

If it were up to me to cancel it, I would have done so a long time ago because we’ve been complaining about this vague comment for years; it doesn’t contribute anything to our understanding.

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?