Description:
Currently the Native Printing client on Chrome OS will pull a ppd file from OpenPrint based on the Manufacturer / Model. However, if attached to a print server that's already been configured with a specific print driver it would be better to use the same print driver, since this may be more specific / feature-rich and up to date than the one supplied by OpenPrint

Use case:
My large retail client has standard print setup for each store with a linux CUPS print server containerized for each store and a custom ppd file from Lexmark which will drive a range of printers for that store. When a Chrome device is configured to talk to a Print Server the client pulls a print driver down from OpenPrint based on configured Manufacturer / Model. If they switch to another Lexmark printer it is likely that they would have to reconfigure the Chrome clients to use a different driver. This also potentially requires them to create an OU structure for every store that number in the thousands. 

Motivation:
The customer's motivation is that they want to configure just the print servers with their PPD files and have clients pull the driver down from the print server. This can potentially save them having to create a massive OU structure to configure print drivers for each and every store.

Existing workarounds:
Configure drivers manually for each store / create OU structure to allow them to configure clients by store.