Tag: fulfillment

  • Fulfillment – Daily Changelog – September 8, 2025

    Changelog – September 8, 2025

    Version 0.1.7 (2025-09-08)

    Added

    • Enhanced Batch Shipping Feedback: Improved confirmation and results display for raffle sticker batch shipping
      • Detailed results panel showing success/failure counts after sending to ShippingEasy
      • Displays specific error messages for failed orders with expandable error details
      • Persistent confirmation now shown on batch page (no need to navigate to ShippingEasy)
      • Toast notifications enhanced to include failure counts
      • Clear visual indicators (✅/❌) for successful and failed shipments

    Fixed

    • Raffle Sticker Shipping Weight Calculation: Fixed incorrect weight handling for ShippingEasy integration
      • Raffle sticker shipments with ≤25 stickers now correctly use 4 oz total weight
      • Fixed per-unit weight calculation to prevent ShippingEasy from multiplying weight by quantity
      • Batch send-to-shippingeasy endpoint updated to normalize existing shipments to 4 oz
      • Resolved 401 unauthorized errors when batch process calls internal shipment API
      • Added middleware exception for internal API calls to prevent authentication loops
      • Fixed auth header forwarding in batch-to-shipment API calls
  • Daily Changelog – Fulfillment App – September 5, 2025

    Daily Changelog – Fulfillment App – September 5, 2025

    Automatic QuickBooks Integration

    Today I implemented a major workflow improvement that allows invoices to be automatically sent to QuickBooks immediately after creation, eliminating the manual step that was previously required.

    What’s New

    Automatic QuickBooks Integration: Added a new checkbox option in the invoice creation dialog that allows users to automatically send invoices to QuickBooks right after creating them in the system.

    Key Features

    • Streamlined Workflow: No more manual step to send invoices to QuickBooks after creation
    • Immediate Sync: Invoices appear in QuickBooks immediately after being created
    • Smart Error Handling: Invoice creation always succeeds even if QuickBooks integration fails
    • User Choice: Users can choose when to enable automatic sending on a per-invoice basis
    • Comprehensive Feedback: Clear success/failure messages for both invoice creation and QuickBooks sync

    Technical Implementation

    • Added new checkbox in invoice creation dialog with green styling to indicate positive action
    • Enhanced invoice creation API to accept send_to_quickbooks parameter
    • Implemented automatic QuickBooks sending after successful invoice creation
    • Leverages existing proven QuickBooks integration infrastructure
    • Added detailed logging and error tracking for troubleshooting

    User Experience

    When creating invoices, users now see a new option: “Automatically send to QuickBooks” with a helpful description explaining that the invoice will be synced with the accounting system immediately after creation.

    The system provides clear feedback:

    • Success: “Invoice created and sent to QuickBooks successfully”
    • ⚠️ Partial: “Invoice created. 2/3 sent to QuickBooks successfully”
    • Error: “Invoice created but failed to send to QuickBooks”

    Benefits

    • Eliminates the manual step of sending invoices to QuickBooks
    • Ensures immediate synchronization with the accounting system
    • Reduces the chance of forgetting to send invoices
    • Provides clear feedback about integration status
    • Maintains data integrity even when QuickBooks integration fails

    The implementation is built on the existing QuickBooks integration infrastructure, ensuring reliability and consistency with the current system.

  • Fulfillment – Daily Changelog – 09/04/2025

    09/04/2025

    • Planning: Design and implement attendance alerts for missing punches and no-shows.

    Notes:

    • Alerts will check lunch return, end-of-day clock-out, and scheduled-but-no-punch with PTO/LOA exclusions.
    • Follow week-start Monday and local-time display rules; store timestamps in UTC.
    • Colors: token-only; no raw hex/rgb in any UI we add.

    • Scope

    – Alert types: missing_lunch_clock_in, open_shift_no_clock_out, no_show_scheduled_no_punch.

    – API: GET /api/attendance/alerts?date=YYYY-MM-DD (optionally range).

    – Diagnostics: structured counts and reasons in server logs.

    • Email

    – Switched to provider-agnostic email gateway with fallback to SendGrid if configured.

    – Added POST /api/attendance/alerts/send to compute and email alerts.

    – Palette rule exception: allow inline hex in src/lib/email.ts only; validator updated accordingly.

    • UI Fixes

    – Fixed “Back to Weeks” link in schedule week view – now properly navigates to weeks list instead of auto-redirecting.

    – Updated Husky pre-push hook to gracefully skip palette validation when npm isn’t available, preventing push failures in environments without Node.

    – Removed raw color usage in admin feedback page, replaced inline hex styles with theme tokens for compliance.