Click here to book a no-obligation intro call!

weclappOS: What weclapp prints itself and what Fulfillment 4 weclapp adds

weclapp prints your documents, Fulfillment 4 weclapp the shipping papers. Both via the same weclappOS client.

Click here to book a no-obligation intro call!

weclappOS is weclapp's free desktop client for Windows, macOS and Linux. It picks up print jobs from the weclapp cloud and outputs them to the printers on your network. weclapp uses it for documents that are to be printed on an event. What weclapp doesn't know: carrier labels, the carrier's customs documents, the ADR transport document and the moment at the packing table when the parcel is closed. Fulfillment 4 weclapp fills this gap, in the same print path. Here you'll find who prints what, so that nothing comes out of the printer twice or not at all.

Book a no-obligation intro call

What weclapp prints itself

  • Print configuration in weclapp: For each status and sales channel, you define which document lands on which weclappOS printer, for example the invoice as soon as it is created, or the delivery note.
  • Your document printing stays as it is: Fulfillment 4 weclapp does not interfere with this configuration and does not bring its own print client.

What Fulfillment 4 weclapp adds

  • Shipping label at scan: The app books the label with the carrier, stores it as a document on the weclapp delivery and creates a print job for the weclappOS printer at your packing table. How the scan works: Scan the delivery note, print the label
  • Customs documents: The carrier's customs document and, for non-EU shipments with their own switches, invoice and delivery note as customs enclosures. Details: Printing customs documents
  • ADR transport document: from the dangerous goods data of your items. Details: Gefahrgut 4 weclapp
  • Targeted printer per document type: Label, customs documents and ADR document go to the printers that each packer selects for them. Details: Printers per packing table

Status change or scan: who triggers what

weclapp prints documents on a status event. The carrier label, by contrast, is created at the scan at the packing table, i.e. when the goods are actually packed; a status change in weclapp alone does not book a label. For multi-parcel shipments, the label of the previous parcel is created as soon as you start the next one, and completion sets the delivery to "Shipped" (Multi-parcel shipments with box scan, Batch picking with turbo label).

If you already print the invoice or delivery note for all shipments via the weclapp print configuration, you leave out the customs enclosures in the app, otherwise they end up in the parcel twice. If you only need them outside the EU, you switch them on in the app. We clarify this with you in the setup appointment. Back to the overview: Print automation with weclappOS.

FAQ

Frequently asked questions

Do I need a second print client alongside weclappOS?

No. weclapp documents and shipping papers from Fulfillment 4 weclapp run through the same weclappOS client.

Does Fulfillment 4 weclapp also print invoices for EU shipments?

No, the app prints the invoice and delivery note as customs enclosures for shipments outside the EU. For everything else, you use weclapp's print configuration.

Can weclapp print the shipping label on a status change?

The carrier label is created at the scan at the packing table, not at the status change. That way it always matches the goods actually packed.

Documents and shipping papers cleanly separated?

We look at your weclapp print configuration and set up shipping printing so that nothing ends up in the parcel twice.

Book an appointment