Contact

Changelog

What shipped and when, including the things that are not finished. A product with no customers yet has nothing to show but its work, so this is the work — dated, so you can tell whether anybody is still here.

—

Every document a retailer we profile asks for is now one we read or produce. New outbound: 812 credit/debit adjustments, 832 price catalogs, 879 price changes, 889 promotion announcements, and the 857 combined ship-and-bill notice. The 857 is built to the X12 standard and has not yet been through a retailer’s testing. A test now fails if any retailer page lists a document we have not built.

Shipping from the portal: look an order up by its PO number, confirm what went in four steps, and print the paperwork. An order can also be answered from a file your own system exports, so nothing that shipped has to be typed twice. Choosing a retailer during setup ticks the documents they require.

Templates can be opened, edited and compared version to version, and each version says why it was saved and who saved it. Mapping a file is now a matter of picking a column for each field and watching the orders appear, not writing a definition by hand. Fixed-width files are mapped the same way; before, a fixed-width file with many orders in it could be read as one. Retailers can be added and corrected from the portal, so a retailer newly trading EDI is ready for the next supplier the same day.

—

A walkthrough guide for the person who will actually use the portal, with screenshots of the real thing and a section on what to do when you get something wrong. A page for every retailer whose requirements we hold. PalletLabs LLC now appears in our mark, as registered.

A full pass over both portals, signed in, at desktop and phone widths. The one worth saying out loud: on an order, See what would be sent was performing the real send rather than a rehearsal. Nobody was affected — there are no customers yet — but it is the button the guide tells you to press first, so it is fixed and tested. The rehearsal now also refuses for the same reasons the real send would, and a refusal is shown on the screen rather than silently dropped.

Smaller things from the same pass: tab names and page headings now agree, in-text links go where they say, the access log reads in words rather than codes, and the retailer SFTP and AS2 settings live with the retailer rather than with your own delivery settings.

—

Made the portal’s layout survive its own security policy, which had been quietly discarding hundreds of spacing and sizing rules. Template screens now say what each template is, rather than showing an internal code.

—

Seven more retailers profiled. Outbound 846 inventory and 940 warehouse shipping orders, and the inbound 945 that answers them. A starting template for QuickBooks Online exports. Templates can be copied and rolled back to an earlier version.

We now notice when a retailer’s published requirements change, instead of finding out from a rejection.

—

The portal learned to tell you things: what a retailer rejected and why, deductions explained, an email before a ship window closes rather than after, and a way to retry a document that failed. Grocery suppliers can print their documents.

This site became readable on a phone, and a status page that cannot show green while something is wrong. The portal stopped loading fonts from Google, so signing in no longer tells a third party you use us. Tightened access checks across the API.

—

A Walmart page, including the part we could not verify. Alerting when a scheduled job keeps failing beside others that work.

—

A page for suppliers holding a letter from Kroger. A “this confused me” button in the portal that is not a support ticket. Every change now goes through review and automated checks before it reaches production, and we are alerted when a backup has not succeeded rather than only when one fails.

—

Published this changelog, an FAQ with ten real questions, and comparison pages against the three vendors people ask us about, and an about page covering why we built this and where it has got to.

Cleared our own test records out of the staff console. Everything in it had been put there by us proving the software worked, which makes a queue of probes that looks like activity.

—

A contact form on this site, writing to the same ticket queue customers use rather than to a mailbox nothing tracks. Compacted the navigation, which had grown to ten items and wrapped onto a second line.

—

Terms version 1.1 took effect, with a plain restatement beside every clause that does something to you.

—

Off-provider backups, so a bad day at our hosting provider is not also a bad day for your documents. Payment and mail providers connected. A heartbeat that pages us when the worker stops.

—

824 application advice inbound, and the 880 grocery invoice outbound — which completes the grocery pair, so a supplier on 875 orders can now be invoiced on the set their retailer actually expects.

—

The month the product became usable rather than demonstrable: the staff console, alerting, ticket management, searchable document history with wildcards, CSV, XML and JSON inbound with retailer templates, CSV and XML outbound, SFTP push delivery, and the free validator on this site.

Also the error catalogue: every failure the software can produce written out in plain English, generated from the code so the list cannot drift from what it actually reports. There are 219 of them.

—Not finished

AS2 is deployed and unproven. The server is live at as2.palletlabs.org with our certificate issued, and it has not yet exchanged a message with a real retailer. If your retailer requires AS2, tell us before you commit and we will tell you honestly where it has got to.

UBL — the XML invoice schema used for European e-invoicing — is read but not written. XLSX is not an output yet; spreadsheets come out as CSV. On EDIFACT we read purchase orders and send back the acknowledgement, with other message types to follow.

And the obvious one: no customers yet, so no testimonials and no third-party reviews. When there are, they will be real names with real outcomes, and we will have asked first.