If the document class is configuration-controlled, then it is possible to provide different seed files per configuration without changing the method based on scope. For example, you could create an SSKTemplateFile document in different plants and configurations, which would mean that each configuration would have its own seed file without the need for further configuration.
You will need to modify the unique key for the template document name to include the configuration name so that you can create the different template documents with the same name in two different configurations.