Vista

UPDATE:

The MIS team has informed us that the patch for determining the De Minimis declaration was released on Monday and deployed in Windsor on Tuesday morning. CTIM will follow up again on Tuesday.

UPDATE:

No additional updates on the issue today. We will check again with support teams tomorrow to see if additional examples have been identified and follow up with MIS Planning on the progress of the planned patch.

UPDATE:

VCS is currently operating in two environments: our legacy experience, which we refer to as CurrentGen, and a new experience we’re building on top of the VistaPrint stack, which we’re calling NextGen.
The orders shared were placed on CurrentGen. While the issue identified is indeed incorrect, we haven’t made any recent changes that would explain this sudden spike. Given how old and long-running this codebase is, it’s likely that this problem has existed for a long time.

UPDATE:

The plant had another instance this morning from VCS. Teams are still working on the issue, where VIPER code—identified during this investigation—results in undeclared shipments in specific use cases and needs improvement. Will check tomorrow for any progress on this issue.

UPDATE:

Teams will continue to work on updating the problematic customs code. Next update Monday on their progress.

UPDATE:

Next update will be provided once we hear back from VCS during their business hours (CEST).

UPDATE:

The Planning team has verified that no recent changes in Viper would have caused these specific orders to not be tagged as declared items, though they identified some inefficiencies to the
current ‘de minimis’ logic. Those improvements will require additional time (1+ days) to implement.

For the immediate issue, the example orders are related to Vista Corporate Services, so we will reach out to them for more information.

UPDATE:

The Viper Planning team is compiling their findings which will be shared shortly. Next update in 1 hour or sooner.

UPDATE:

The cause has been narrowed to a discrepancy between orders with the same destination that might not be grouped together when shipped which can happen for valid reasons at times.

The support/dev team is currently looking into whether this is happening more than expected and if so, the potential causes. Next update in 1 hour.

UPDATE:

Support teams are making progress on the issue. Next update in 1 hour or sooner if we receive additional details.

UPDATE:

The team is still investigating the incident involving an order that was manifested on an undeclared truck, at critical priority. The next update will be provided in 30 minutes or less.

UPDATE:

The team is still investigating the incident involving an order that was manifested on an undeclared truck, at critical priority. The next update will be provided in 30 minutes or less.

UPDATE:

The team is still investigating the incident involving an order that was manifested on an undeclared truck, at critical priority. The next update will be provided in 30 minutes or less.

UPDATE:

The team is still investigating the incident involving an order that was manifested on an undeclared truck, at critical priority. The next update will be provided in 30 minutes or less.