------------ Release Update 26.03.17 DB Version 206 ---------- Updated: 03/19/2026

Automated EDI Processing

Streamline Your EDI Workflow -- We're excited to announce a powerful new automation feature that eliminates the manual effort previously required for EDI 855 Purchase Order Acknowledgment processing.

Use the following new settings on EDI Properties to specify your EDI Automation settings. 

Automated Batch Processing

• Automatically processes all configured EDI partners in a single operation
• Runs independently in the background - set it and forget it
• No more manual vendor-by-vendor processing

Intelligent Error Management

• Validates each EDI configuration before processing
• Continues processing even if one vendor encounters an issue
• Never lets one problem stop the entire workflow

Proactive Failure Notifications

• Email alerts sent automatically when issues occur
• Detailed error reports include vendor names, error types, and specific messages
• Summary statistics show total processed, successful, and failed transactions

Comprehensive Logging

• Every processing attempt is logged for audit purposes
• Complete transparency into system operations
• Easy troubleshooting with detailed diagnostic information

Benefits

• Save valuable time with one-click processing for all vendors
• Reduce risk of missed acknowledgments
• Immediate notification of any issues
• Guaranteed coverage of all configured EDI partners

Contact your system administrator to configure automated EDI processing for your organization.
 

IM+ Two Way Communication with IMRCHNT

The UpdateCustomerInfo API enables seamless synchronization of customer data between your IM+ software and the IMRCHNT database. When customer information changes in IM+, this endpoint updates the corresponding records in real-time, including contact details, addresses, phone numbers, and custom fields. The API supports partial updates, so only modified fields need to be transmitted, reducing bandwidth and processing overhead. Built-in validation ensures data integrity by verifying customer existence before committing changes, and transactional updates guarantee both core customer and address records stay synchronized even if network issues occur mid-process.

Database Performance & Reliability Improvements

This update includes a set of targeted optimizations to the iMerchant database that improve speed and stability across all stores. New search indexes have been added to several high-traffic tables — including physical inventory, product details, purchase order receiving, and point-of-sale records — so that common lookups find data directly rather than scanning years of history. Stores that have already received these changes have seen dramatic improvements, with some processes like inventory posting dropping from hours to minutes. In addition, a fix has been applied to prevent a rare but impactful condition where simultaneous register activity could cause temporary table-level locks, which in some cases led to payment processor timeouts and soft voids at the register. 

Faster Image Loading at POS

To improve speed and reduce delays at the point of sale, uploaded images are now limited to 20 KB for Store Receipt, Invoice and Balance Card Images. This ensures images load quickly over the network and helps keep transactions running smoothly; if a file exceeds this size, you’ll be prompted to select a smaller image.

Recommendations

• Optimize the image — For receipt printing, images rarely need to be over 20–40 KB. Convert to grayscale, reduce DPI to 203, and compress before storing on the server.
• Pre-rasterize on the server — Send the image to the printer driver already rasterized so the RDP channel isn't doing heavy lifting.
• Use ESC/POS commands instead of images where possible — If your receipt printer supports ESC/POS, use text-based commands for logos/headers. They're tiny (bytes, not kilobytes) and render faster than image data.

The sweet spot for a receipt image over RDP is keeping it under 30–40 KB — above that, on anything less than a solid 5+ Mbps low-latency connection, users will start noticing the lag between hitting "print" and the receipt coming out.