isaaccladandClaude Opus 4.8
50b170b0af
Deploy Ladill POS / deploy (push) Successful in 35s
Builds on Phase 1 with the menu structure restaurants need: - Menu setup page (restaurant mode): categories, kitchen stations, and modifier groups with options (price deltas). - Products gain category, kitchen station, default course, and attached modifier groups (managed on the product form). - Ordering: the ticket groups the catalog by category and, when a product has modifier groups, opens a picker (respects min/max select) for options + notes + course before adding. Effective price = base + modifier deltas (resolved server-side; client prices are never trusted). - Fire-by-course: send the whole tab or just one course to the kitchen. - KDS: filter by station; each item shows its station, course, modifiers and notes. Schema additive (pos_categories, pos_stations, pos_modifier_groups, pos_modifiers, product↔group pivot, pos_sale_line_modifiers; category/station/course columns on products and lines). PosRestaurantTest covers modifiers, course and station routing; suite green (11 passed). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Ladill POS
In-store register at pos.ladill.com — product grid, cart, cash or Ladill Pay checkout.
Features (v1)
- Register — catalog + quick-amount sales
- Products — local catalog CRUD
- Sales — history and receipt view
- Ladill Pay — MoMo/card via
source_service: pos,fee_tier: sales
Local dev
cp .env.example .env
composer install
php artisan key:generate
touch database/database.sqlite
# set DB_CONNECTION=sqlite in .env
php artisan migrate
npm install && npm run build
php artisan serve
Tests
php artisan test
Deploy
See DEPLOY.md.
Roadmap
- CRM timeline + product import
- Invoice receipt prefill
- Merchant catalog import